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

Header Data

From: GRASE Trac <tr***c@grasehotspot.org>
Message Hash: 27be2a157f9390c40f552167934f2856844d1714ece5e72e17a9911ad452eb79
Message ID: <069.e3341d0e8e39bceeb02a1bfc4e8bc704@grasehotspot.org>
Reply To: <054.55d8f9545e45c0cec372ac698d73d302@grasehotspot.org>
UTC Datetime: 2012-03-15 17:44:16 UTC
Raw Date: Fri, 16 Mar 2012 00:44:16 -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:
---------------------------------+----------------------

Comment (by hans van de voorde):

 I think that the principle should be still the same. The fixed parts
 should be translated as normal. The Hotspot owner dependent data should be
 stored per language version and would be still the responsability of the
 Hotsopt owner. (in my company we were maintaining 12 language versions of
 our software. There was just one version and all the text's of forms and
 reports were storred in a oracle database. the user could in the login
 form choose his language from a dropdown box (from the list of available
 languages cq licenced/installed langage databases. Customer customized
 froms/reports could be storred in the same language database)(This was a
 clear and easy way to do it . Easy for the translators and for
 maintenance, and easy for us to charge per language)

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

Thread