[TF-dev] Re: [] Re: [[TF-dev]] #NOI18N in localization files

Hi Masaki,

Masaki Katakai wrote:
> Hi Dmitry,
>
> > Hm... can we file a enhancement for CTI to address that? :)
>
> I think we can. I'll try to discuss with other localization team.
>
> >> For installer/nbi files, we can not comment out.
> > Is this due to the fact the installer/nbi are not IDE modules?
>
> Yes, I heard it from you ;-) Missing entries in localized files
> will cause exceptions because installer/nbi is not using NbBundle.
>
> NbBundle will not cause exception when target entry is missing in
> localized file. English will be used instead.
> Is it possible to use NbBundle (or own class) in installer/nbi?
Well.. not really, but we have the same functionality in installer 
already (I fixed that right after 6.7 was released).
That is true for all .properties files except 
installer/mac/newbuild/Bundle.properties but there is no NOI18N comments 
there.
That is also not true for .js files - but there are not handled in CTI.


Dmitry
>
> Regards,
> Masaki
>
> 09.11.25 4:13 AM, Dmitry Lipin wrote:
>> Hi Masaki,
>>
>> Masaki Katakai wrote:
>>> Hi Dmitry,
>>>
>>> CTI does not support it. #NOI18N comment is special.
>> Hm... can we file a enhancement for CTI to address that? :)
>> Wouldn`t that be more reliable and straightforward than using our 
>> pre-processing and post-processing scripts?
>> Just thinking loudly.
>>> Also comments in .properties files are usually not
>>> visible on such translation tools.
>>>
>>> To avoid over-translation, most of #NOI18N keys in .properties
>>> files except installer/nbi are commented out.
>>> I'm doing some pre-processing before we upload files to CTI.
>>>
>>> For installer/nbi files, we can not comment out. 
>> Is this due to the fact the installer/nbi are not IDE modules? Or 
>> just some technical limitations in CTI?
>> Can I help somehow with that if that is in our pre/post processing 
>> scripts area?
>>
>> Dmitry
>>> So I have some post-processing scripts to revert them back to English
>>> if string is localized.
>>>
>>> Regards,
>>> Masaki
>>>
>>> 09.11.19 11:03 PM, Dmitry Lipin wrote:
>>>> Hi Petra,
>>>>
>>>> Is it a know bug that current OpenCTI interface does not skip 
>>>> strings in .properties files which are marked as #NOI18N and thus 
>>>> show them in as to be localized?
>>>> I see a bunch of such strings, at least, in 
>>>> NetBeans_6.8_properties_platform_javase | ru_RU / 
>>>> installer.engine.kit.
>>>>
>>>> Dmitry
>>>
>>>

-- 
Dmitry Lipin
NetBeans Installer Team
Sun Microsystems, Inc.
Phone EMEA/APAC x33354 AMER x7033354
Email: [email protected]