Custom property text not to be translated?

[rakunavi]

Hello Tracker Support,

The Custom Property category of Document Properties has translated text in the following two places.

• DlgDocPrefs.Custom.note
• DlgDocPrefs.Custom.note2

• figure1.png
  
  
  figure2.png

However, it seems to me that the examples here of names that cannot be specified as property names should be left in the original text and should not be translated. It seems that most language files, including Japanese, have translated this part as well. Each is marked with a yellow marker in the figure above.

The following is a list of language files in which the above text has been translated and appears to need correction. If, as I believe, the above passage is the part that should not be translated, it might be a good idea to contact translators not only in Japanese, but also in the following languages

Code: Select all

Language			ISO Code
-------------------------------	----------
Arabic (Saudi Arabia)		ar-SA
Azerbaijan (Latin)		az-Latn-AZ
Czech				cs-CZ
Danish				da-DK
Finnish				fi-FI
French				fr-FR
Galician			gl-ES
Croatian (Croatia)		hr-HR
Italian				it-IT
Japanese			ja-JP
Korean				ko-KR
Lithuanian			lt-LT
Polish				pl-PL
Portuguese			pt-BR
Russian				ru-RU
Turkish				tr-TR
Ukrainian			uk-UA
Chinese (Simplified, China)	zh-CN

The following is a list of those that seem to have dared to leave the above passage untranslated, with full knowledge of the meaning of the original text. In other words, it is a list of language files that do not appear to need any correction at all.

Code: Select all

Language			ISO Code
-------------------------------	----------
German				de-DE
Spanish				es-ES
Hungarian			hu-HU
Dutch				nl-NL

Please give my regards to translators.
Thank you for your sincere support.

Best regards,
rakunavi

[TrackerSupp-Daniel]

Hello, rakunavi

I split this post out of the original thread as it seems to be a bit more of a situation that should be handled on its own, and is not a unique issue to the Japanese language as you report.

I will forward this to the Dev team to see what they think on it. If this is something that should not be translated, than it should be relatively simple for us to disable that object in the next translation tool, no need to reach out to individual translators, but that depends on if our devs think it should be disabled.

I will keep you posted if I hear anything from them on this.

Kind regards,

[rakunavi]

Hello Daniel, thank you for splitting up my post.

If, as I suspect, it is a part that should not be translated, then I think the solution you suggest is the best.
Please give my best regards to developers.

Best regards,
rakunavi

[TrackerSupp-Daniel]

Hello, rakunavi

That was a quick confirmation, you are correct, these strings should not be translated, the Team is aware and will look into removing them in the next release.

Kind regards,