From: Roland Illig <roland.illig@gmx.de>
To: Jens Remus <jremus@linux.ibm.com>, binutils@sourceware.org
Subject: Re: New German PO file for 'opcodes' (version 2.41.90)
Date: Wed, 17 Jan 2024 16:58:28 +0100 [thread overview]
Message-ID: <11eb3e3c-a90e-4cd1-9fc9-6a9ea447689c@gmx.de> (raw)
In-Reply-To: <51a0b9fb-684d-475c-8beb-6c18c79c94fb@linux.ibm.com>
Am 17.01.2024 um 10:52 schrieb Jens Remus:
> Am 16.01.2024 um 21:02 schrieb Translation Project Robot:
>> This is a message from the Translation Project robot.
>>
>> A revised PO file for textual domain 'opcodes' has been submitted
>> by the German team of translators. The file is available at:
>>
>> https://translationproject.org/latest/opcodes/de.po
>
> I noticed that the term "z/Architecture" has been translated to
> "z/-Architektur". It would be preferable not to translate this term
I fixed the German translation, just as you suggested. If you find more
typos or other mistakes, please tell me.
> Is there a way to mark or annotate terms within message texts as not to
> translate?
The developers could insert a /* TRANSLATORS: ... */ comment above the
line, relying on the translators to see this message. This often works.
If it doesn't, I'd use the placeholder variant you suggested. More
generally, I also recomment placeholders for messages that often repeat,
such as "option '%s' requires an argument", as this prevents the
translators from introducing typos in the option name.
Roland
next prev parent reply other threads:[~2024-01-17 15:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-16 20:02 Translation Project Robot
2024-01-17 9:52 ` Jens Remus
2024-01-17 15:58 ` Roland Illig [this message]
2024-01-18 11:25 ` Nick Clifton
2024-01-18 12:44 ` Jens Remus
2024-01-17 15:52 Translation Project Robot
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=11eb3e3c-a90e-4cd1-9fc9-6a9ea447689c@gmx.de \
--to=roland.illig@gmx.de \
--cc=binutils@sourceware.org \
--cc=jremus@linux.ibm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).