After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 342895 - Problem with translating changed strings
Problem with translating changed strings
Status: RESOLVED FIXED
Product: dia
Classification: Other
Component: general
CVS head
Other All
: Normal normal
: ---
Assigned To: Dia maintainers
Dia maintainers
Depends on:
Blocks:
 
 
Reported: 2006-05-25 07:49 UTC by Clytie Siddall
Modified: 2006-05-25 20:09 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16



Description Clytie Siddall 2006-05-25 07:49:51 UTC
Today I went to update my translation of Dia, but a lot of strings have a changed format that doesn't work for my language.

po:165
Original:	⌘0	ToolsModify
Việt:	✘?	/Công cụ/Sửa đổi

The forward slashes which separate the two terms have been removed in the original string, and the English terms joined together. 

1. This does not work in my language, which is monosyllabic, and relies on each word being separate.

2. Because my language is monosyllabic, translated terms usually have more words than the original term. Where the original string here was two English words, now joined together, my translation is _four_ Vietnamese words, which I can't join together.

So what format is appropriate? I will have to separate the two terms somehow, but I don't know how that will affect the application. Are these strings displayed complete? Do they need to be short for some reason?

Probably the best result in my language would be to use an arrow, which implies the existing structure:

po:165
Original:	⌘0	ToolsModify
Việt:	✘?	Công cụ → Sửa đổi

but would that be OK in the Dia display?

I don't want to go ahead and update all those strings, until I know what format is appropriate. :S

If you do have a required length or format, it really helps if you include a translator comment. In the next release of gettext, there will be a separate context line:

msgctxt "context"
      msgid "original"
      msgstr "translation"

which will make all that so much easier.

I'll wait to hear from you before updating the translation.

from Clytie, Vietnamese translator
Comment 1 Hans Breuer 2006-05-25 08:08:59 UTC
Thanks for noticing. The "camel case" words like ToolsModify are not
to be translated/user visible. It is a bug if they are marked for
Translation. I think it is another unwanted side-effect of bug #340352
and not needed for the use of the GtkAction framework ...
Comment 2 Clytie Siddall 2006-05-25 08:12:44 UTC
Thanks for your prompt reply. :)

So do you want me to go ahead and update the file, ignoring those strings, or should I wait until the dia file is updated to not show those strings?

I can wait a couple of days if the file needs sorting out. :)

from Clytie, Vietnamese translator
Comment 3 Hans Breuer 2006-05-25 20:09:19 UTC
Should be fixed now, please report further issues.

2006-05-25  Hans Breuer  <hans@breuer.org>

	* app/interface.[hc] app/menus.c : rename ToolButton::menu_item
	to action_name. Don't mark action names for translation. It is not
	needed and some languages don't support CamelCase. Fixes bug #342895