Hi Arnaud,
Am 06.03.2018 11:32 schrieb "Arnaud Bonatti" :
Hello everybody! As you already know, I’m trying these days to improve
the content of the “po” directory in the “dconf-editor” module I
maintain.
With the previous discussion in mind, let me summarize our rules:
Never touch po files, rea
Hi Mario,
2018-03-06 13:47 UTC+01:00, Mario Blättermann :
> Never touch po files, really never. […]
I don’t find a way to express how sad I am to see that it looks
impossible for devs to help translators in other way than adding
things to translate; and for maintainers to have a global control of
Hi,
2018-03-06 11:31 GMT+01:00 Arnaud Bonatti :
> Hello everybody! As you already know, I’m trying these days to improve
> the content of the “po” directory in the “dconf-editor” module I
> maintain. I must start by thanking again everybody for the work done
> there, it’s impressive, really! But m
6.03.2018 14:09 Arnaud Bonatti wrote:
> [...]
> 2018-03-06 13:47 UTC+01:00, Mario Blättermann :
> > Never touch po files, really never. […]
>
> I don’t find a way to express how sad I am to see that it looks
> impossible for devs to help translators in other way than adding
> things to translate;
2018-03-06 14:44 GMT+01:00 Ask Hjorth Larsen :
> [...]
> Changing the subject to something purely practical: Pruning/cleaning
> the po-files can probably be fully scripted, so there would be no harm
> in committing a script somewhere which does this, then sending bug
> reports to translation teams
2018-03-06 20:55 GMT+01:00 Rafal Luzynski :
> 6.03.2018 14:09 Arnaud Bonatti wrote:
>> [...]
>> 2018-03-06 13:47 UTC+01:00, Mario Blättermann :
>> > Never touch po files, really never. […]
>>
>> I don’t find a way to express how sad I am to see that it looks
>> impossible for devs to help translat
6.03.2018 21:33 Mario Blättermann wrote:
> [...]
> Unused strings can help to find a good translation for another string.
> Well, nowadays the GUI tools like Poedit do this work using their
> translation memory. But you must not expect that just everyone works
> with specialized GUI editors. Maybe
2018-03-06 17:33 GMT-03:00 Mario Blättermann :
>
> Unused strings can help to find a good translation for another string.
> Well, nowadays the GUI tools like Poedit do this work using their
> translation memory. But you must not expect that just everyone works
> with specialized GUI editors. Maybe
2018-03-06 21:54 GMT+01:00 Rafal Luzynski :
> 6.03.2018 21:33 Mario Blättermann wrote:
>> [...]
>> Who is "one" in this case? Who makes the decision that it's okay to
>> throw other's work away? [...]
>
> A project maintainer/developer? I don't know. I'm not telling that
> one should remove the fi
2018-03-06 20:55 UTC+01:00, Rafal Luzynski :
> Back about your idea: I'm afraid it does not make much sense because
> your removed strings would be restored in the next translation update.
What would be restored in next translation update would be *currently
used strings*, that are ok, with or wit
Sgrìobh Arnaud Bonatti na leanas 06/03/2018 aig 22:51:
>
> For every problem, there’s a code solution.
Actually, there's not. Adding a comments e.g. to tell translators
whether "View" means a verb or a noun would be a lot more useful - and
there's a case right here that can't have correct machine
I never talked about automatic generation of content. I talked about
manually fixing things in various languages, even without being part
of the respective translation teams. There are tenth of strings
(counting all languages) that doesn’t appear translated in the last
release, but that could be fi
On Tue, Mar 6, 2018 at 5:31 AM, Arnaud Bonatti wrote:
> – it’s quite impossible to use a tool like `grep` globally on
> translations to check for typos, as there are unused strings that
> makes the output unreadable.
Couldn't you just filter out po/ when using grep?
Thanks,
Jeremy Bicha
___
13 matches
Mail list logo
