Inkscape

Hi,



> De : Leandro Regueiro <leandro.regueiro@...>
> Can you please change the comments before | in strings like this  one:
> 
> "Grid|_New"
> 
> to a msgctxt tag for not using "comment|" anymore  in Inkscape translation?
> 
> IMHO this leads to confusions and  mistranslations.

That's a planned task for 0.49 (or maybe 0.48.1). Gettext context macro (C_) 
support has been added to Inkscape very recently, and all the old-style context 
strings are going to be replace with it soon.

Instead of:

msgid "Grid|_New"

you'll see:

msgctxt "Grid"
msgid "_New"

Regards,
--
Nicolas

On Mon, Aug 16, 2010 at 12:46 PM, Nicolas Dufour <nicoduf@...> wrote:
> Hi,
>
>
>
>> De : Leandro Regueiro <leandro.regueiro@...>
>> Can you please change the comments before | in strings like this  one:
>>
>> "Grid|_New"
>>
>> to a msgctxt tag for not using "comment|" anymore  in Inkscape translation?
>>
>> IMHO this leads to confusions and  mistranslations.
>
> That's a planned task for 0.49 (or maybe 0.48.1). Gettext context macro (C_)
> support has been added to Inkscape very recently, and all the old-style context
> strings are going to be replace with it soon.
>
> Instead of:
>
> msgid "Grid|_New"
>
> you'll see:
>
> msgctxt "Grid"
> msgid "_New"

This is exactly what I want. These strings give bad results in
open-tran when you search by "grid".

Another thing to do is putting more comments, since Inkscape is not
the kind of software that much of us are used to translate, so a
little more comments in translations could help us a lot. A good
example is the "on" string reported in other recent thread.

Thanks and bye.

On Mon, Aug 16, 2010 at 2:46 PM, Nicolas Dufour wrote:

> That's a planned task for 0.49 (or maybe 0.48.1).

GIMP has a quite reasonable policy of not introducing changes to
translatable messages in point releases of a stable version. Can we
please follow it too?

Alexandre Prokoudine
http://libregraphicsworld.org

> De : Alexandre Prokoudine <alexandre.prokoudine@...>
> On Mon, Aug 16, 2010 at 2:46 PM, Nicolas Dufour wrote:
> 
> > That's a  planned task for 0.49 (or maybe 0.48.1).
> 
> GIMP has a quite reasonable  policy of not introducing changes to
> translatable messages in point releases  of a stable version. Can we
> please follow it too?

Yes, I foresee some difficulties managing different po files for the 0.48.x 
branch and for the trunk... (that's the reason why I wrote "maybe".) Thus 
limiting the existing 0.48.x pot file to what's already in it now sounds good 
for me. Of course, it would be open for translation updates, but not for new 
strings.
The main drawback is that it prevents us from adding new features if they add 
new strings.

Is there a link to this translation policy?
--
Nicolas

On 8/16/10, Nicolas Dufour wrote:

> The main drawback is that it prevents us from adding new features if they
> add new strings.

Ahem. Did we ever add features to point releases? :)

> Is there a link to this translation policy?

No, I don't have any. AFAIK it's a sort of unwritten rule in the lines
of "Hey, the strings freeze was there for a reason!" :)

Alexandre Prokoudine
http://libregraphicsworld.org

> De : Alexandre Prokoudine <alexandre.prokoudine@...>
> Ahem. Did we ever add features to point releases? :)

Some others do, and since Inkscape point releases are very rare, it's not that 
obvious.
Don't forget I'm still quite new to Inkscape ;)

Regards,
--
Nicolas

On Tue, Aug 17, 2010 at 7:53 AM, Nicolas Dufour <nicoduf@...> wrote:
>> De : Alexandre Prokoudine <alexandre.prokoudine@...>
>> Ahem. Did we ever add features to point releases? :)
>
> Some others do, and since Inkscape point releases are very rare, it's not that
> obvious.
> Don't forget I'm still quite new to Inkscape ;)

Of course changing the strings just before a release is a bad idea,
but you can change them just after the release (in trunk) to made
changes, the same way you add new strings, change other strings (maybe
due to bad english texts) or you delete old and unnecessary strings.

Hi,


> De : Leandro Regueiro <leandro.regueiro@...>
> Of course changing the strings just before a release is a bad  idea,
> but you can change them just after the release (in trunk) to  made
> changes

Done (revision 9722).

Regards,
--
Nicolas