2012-03-12 - Re: [GRASE-Hotspot] #68: Multi language selection for user part

Header Data

From: GRASE Trac <tr***c@grasehotspot.org>
Message Hash: ed93a9d0b86fb07f3b09c6cc7d8554e03b3d5c9f8bd52543fa82da39205941e6
Message ID: <069.5e98afb0407e3590d8fe52affabf9aa3@grasehotspot.org>
Reply To: <054.55d8f9545e45c0cec372ac698d73d302@grasehotspot.org>
UTC Datetime: 2012-03-12 16:22:31 UTC
Raw Date: Mon, 12 Mar 2012 23:22:31 -0000

Raw message 

#68: Multi language selection for user part
---------------------------------+----------------------
  Reporter:  hans van de voorde  |      Owner:  tim
      Type:  enhancement         |     Status:  accepted
  Priority:  major               |  Milestone:  3.9
 Component:  Splash Screens      |    Version:  3.7
Resolution:                      |   Keywords:
---------------------------------+----------------------
Changes (by tim):

 * status:  new => accepted
 * type:  defect => enhancement
 * component:  Admin Interface => Splash Screens


Comment:

 This has always been the intention. It has become more difficult now that
 we allow total customisation of the login interface.

 Original plan (when you couldn't customise the login) was to translate it
 like the rest of the interface. Now that you can customise it, we need a
 way to indicate what text can be translated (probably same was we
 currently do it in templates, with {t} {/t} tags), then we need a way for
 the hotspot owner to translate the text. I'm thinking that normal Gettext
 tools aren't going to cut it for the average hotspot owner.

 Any ideas on how we do this (from a GUI point of view)?

 The text that doesn't change should be easier to translate, which means
 the usermin section is easy to do.

-- 
Ticket URL: <http://trac.grasehotspot.org/ticket/68#comment:1>
GRASE Hotspot <http://grasehotspot.org/>
GRASE Hotspot bug tracker

Thread