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
>>>>>
>>>>
>>