public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Siddhesh Poyarekar <siddhesh@sourceware.org>
To: Benno Schulenberg <coordinator@translationproject.org>,
	"libc-alpha@sourceware.org" <libc-alpha@sourceware.org>
Subject: Re: libc-2.25.90.pot
Date: Wed, 19 Jul 2017 07:10:00 -0000	[thread overview]
Message-ID: <de9068e2-b4fd-e67d-2d43-5137e2a96822@sourceware.org> (raw)
In-Reply-To: <0961b9b1-b6b9-c0c9-bfe3-929ce522d7a8@sourceware.org>

Looping libc-alpha into the response as well; I just noticed that you
pinged here too.

Siddhesh

On Wednesday 19 July 2017 12:38 PM, Siddhesh Poyarekar wrote:
> On Monday 17 July 2017 01:31 AM, Benno Schulenberg wrote:
>> I see these changes when compared to the previous POT file:
>>
>> -msgid "\"%s\", line %d: "
>> +msgid "\"%s\", line %"
>>
>> -msgid " (rule from \"%s\", line %d)"
>> +msgid " (rule from \"%s\", line %"
>>
>> Are you sure these changes are intentional?  If yes, then maybe
>> they could use a translator hint, to say what is coming after the
>> last "%"?  Also, since those strings are not marked as c-format,
>> a malicious translator might be able to crash the relevant program
>> by putting in %tralala or something instead of %s?
> 
> It is a safe and intentional change; the full string is:
> 
> "\"%s\", line %"PRIdLINENO": "
> 
> where PRIdLINENO is PRIdMAX, which is a signed integer of maximum width,
> which could change for different architectures.  It is however a numeric
> type.
> 
> Would you like me to add a comment on top of that line to indicate that
> it is a numeric type?  I reckon the string itself is self-explanatory.
> 
> Siddhesh
> 

      parent reply	other threads:[~2017-07-19  7:10 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <8b9b4e60-f580-e56a-26bc-adb7192ba779@sourceware.org>
     [not found] ` <6e7f7602-3536-2edb-0cf4-e66a948fdb71@translationproject.org>
2017-07-18 17:08   ` libc-2.25.90.pot Benno Schulenberg
2017-07-18 19:02     ` libc-2.25.90.pot Adhemerval Zanella
2017-07-19  7:15       ` libc-2.25.90.pot Siddhesh Poyarekar
2017-07-19  7:33         ` libc-2.25.90.pot Benno Schulenberg
2017-07-19 13:28           ` libc-2.25.90.pot Adhemerval Zanella
2017-07-19 13:50             ` libc-2.25.90.pot Siddhesh Poyarekar
2017-07-20 11:17               ` libc-2.25.90.pot Siddhesh Poyarekar
2017-07-20 12:52                 ` libc-2.25.90.pot Adhemerval Zanella
2017-07-20 14:57                   ` libc-2.25.90.pot Siddhesh Poyarekar
2017-07-20 19:41                     ` libc-2.25.90.pot Paul Eggert
2017-07-25 10:23                       ` libc-2.25.90.pot Siddhesh Poyarekar
     [not found]   ` <0961b9b1-b6b9-c0c9-bfe3-929ce522d7a8@sourceware.org>
2017-07-19  7:10     ` Siddhesh Poyarekar [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=de9068e2-b4fd-e67d-2d43-5137e2a96822@sourceware.org \
    --to=siddhesh@sourceware.org \
    --cc=coordinator@translationproject.org \
    --cc=libc-alpha@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).