From: Nick Clifton <nickc@redhat.com>
To: Ulf Samuelsson <binutils@emagii.com>, binutils@sourceware.org
Subject: Re: [PATCH v4 0/6] ASCIZ Command for output section
Date: Tue, 14 Feb 2023 16:20:13 +0000 [thread overview]
Message-ID: <9e5e4394-1421-e1ba-910e-b02b3c22808e@redhat.com> (raw)
In-Reply-To: <fcba73a3-cb38-7290-cffb-2e51e6766c04@emagii.com>
Hi Ulf,
> One question:
> The lang_add_string contains an error message if the string does not fit into the allocated area.
> This will never get triggered by the ASCIZ command, since that will allocate the size of the string.
> If you specify a size to the ASCII command and then provide a longer string it will trigger.
Ah - you know that I mentioned that I had tidied up the code
a little bit ? Well the other area I tidied was the lang_add_string
function. I simplified it, removed the redundant size checking code
and string padding code, and changed the stacked if-statements into
a simpler switch-statement...
So currently there are no messages that need translation,
> There are no translations for the string at the moment.
> Will the linker output the English string, or what?
If a translation for a specific string is not available then it will
just be displayed as-is. So in this case the English version will be
used.
> What is the procedure to get a translation?
The hard way:
Create a new ld/po/ld.pot file and send it to the Translation Project
with a request for new translations:
https://translationproject.org/html/maintainers.html
The easy way:
Wait for the next official release of the binutils. As part of
the process for creating a release I take care of asking the Translation
Project to update the translation files.
Note - this does not mean that new translations will be created
for all supported languages. The translation project runs on a
volunteer basis and it is up the the volunteers to find time to
create new translations and/or update old translations.
> I can provide a Swedish translation at the least.
If you would like to volunteer some time to the Translation Project
I am sure that they would love to hear from you.
Cheers
Nick
prev parent reply other threads:[~2023-02-14 16:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-13 16:20 binutils
2023-02-13 16:20 ` [PATCH v4 1/6] Document the ASCIZ command binutils
2023-02-13 16:20 ` [PATCH v4 2/6] Add ASCIZ to NEWS binutils
2023-02-13 16:20 ` [PATCH v4 3/6] Add ASCIZ to testsuite binutils
2023-02-13 16:20 ` [PATCH v4 4/6] ldlex.l: Add ASCIZ token binutils
2023-02-13 16:20 ` [PATCH v4 5/6] ldgram.y: Add 'ASCIZ <string>' command binutils
2023-02-13 16:24 ` [PATCH v4 0/6] ASCIZ Command for output section Ulf Samuelsson
2023-02-14 10:16 ` Nick Clifton
2023-02-14 16:07 ` Ulf Samuelsson
2023-02-14 16:20 ` Nick Clifton [this message]
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=9e5e4394-1421-e1ba-910e-b02b3c22808e@redhat.com \
--to=nickc@redhat.com \
--cc=binutils@emagii.com \
--cc=binutils@sourceware.org \
/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).