So you mean your original proposal was for 9.1.1 release? I thought the
target for opensourcing localization was v3 so I wasn't considering of
v2 based releases. They are pretty different in workspace structure.
> - How do we get MQ and webservices l10n files since they are 3rd party
> files?
Yes this is also my question. For 3rd party dependencies that aren't
localized, do we have to unbundle them and place files?
thanks,
Shinya
Georges MURR wrote:
> Hi Ogino-san,
> Thanks for the summary. it looks good to me.
> However, for the moment we are targeting salfin/9.1.1 release. The
> workspace tag is SJSAS91_FCS_BRANCH
>
> if you want to checkout the workspace, you can do the following:
> % cvs co -r SJSAS91_FCS_BRANCH appserv
> % cd appserv
> % maven bootstrap-all checkout build
>
> May be we can do the same approach you mentioned to do the sync for
> 9.1.1 workspace too.
> Since we already have the UBE workspace for 9.1, I have written a java
> program to create the l10n workspace using the files already present in
> UBE workspace.
> Please get a look at
> /net/dragon1.red.iplanet.com/export/home/georges/cvs_glassfish/glassfish/l10n
>
>
> The java file is CreateL10nWs.java and located under glassfish
> directory. it uses 2 files ube.lst and glassfish.lst
> ube.lst is the list of files in ube workspce
> glassfilsh.lst is the list of files un glassfish workspace.
> Both files are also located in the same dir as the java file.
>
> if you run CreateL10nWs under glassfish directory, it will create the
> l10n directory. it will find the location of a ube file in glassfish
> workspce and copy the EN file under l10n worspace from glassfish
> workspace, then copy corresponding l10n files from ube workspce.
> May be this will help us write the sync scripts because l10n directory
> contain the list of files that need to be localized.
>
> We have more issues to solve:
>
> - How do we get MQ and webservices l10n files since they are 3rd party
> files?
> - We need a script to build the l10n glassfish installer (Dinesh can
> help with this one)
>
>
> Regarding your questions:
>
> * Currently one -l10n jar per each module. Should that be per each
> locales?
> We should have only one l10n jar file for all modules and all
> locales. Currently we have 3 l10n jar files under lib directory:
> appservt-rt_<locale>.jar, webservices-rt_<locale>.jar,
> webservices-tools_<locale>.jar. With 7 locales, we are currently
> adding 21 jar files under lib directory. This will affect the
> performance of the appserver. we need to combine them to a
> minimum of 3 jar files appservt-rt_l10n.jar,
> webservices-rt_l10n.jar, webservices-tools_l10n.jar or may be to a
> single l10n jar file?
>
> * Can l10n includes and excludes list be owned by base module?
> Because original module owner knows it best.
> I think yes. We can write the initial ones, but after that core
> team need to maintain them
> * Other non properties files.
> we only have one xml file. The rest is admin-gui and upgrade-tool
> online help. We know where these files are located.
> * Is generate-sources (or resources) lifecycle appropriate?
> Can you explain please?
> * Nice to have some way of tracking localization status. e.g. Daily
> report on xx% localized in yy module, zz locale. or xx words not
> localized in ....
> I think it is a good idea
> * any thing else?
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> Shinya Ogino wrote:
>> Georges,
>>
>> I did some study on syncing files and building l10n modules yesterday
>> and summarised it in my blog. Please check and let me know how you think.
>>
>> http://blogs.sun.com/ogino/entry/how_should_we_localize_glassfish
>>
>> thanks,
>> Shinya
>>
>> Shinya Ogino wrote:
>>> Great, thanks.
>>> Including g11n_at_glassfish alias.
>>>
>>> Shinya
>>>
>>> Georges MURR wrote:
>>>> I agree, so let's go with
>>>> 10n/admin-gui/src/java/com/sun/enterprise/admin/resources/
>>>> Strings.properties
>>>> Strings_<locale>.properties
>>>>
>>>> I will write a program that will create the l10n workspace based on
>>>> the files that we currently have under UBE workspace. Since there
>>>> are more than 400 files, it will be a very tedious task to do it
>>>> manually.
>>>>
>>>>
>>>>
>>>> Georges
>>>>
>>>>
>>>>
>>>> Shinya Ogino wrote:
>>>>> Georges MURR wrote:
>>>>>> Hi,
>>>>>> Thanks for the feedback. According to your suggestion the l10n
>>>>>> directory structure that I proposed does not seem to be right.
>>>>>> Instead, we should have l10n directory structure the same as
>>>>>> glassfish wokspace.
>>>>> Yes. agree.
>>>>>
>>>>>> for instance, if a property file is located under
>>>>>> admin-gui/src/java/com/sun/enterprise/admin/resource/Strings.properties
>>>>>>
>>>>>> the file in l10n workspace should be located under
>>>>>> <locale>/admin-gui/src/java/com/sun/enterprise/admin/resource/Strings.properties
>>>>>>
>>>>> Yes I also think that will be one good option. In that case
>>>>> however, if someone in community wants to add an locale for the
>>>>> file, he has to create a new sub module (l10n/<locale>) and that
>>>>> can be some barrier...
>>>>> Or, if it can be like this,
>>>>> l10n/admin-gui/src/java/com/sun/enterprise/admin/resources/
>>>>> Strings.properties
>>>>> Strings_<locale>.properties
>>>>> shouldn't it be easier for contributors?
>>>>>
>>>>> Shinya
>>>>>
>>>>>>
>>>>>> This way we know where each file under l10n workspce is coming from.
>>>>>>
>>>>>> what do you think?
>>>>>>
>>>>>>
>>>>>>
>>>>>> Georges
>>>>>>
>>>>>>
>>>>>> Shinya Ogino wrote:
>>>>>>> Thanks Georges.
>>>>>>>
>>>>>>> > One question, how can we detect new files introduced by core team.
>>>>>>> > Should it be core team responsibility to update the sync script
>>>>>>> > described in section 6?
>>>>>>>
>>>>>>> If each module owners could place and maintain a list of files to
>>>>>>> be localized, say l10n.list, in their module directory, I think
>>>>>>> that's ideal. Because v3 seems much modular and workspace changes
>>>>>>> a lot from v2.
>>>>>>>
>>>>>>> And for the same reason, it is difficult to fix 2.1.1, 2.1.2, or
>>>>>>> 2.2 at this very early stage of v3. BTW, maven module basically
>>>>>>> generates one jar/zip from one module each so we may consider an
>>>>>>> option of holding multiple modules under l10n.
>>>>>>>
>>>>>>> Anyway, I have some idea for 6 so please let me try to prepare it
>>>>>>> by sometime next week.
>>>>>>>
>>>>>>> thanks,
>>>>>>> Shinya
>>>>>>>
>>>>>>> Georges MURR wrote:
>>>>>>>> Hi,
>>>>>>>> I have written a draft version of the l10n workspce and build
>>>>>>>> process for glassfish. Could you please review it and provide
>>>>>>>> comments.
>>>>>>>> Terena, could you please fill in info in section 5.
>>>>>>>>
>>>>>>>> One question, how can we detect new files introduced by core
>>>>>>>> team. Should it be core team responsibility to update the sync
>>>>>>>> script described in section 6?
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> Thanks,
>>>>>>>> Georges
>>>>>>>>
>>>>>>>
>>>>>
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: g11n-unsubscribe_at_glassfish.dev.java.net
>>> For additional commands, e-mail: g11n-help_at_glassfish.dev.java.net
>>>
>>
>