How did you cook NL version?

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

How did you cook NL version?

FR web forum
Hello dev team
Read this: https://bz.apache.org/ooo/show_bug.cgi?id=127538
Why SV package is not correct compared with Pootle?
So bizarre!

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: How did you cook NL version?

Matthias Seidel
We should not wait until Pootle synchronisation.

It should at least be corrected in trunk, as this is such an obvious bug.

Matthias


Am 28.09.2017 um 18:54 schrieb FR web forum:

> Hello dev team
> Read this: https://bz.apache.org/ooo/show_bug.cgi?id=127538
> Why SV package is not correct compared with Pootle?
> So bizarre!
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
>


smime.p7s (5K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: How did you cook NL version?

Andrea Pescetti-2
Matthias Seidel wrote:
> We should not wait until Pootle synchronisation.
> It should at least be corrected in trunk, as this is such an obvious bug.

In case this is too brief:

1. Version 4.1.x only contains specific localization changes that were
explicitly requested (not this one). No Pootle synchronization was done;
not because of laziness, but because Pootle is aligned with the
trunk=4.2.x strings and a mass-import can't be done on 4.1.x due to
moved/changed strings.

2. Importing localization work from Pootle is one of the many good
reasons why we should focus on 4.2.0 as soon as 4.1.4 is out of the door.

Now, one could flag https://bz.apache.org/ooo/show_bug.cgi?id=127538 as
a 4.1.4 blocker, but blockers are judged on the severity and common
sense, so "fix a string that was also broken in 4.1.0, 4.1.1, 4.1.2,
4.1.3" is hard to justify as a top priority this late in the release
process.

"Fixing in trunk" as Matthias asks for can be done, but we will do it
anyway as part of the 4.2.0 release, since updating translations from
Pootle WILL be part of the release in that case, for the reasons
explained above.

Regards,
   Andrea.

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]