[texworks] Updated German translation
fadisemmo at freenet.de
Sun Jan 31 16:12:02 CET 2010
Jonathan Kew schrieb:
> I've committed this update; thanks.
> You raise some good points here; I can see that these could be tricky to translate. Actually, I think this also highlights the fact that even in English, these are rather awkward terms that might be too jargon-ish. Perhaps we should consider whether there would be better terminology we could use in English, too.
> "Standalone Scripts" - your comment that they are not really "standalone" is equally true for English, obviously. I've always felt it was a bit of a cumbersome term, anyway. So what else could we call them? I wondered about "Menu Scripts" (because they're the ones that appear as menu commands) or perhaps "User Scripts" (because they're scripts intended to be run directly by the user). What do people think - would either of these be better? Any other suggestions?
"User Scripts" sounds best imo.
> "Hook Scripts" - the use of "hook" is rather technical jargon. I quite like "Extension Scripts" (translating back from your German suggestion), even though it's true that in some sense all scripts are extensions. Anyone else have comments?
Why not just call it "Extensions"?
> "Hook:" - at the moment, I can't think of a term I prefer here; even if we changed "Hook Scripts" I think we could still refer to place where they're called as being a "hook". Something more verbose like "Attachment point" doesn't really improve things, in my opinion. But again, comments welcome.
"Hook" sounds a bit strange but I can't think of a better name as of now.
> On 31 Jan 2010, at 13:32, Stefan Löffler wrote:
>> I've updated the German translation (see attachment). Most stuff was
>> pretty straight-forward. I'm not too sure I'm happy with three (rather
>> free) translations, though, so I'd like to put them here for general
>> 1) "Standalone Scripts"
>> My translation attempt is "Eigenständige Skripte", which is a bit weird,
>> since they are not really "eigenständig" in the sense that they are
>> independent of Tw altogether. However, it's actually a fairly literal
>> translation and alternatives like "Befehlsskripte" appealed to me even
>> 2) "Hook Scripts"
>> "Erweiterungsskripte". Again a bit of a mis-namer, since all scripts are
>> by definition extending ("erweitern") Tw. However, I didn't find a good
>> translation for "hook" in this context, so I figured that - contrary to
>> the standalone scripts - the hook scripts do in fact extend/modify the
>> core functionality of Tw (as opposed to providing additional, new user
>> 3) "Hook:"
>> Again, my translation attempt is quite free: "Anknüpfungspunkt:". What
>> is meant is the point in the code from which the script is called (this
>> labels a quite technical, internal, english name that is displayed in
>> the "Manage Scripts" dialog).
>> Does anyone have better suggestions or comments about this?
More information about the texworks