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

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