Bug 200059 - kde-l10n-de error in kmix.po translation
Summary: kde-l10n-de error in kmix.po translation
Status: RESOLVED FIXED
Alias: None
Product: i18n
Classification: Translations
Component: de (show other bugs)
Version: unspecified
Platform: Gentoo Packages Linux
: NOR normal
Target Milestone: ---
Assignee: Thomas Reitelbach
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-07-13 18:21 UTC by Jochen S.
Modified: 2009-08-31 10:01 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
image showing line break between unit and percent sign of kmix' tooltip. (4.64 KB, image/jpeg)
2009-07-14 10:49 UTC, Jochen S.
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Jochen S. 2009-07-13 18:21:31 UTC
Version:            (using KDE 4.2.96)
OS:                Linux
Installed from:    Gentoo Packages

Hello,

there's a little error in the german translation of kmix.po at line 183. The correct line should read:
msgstr "Lautstärke bei %1%"
instead of
msgstr "Lautstärke bei %1 %"

That would prevent some ugly line breaks right in front of the percent sign.


Greetings
Jochen
Comment 1 Frederik Schwarzer 2009-07-14 10:17:14 UTC
In German there is a (small?) space between the value and its unit. That's why we put it there. In cases where a line break is possible, we have to be careful.
However, do you have a line break there or do you just think there might be one in certain cases?
For me there are much longer tooltips, that do not break.
If there is a line break, we could use  , if tooltips can handle that.
If it cannot, we should remove the space. :)
Comment 2 Jochen S. 2009-07-14 10:48:00 UTC
Indeed DIN 5008 states that there should be a small space between unit and number / group of numbers. And yes, unfortunately the kmix tooltip breaks the line between unit and the percent sign (image attached).

Greetings
Jochen
Comment 3 Jochen S. 2009-07-14 10:49:05 UTC
Created attachment 35307 [details]
image showing line break between unit and percent sign of kmix' tooltip.
Comment 4 Frederik Schwarzer 2009-07-14 11:22:01 UTC
Oh, I didn't know that "tooltip". For me it is still a small coloured stripe. ;)

I just tested an altered translation in openSUSE and saw that the tooltip used can handle html entities. We could change the string to "Lautstärke bei %1 %" then. Objections? Other ideas?
Comment 5 Jochen S. 2009-07-14 19:19:04 UTC
Hello,

(In reply to comment #4)
> Oh, I didn't know that "tooltip". For me it is still a small coloured stripe.

how is this thingy then called? 

> I just tested an altered translation in openSUSE and saw that the tooltip used
> can handle html entities. We could change the string to "Lautstärke bei
> %1 %" then. Objections? Other ideas?

Preferably a smaller blank should be used (though DIN 5008 allows to use a standard blank for word processing). What about unicode U+202F or U+2009 (NARROW NO-BREAK SPACE / THIN SPACE)?

Cheers
Comment 6 Frederik Schwarzer 2009-07-14 20:30:33 UTC
> > Oh, I didn't know that "tooltip". For me it is still a small coloured stripe.

> how is this thingy then called? 

That's not what I meant. :) It is only that I run KDE 4.2 here and here KMix still has these "normal" tooltips. I think the new fancy ones are still calles tooltip.

> > I just tested an altered translation in openSUSE and saw that the tooltip used
> > can handle html entities. We could change the string to "Lautstärke bei
> > %1 %" then. Objections? Other ideas?

> Preferably a smaller blank should be used (though DIN 5008 allows to use a
> standard blank for word processing). What about unicode U+202F or U+2009
> (NARROW NO-BREAK SPACE / THIN SPACE)?

Yes, using a unicode character might be better (more readable?).

However, Qt does not support the full range of UTF-8, so this will have to be tested. I could do that later today, maybe tomorrow.
Comment 7 z0idberg 2009-07-14 22:08:59 UTC
@Jochen

The DIN rules are, in my opinion, just a prostration in front of text applications which do not modernise.

They are designed for someone who writes in MS Word and has no idea about any typographic stuff.

So, imho, the correct, smaller, typographically correct space should be used. I don’t think it will pose any problems.

If QT has some problems with UTF-8 (but it uses UTF-16 internally?), it would be with the SMP, not the BMP. They are not needed for German, so I think it all comes down to the font... which supports it.


By the way, why are we talking in English about a topic which is _only_ for Germans?
Comment 8 Frederik Schwarzer 2009-07-16 12:16:27 UTC
Sorry, I cannot test it yet... stuff came into my way for the next few days.

We are writing in English because someone could come to the conclusion that this is a bug to be fixed in KMix. ;)
Comment 9 Frederik Schwarzer 2009-07-16 21:41:53 UTC
Well, I had some time after all. ;)

I object to using the unicode character directly because you cannot really distinguish it from the normal space.

I would insert the HTML entity   (Narrow No-Break Space) so that it is clear there is some special case there.

It works for the KMix case because the widget supports rich text. However, not all widgets do (I'd like to stand corrected) so we cannot just make that change globally.

So what do we do?
Comment 10 Frederik Schwarzer 2009-07-22 12:55:06 UTC
SVN commit 1000930 by schwarzer:

do not break between value and unit

BUG: 200059

 M  +2 -2      kmix.po  


WebSVN link: http://websvn.kde.org/?view=rev&revision=1000930
Comment 11 Frederik Schwarzer 2009-07-22 13:00:31 UTC
So, I put in the html entity   (Narrow No-Break Space) here preliminarily to fix this very visible issue. Further discussion welcome on the list.

Thanks, Jochen, for the report.
Comment 12 Frederik Schwarzer 2009-07-22 13:01:08 UTC
o.O ... and closing again
Comment 13 Frederik Schwarzer 2009-08-07 09:19:56 UTC
Reopen. The bug is not fixed. I suppose in my tests the line break was avoided due to the fact that I included a narrow space, which decreased the length of the string for a few pixel and made a line break unnecessary.

I will investigate further before 4.3.1.


(why is it only possibe to change reports to "unconfirmed"?)
Comment 14 Frederik Schwarzer 2009-08-07 09:20:44 UTC
(changing to new, since it is now available :/)
Comment 15 Frederik Schwarzer 2009-08-19 12:26:07 UTC
SVN commit 1013216 by schwarzer:

remove the space for now to avoid line breaks at that position

Unfortunately I had no time to look into this issue more closely so I
just remove the space for now to get rid of the line break. Feel free to
dig deeper. :)

CCBUG: 200059

 M  +2 -2      kmix.po  


WebSVN link: http://websvn.kde.org/?view=rev&revision=1013216
Comment 16 Thomas Reitelbach 2009-08-31 10:01:19 UTC
Fixed now. I inserted the correct non-breaking space Unicode-Character. BTW: I used the normal-width space because the narrow non-breaking space is too small for most fonts. The most correct Character „Thin space“ is not available as non-breaking variant.
We are now checking if we apply this fix to several places in our translation where similiar bugs could occur.

Thank you for your report.