[PATCH 7 of 7] debugignore: make messages translatable

timeless timeless at gmail.com
Fri Jun 3 11:09:26 EDT 2016


On Fri, Jun 3, 2016 at 10:03 AM, FUJIWARA Katsunori
<foozy at lares.dti.ne.jp> wrote:
> At Tue, 31 May 2016 20:46:21 +0900,
> Yuya Nishihara wrote:
>>
>> On Tue, 31 May 2016 16:25:17 +0900, FUJIWARA Katsunori wrote:
>> > At Tue, 31 May 2016 01:00:35 -0400,
>> > timeless wrote:
>> > > FUJIWARA Katsunori <foozy at lares.dti.ne.jp> wrote:
>> > > >> Do we have a way to mark these output and untranslated instead?
>> > > >
>> > > > Would I send a patch for bulk changes, which replaces all "_()" in
>> > > > debug* commands to disable translation ?
>> > >
>> > > I'd rather it not be just removing _(), we should at least have something,
>> > > perhaps untranslated("").
>> >
>> > Oh, sorry. I just omitted 'with "()"' for 'replaces all "_()"' :-)
>>
>> Sounds good to me, maybe you know, except for "debuginstall".
>
> because "debuginstall" is referred by some messages/documents for end
> users, isn't it ?
>
> AFAIK, there are some other references to debug* commands below. We
> should except also these commands from target of bulk change,
> shouldn't we ? (even though only debugcreatestreamclonebundle has
> actual translatable messages in commands.py :-))
>
>   - "hg bundle" might show "use 'hg debugcreatestreamclonebundle'"
>   - "hg unbundle" might show 'use "hg debugapplystreamclonebundle"'
>   - "hg verify" might show 'run "hg debugrebuildfncache" to recover from corrupt fncache'

So. I think the real question we should ask is "why don't we want
debug messages translated?"

here are a couple of answers:
1. We want people sending English debugging to the list.
2. We don't want to waste the precious time of our localizers on
things that most users won't see.
3. Debug apis aren't part of our stable contract.

For #1, it's easy enough for people to be told to run the command
either w/ -T (if supported) or the env flag to get English output. (We
could even add a flag for this if we find it too hard to get people to
use the env var)
For #2, it should be easy enough to tell localizers that they don't
*have* to translate debug messages -- and if it isn't, I'm happy to
write scripts to split debug stuff into a separate .pot or something
to make it easier on them to decide what to prioritize.
For #3, that's ok, but why should that impact our choice about
translating the messages?

If you have a different answer to my "why" question, i'd like to hear it.


More information about the Mercurial-devel mailing list