[texworks] german translation

[Thomas Floeren]

Hi Stefan,

thanks for taking in account my "efforts"
On Oct 8, 2009, at 5:23 PM, Stefan Löffler wrote:

> Hi Thomas,
>
> Thomas Floeren schrieb:
>> I've done a quick correction step on the file.
>> There have been a few semantical issues, lots of orthographical, and
>> some expression issues.
>
> Wow, thanks for all the effort!
>
>> Some (few) entries were not editable (File ... trans not readable).
>
> I don't quite understand how/which. If you could point me at a  
> specific
> entry (with the context and the source text)...
>
For example in the "ReplaceDialog" context the strings from "wrap  
around" to "Regular expressions".
They were grayed out and had the above mentioned comment. I'll send  
you a screenshot of this.

>> Please have a look on the file and tell me what you think.
>>
>> (The file is attached. In case the attachment is eliminated by the
>> list server, please give me an alternative upload address.)
>
> I actually did get the file via the mailing list. But never mind...
> I did have a look at it (well, rather at the changes you made), and I
> have a few points I'd like to comment on/put up for discussion here  
> (oh
> no, not again ;)):
>
> Unless noted otherwise, I'll always give "source" / "orig.  
> translation"
> / "your translation"
>
> 1) Lots and lots of great improvements. Some of those translations  
> were
> really bad in the original version ;).
>
Well that's your opinion, as you insinuated already

> 2) some typos in the comment to the translation of "regular  
> expression"
> (whichh, shouldnt) (duh ;))
>
Sorry for this. But when I'm typing comments I don't bother too much  
of orthographics ;)

> 3) "No recent search strings" / "Keine zuletzt verwendeten
> Suchausdrücke" / "Keine zuletzt verwendeten Suchen"
> I have no idea if the word "Suchausdrücke" exists officially or not.
> IMO, "Suchausdrücke" sounds better than "Suchen", though. Actually,  
> it's
> not the searches that are saved, it's the search strings. Comments?
>
Well, the point is simply that "Suchausdrücke" sounds like a really  
complicated thing;
but if you do a search for a simple word like "customise" to have it  
replaced by "customize",
this is - in my understanding - a simple "Suche". Check: What was the  
"Suche"? The Suche
was "custonise". What was the "Suchausdruck"? The Suchausdruck was:  
Just the searched word, no conditionals etc.
"Suche" imo is more adequat to represent the thing we are asking for:
The *last search event* (and not the last used search expression, may  
it has been a regex
or something differnet). No need to complicate the things artifically ;)

> 4) "Fit to Width" / "In Breite einpassen" / "In der Breite einpassen"
> I didn't like the original, but I'm not 100% comfortable with your
> suggestion, either. Somehow, it all cries "in welcher 'Breite'?" for  
> me.
> Maybe "An Fensterbreite anpassen"? Suggestions?
>
This sounds really great to me. Just one suggestion: "Fensterbreite",  
nothing more

> 5) I noticed you added a space in front of each "...". Is there a
> particular reason for this (style guidelines or something)?
>
Ahem, it is common understanding, I think. The dots have a specific  
signification;
they siginifate ellipsis, normally. So: if you want to indicate an  
ellipsis for a word
you add "..." to the word; if you want to indicate an ellipsis for the  
phrase
you add an " ..." to the phrase.
Example: You want to say "customizing", "customization", "customize"  
e.g. in one word
you would say "customi..."
But if you want to say "customize your outfit", "customize the  
application" etc.
in one phrase you say "customize ..."
The space makes the difference between word and phrase.
The ellipsis without space completes the word, the ellipsis with space  
completes the phrase.

> 6) "Tile" / "Kacheln" / "Verteilen"
> IIRC, the majority voted for "Kacheln" (see my summary post)
>
This is a rather complicated stuff. Stay with "Kacheln" if you like,
it's not bad. But just think of what is happening and you will
see that the windows are rather 'verteiled'. Why? "Kacheln" means
just to distribute all the windows in order to achieve a well  
distributed
Mosaik-like arrangement, all over the surface. This is not the case.

> 7) "&Wrap around" / "Am &Anfang fortfahren, wenn das Ende
> erreicht ist" / "Am &Anfang fortfahren"
> It's a lot better (more concise) now. Still, I'd like to make a call  
> for
> more suggestions because when searching backwards, it doesn't actually
> continue from the beginning. Ideas anyone?
>
When searching backwards, it should search backwards, no? Till the
start of the document, but no wrap? So, everything is ok(?)

> 8) "Subset" / "Untermenge" / "Subset"
> You said that this is a fixed term. I've never heard it before, so if
> someone could confirm this? To clarify: "subset" means that only some
> glyphs of a font are embedded in the document (instead of all the
> glyphs/the whole font). In fact, I'd favor the opposite version
> ("Komplett"), but that's not the way the program works, unfortunately.
>
I got you, but I think it doesnt matter. If the person in question knows
what "subset" means he/she will proceed accordingly.
If the person does not understand subset, he/she won't understand  
"Untermenge"
either. So: the term "Subset" is well defined and we shouldnt  
unnessesarily
occupie a still libre european term for this.

> 9) "Fit to Window" / "Einpassen" / "In Fenstergröße Einpassen"
> "Einpassen" should be lower case here, IMO.
>
Yes, of course, my fault

> 10) "When launched, show" / "Zeige, wenn gestartet" / "Anzeigen nach  
> Start"
> (in the context of the first tab of the prefs dialog) I'd like to  
> submit
> "Nach dem Start Folgendes anzeigen" for consideration.
>
I pass; not the time available at the moment; cannot localize the  
instance

> 11) "Editor defaults" / "Editor Standardeinstellungen" /
> "Standard-Editoreinstellungen"
> I'd like to submit "Standardeinstellungen für den Editor" for  
> consideration.
>
Well, hande it as you want, but in German you have to connect composed  
words
always with a hyphen (alternatinely you write them together). This is  
nothing new
of the reformed orthography, this has always been so. And btw it has  
its sense.

> 12) "Auto-hide output panel unless errors occur" / "Verberge Ausgabe,
> wenn kein Fehler auftritt" / "Ausgabe unterdrücken wenn kein Fehler
> auftritt"
> Technically, this isn't true. There is an output, and the  
> corresponding
> window is shown during the TeX run. It is just hidden afterwards, not
> suppressed.
>
Yu're right.

> 13) "Syntax coloring:" / "Syntax-Hervorhebung:" / "Syntaktische
> Hervorhebung:"
> I consider "Syntax-Hervorhebung" a kind of standard translation. But
> this may be due to my background in programming. Comments?
>
For me "Syntax-Hervorhebung" is also ok. But pay attention to the
orthography when implementing it ;

> 14) In the translation of "About ", you have what appears to be a
> unicode character for three dots, instead of "..."
>
dots or the appropriate UTF-8-character, this is up to the maintainer.
But I guess that you know that the UTF"threedots" are not equivalent  
to the ...

> 15) "No default binary directory found" / "Kein
> Standard-Binärverzeichnis gefunden" / "Kein Standard-Binary- 
> Verzeichnis
> gefunden"
> I agree that there is no such thing as a "Binärverzeichnis". However,
> I'd like to submit "Kein Standard-Programmverzeichnis gefunden" for
> consideration.
>
I fully agree :)


> 16) You should add yourself to the translators in the about dialog ;).
>
> Phew, sorry for the number of comments. But you asked for it ;).
>
I did ask for it? Well, add me to the list of correctors.

As I said already in the mail to you: The translation is quite good.
But there wasn't any reason to not eliminate the small issues.

To be sincere: As I saw the first (first to me) translation of this
handy program, with such hammers like "Übersetzen" and other less  
grave issuses
I told to myself:

Fine, now somebody has done a really simple editor with preview and all,
they are going to upload it to TeXlive09, it has chances to encourage  
people
to use ConTeXt/LaTeX.
... and then german users find this lousy localization.

But I was wrong


But nevertheless I think we should also pay attention to the "small  
details"
which make a good translation, in the end.

Thomas
> Cheers
> Stefan