Internationalization of applications
Posted: Wed Apr 07, 2010 1:25 pm
This is an email thread between Chris Chapman and Mike Neilson about internationalization. I wanted to move it here for further discussion.
Mike
-----Original Message-----
From: Chris Chapman [mailto:chris.chapman@aggiemail.usu.edu]
Sent: Wednesday, April 07, 2010 11:08 AM
To: Michael Nielsen
Cc: Neal Midgley; Paul Wilhelm; Josh Cummings; rhusted@gmail.com
Subject: Re: Timeline Localization
Thanks, Mike
I wasn't very specific about my localization question. Let me try again. The
current db schema has a timeline table and an event table. Each of these
tables has an attribute that references a language table. The language table
has three attributes: CODE, NAME, DESCRIPTION. The plan has been to make these
timelines and events available in multiple languages. What I was wondering is
whether it is possible to take out the language table and use Java locale or
ICU4J for the language codes for a timeline or event, or if these libraries
are not robust enough for the Church's language requirements and we need to
implement and/or extend the ISO standards ourselves?
Thanks,
Chris
On Wednesday 07 April 2010 10:45:28 am Michael Nielsen wrote:
> Generally what we've done for localization is put the strings in a
> properties file and for database strings, we have a table with a language
> code and the strings located there.
>
> However, I need to verify that the new stack still recommends doing it this
> way. I was under the impression that things have changed. I'll check
> with the community guys today.
>
> I know Paul and Neal are still having trouble getting the app running. I
> haven't taken a look at it yet. I will have some time this weekend to look
> at it.
>
> I think going forward, we should at least take into consideration
> localization and build it with localization in mind.
>
> Neal's email is MidgleyNe@ldschurch.org
>
> -----Original Message-----
> From: Chris Chapman [mailto:chris.chapman@aggiemail.usu.edu]
> Sent: Wednesday, April 07, 2010 5:52 AM
> To: Paul Wilhelm; Michael Nielsen; Josh Cummings
> Cc: Robert Husted
> Subject: Timeline Localization
>
> I do have a question about localization. What is the stack standard for
> localization? I was not able to make it to the localization deep dive last
> week. (I wish I could have attended all of them!) From what I know, we can
> use a pre-built solution (like Java Locale or icu4j) or roll our own. I
> kind of hesitate to roll our own, unless that is common with Church
> applications. What is commonly done?
>
> Were any of you able to get the timeline app working with Oracle? Robert
> has updated the timeline-db project with an Oracle schema. It includes a
> language table with foreign key constraints, which is why I am asking
> about localization now. I don't know whether to start creating language
> objects or to just save a language code (from a Java library) to the
> database.
>
> Also, does anyone know Neal's email address? I couldn't seem to find it.
>
> Thanks,
> Chris
Mike
-----Original Message-----
From: Chris Chapman [mailto:chris.chapman@aggiemail.usu.edu]
Sent: Wednesday, April 07, 2010 11:08 AM
To: Michael Nielsen
Cc: Neal Midgley; Paul Wilhelm; Josh Cummings; rhusted@gmail.com
Subject: Re: Timeline Localization
Thanks, Mike
I wasn't very specific about my localization question. Let me try again. The
current db schema has a timeline table and an event table. Each of these
tables has an attribute that references a language table. The language table
has three attributes: CODE, NAME, DESCRIPTION. The plan has been to make these
timelines and events available in multiple languages. What I was wondering is
whether it is possible to take out the language table and use Java locale or
ICU4J for the language codes for a timeline or event, or if these libraries
are not robust enough for the Church's language requirements and we need to
implement and/or extend the ISO standards ourselves?
Thanks,
Chris
On Wednesday 07 April 2010 10:45:28 am Michael Nielsen wrote:
> Generally what we've done for localization is put the strings in a
> properties file and for database strings, we have a table with a language
> code and the strings located there.
>
> However, I need to verify that the new stack still recommends doing it this
> way. I was under the impression that things have changed. I'll check
> with the community guys today.
>
> I know Paul and Neal are still having trouble getting the app running. I
> haven't taken a look at it yet. I will have some time this weekend to look
> at it.
>
> I think going forward, we should at least take into consideration
> localization and build it with localization in mind.
>
> Neal's email is MidgleyNe@ldschurch.org
>
> -----Original Message-----
> From: Chris Chapman [mailto:chris.chapman@aggiemail.usu.edu]
> Sent: Wednesday, April 07, 2010 5:52 AM
> To: Paul Wilhelm; Michael Nielsen; Josh Cummings
> Cc: Robert Husted
> Subject: Timeline Localization
>
> I do have a question about localization. What is the stack standard for
> localization? I was not able to make it to the localization deep dive last
> week. (I wish I could have attended all of them!) From what I know, we can
> use a pre-built solution (like Java Locale or icu4j) or roll our own. I
> kind of hesitate to roll our own, unless that is common with Church
> applications. What is commonly done?
>
> Were any of you able to get the timeline app working with Oracle? Robert
> has updated the timeline-db project with an Oracle schema. It includes a
> language table with foreign key constraints, which is why I am asking
> about localization now. I don't know whether to start creating language
> objects or to just save a language code (from a Java library) to the
> database.
>
> Also, does anyone know Neal's email address? I couldn't seem to find it.
>
> Thanks,
> Chris