Bug 145514

Summary:	SL10.1-LOC-Linux-DE-Beta1-06/01/25 -Add Scanner _Untranslated text
Product:	[openSUSE] SUSE Linux 10.1	Reporter:	Thomas Casserly <thomasc>
Component:	Translations	Assignee:	Kerry OConnor <kerryoc>
Status:	VERIFIED FIXED	QA Contact:	Karl Eichwalder <ke>
Severity:	Normal
Priority:	P5 - None	CC:	davidbo, emmetw
Version:	Beta 1	Keywords:	German, L10N
Target Milestone:	Beta 5
Hardware:	Other
OS:	Other
Whiteboard:
Found By:	Localization	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---
Attachments:	Add_Scanner untranslated text

Description Thomas Casserly 2006-01-25 14:52:05 UTC

YaST control centre_ Add Scanner _Untranslated text
SL10.1
DE
Beta 1

Steps to reproduce:
Install Suse 10.1.
Open the K Menu and select the "System" option.
From the sub menu select the "YaST (Kontollzentrum)/ YaST (Control Center)"
option.

YaST control center launches.
Choose "Hardware" from the left hand pane, and click "Scanner"

Click the "Add / Hinzufugen" button.
Scroll from left to right on the "Scanner model and driver / Scanner-Modell-und -treiber" window.

Expected Result: Text should be translated.

Actual Result: A number of strings have untranslated text at the end. The untranslated text is in all cases enclosed in [ ] brackets

Comment 1 Thomas Casserly 2006-01-25 14:57:00 UTC

Created attachment 65005 [details]
Add_Scanner untranslated text

Comment 2 Kerry OConnor 2006-01-27 16:45:46 UTC

Hi Karl, should these messages be translated. They appear to be coming from "sane" files found in /usr/share/sane/descriptions/*.* ?

Comment 3 Karl Eichwalder 2006-01-27 17:35:43 UTC

thanks for tracking down the cause.  It's probably not that easy to fix it.  Re-assigning for evalution

Comment 4 Michael Gross 2006-01-30 15:47:20 UTC

The general rule is not to complain about _missing_ translations in the beta releases ;) Nontheless, we should ask the sane-maintainer.

Comment 5 Johannes Meixner 2006-01-31 08:43:19 UTC

The matching YaST source scanner/src/helps.ycp is:
----------------------------------------------------------------------------
// SelectModel dialog help 4/5:
// Add the following sentence to translations:
// Such comments are only available in English.
_("<p>
When additional comments are available, they are shown in square brackets.
</p>") +
----------------------------------------------------------------------------

I assume the translators didn't read the comment that
they should add a text like
"Such comments are only available in English."
to translations (of course for English it is not necessary).

The source is o.k.
Changed component to "Translation" and added Rebecca to Cc.

Comment 6 Karl Eichwalder 2006-02-03 16:17:17 UTC

Translators read comments only, if the text is dubious.  Thus it would be better to start the english message with an alert and throw it away at display time (all character up to "|"):

_("translation_comment_wanted|<p>
When additional comments are available, they are shown in square brackets.
</p>")

For now, Kerry, please make sure to "enlarge" the translations as explained by Johannes Meixner (c#5).

Comment 7 Rebecca Walter 2006-02-03 16:27:09 UTC

This is not acceptable. The translators need to read the comments as they can contain important information.  If they don't, there is a very high risk that they will seriously mess things up.

Changing the strings to contain the comments is not an option. It will result in broken translations and is too much work for the developers.

The developers and I will not accept blame for bad translations caused by translators not reading the comments that we work so hard to provide.

Comment 8 Karl Eichwalder 2006-02-06 07:45:35 UTC

I don't want you to change the strings to contain the comments (even if that's the way KDE works and will be supported by the forthcoming gettext tools).  We only have to add information to a small number messages, if something special is required in the translations (like "ASCII only", "more info only useful for certain languages", strings that are ambiguous and thus causing trouble in the translation memories).

Don't forget that translations are also human beings ;)

Comment 9 Rebecca Walter 2006-02-06 11:31:55 UTC

I think this would cause more problems than it is worth.  It would be better if it just were made clear to the translators that they ought to read the comments.  Comments also talk about things that shouldn't be translated, like commands that resemble a word.

If you want any consideration of this proposal, you would have to talk to emap and visnov, but I think it would create more confusion for everyone, increase the developer workload unfairly, and end up with more bug reports and questions than we have now.

Comment 10 Kerry OConnor 2006-02-10 12:10:14 UTC

I expanded the translation in the lefthand help text for all languages. e.g.
msgid ""
"<p>\n"
"When additional comments are available, they are shown in square brackets.\n"
"</p>"
msgstr ""
"<p>\n"
"Wenn weitere Kommentare verfÃ¼gbar sind, stehen sie in eckigen Klammern.\n"
"Solche Kommentare sind nur in Englisch verfÃ¼gbar."
"</p>"

scanner.**.po should be in for Beta 5.

Comment 11 Emmet Wildes 2006-03-22 14:41:43 UTC

Closing issue as fixed for German, Beta8.