Hello,

I'd like to come to a solution regarding the quotation style we are using in our German translation. At the moment, there are some files with Inch-signs (") as quotes and there are some using the typographically correct german quotation style: „Wort“.

I'd suggest using the correct style everywhere. For more information on typographically correct punctuation characters, read http://praegnanz.de/essays/typo-im-web-ein-sonder-zeichen-setzen

Regards,
Konstantin Käfer

Comments

kkaefer’s picture

kkaefer commented

I'd like some answers ;-)

Anonymous’s picture

Anonymous (not verified) commented

Well, you know my take on this: Yes, let's use typographically correct ones ...

Uwe Hermann’s picture

Uwe Hermann commented
Priority: Critical » Normal

Yep, go for it! I'll apply any patches I get. It's not a critical issue, though...

Uwe.

Frando’s picture

Frando commented
Status: Active » Fixed

seems that everyone agrees with it ..
so let's use „Wort“ from then on (ALT-0132 and ALT-0147 on win).

Uwe Hermann’s picture

Uwe Hermann commented
Status: Fixed » Active

OK, let's close this when the work is finished.

René Schwarz’s picture

René Schwarz commented

Wouldn't it be better if we use the appropriate HTML-Unicode notation?

F.e. instead of „ (ALT-0132) -> „

Possibly so there are a little less problems by the use of a incorrect charset on user-side. I could imagine that this could be a very relevant fact at multi-language-pages.

René Schwarz’s picture

René Schwarz commented

The example was mistyped, sorry.

F.e. instead of „ (ALT-0132) -> „

kkaefer’s picture

kkaefer commented

Then it would just be consequent to replace all Umlauts and the ß with the equivalents, too. -1 on this.

René Schwarz’s picture

René Schwarz commented

Yes, but this is not a really big problem, or?

I would agree to do these changes, so noone has got any efford. But I'm waiting until your accordance.

IMHO it is a good step to serve as a model for good translation style and internationalization facing a standards compliance code. Some more information about this way of programming can be found here:
http://de.selfhtml.org/html/allgemein/zeichen.htm
(but I'm sure you'll know that all).

kkaefer’s picture

kkaefer commented

Well, all modern browsers support Unicode. If a client does not support unicode, the content is also displayed incorrectly. It's not just the interface but the whole system that relies on Unicode. Also, translation would become a bit more difficult once you have to replace every special character.

René Schwarz’s picture

René Schwarz commented

Yes, this is true. But it could be done after proofreading before releasing. I think this search & replace takes not a long time....

kkaefer’s picture

kkaefer commented

You don't understand. It wouldn't make any sense to convert the translation strings to entities as the content of every Drupal site is still in UTF-8.

kkaefer’s picture

kkaefer commented
Status: Active » Closed (fixed)
brevity’s picture

brevity commented

Module "Markdown with SmartyPants" might be a good candidate to be tought language awareness so that "Wort" automatically gets its proper quotation marks!

http://drupal.org/node/9838
http://drupal.org/project/issues/marksmarty

kkaefer’s picture

kkaefer commented

brevity, for content you are right. But the discussion was about the user interface strings (the translation), not about user submitted content.

bluecafe’s picture

bluecafe commented

I am for the inch signs at all. I think the german "typically correct" styling looks simply ugly. My German keyboard doesn't even support it ... haha :)

joachim namyslo’s picture

joachim namyslo
Primary language German
Location Kulmbach 🇩🇪 🇪🇺
commented
Issue summary: View changes