So here is the answer coming from Christian, it seems that lot of us are
affected by this bug. I hope we will have a rc4 where we will be able to
have it corrected, but I'm not sure however it's important enough to stop a
release. Anyway, please fix for translation asap as it's corrupting
documents, the sooner it's fixed, the better. Even if it doesn't make it in
4.1.0 (and it's not a production version), 4.1.1 is next month. What I
really don't like is the poor quality it renders for our translation.
-------- Message original --------
Sujet: Re: issue 67093: mix between Title and Header in various l10n
Date : Mon, 22 Jul 2013 21:39:25 +0200
De : Christian Lohmaier <email@example.com>
Pour : Sophie <firstname.lastname@example.org>
Copie à : libreoffice-dev <email@example.com>
Hi Sophie, *,
On Mon, Jul 22, 2013 at 4:47 PM, Sophie <firstname.lastname@example.org> wrote:
I've seen this patch
correcting this issue for French
But much more locale than French seems to be affected from the tests made
the FR team (PT, RU, IT, SP, CN...)
I did some grepping and applied some old translations from the time of
the 4.1 branch where the translations did differ between the two.
(13 languages) - but still 23 remain with the problem.
The issue here is that data are lost because the style structure is
Has it been modified also for the other languages, or should I send a head
up on the l10n list?
after the fix for french and https://gerrit.libreoffice.org/#/c/5038/
, the following languages still have the problem:
egrep -A3 "(STR_POOLCOLL_HEADLINE_BASE|STR_POOLCOLL_DOC_TITEL)"
*/sw/source/ui/utlui.po |grep msgstr | uniq -d
kl and ky don't have a translation. So that leaves 23 languages where
the strings are the same.
List of languages:
be bn-IN bn bo bs hi hr id kok ko mai mni mn my ne nn oc om or sa-IN sid tg
To unsubscribe e-mail to: email@example.com
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/l10n/
All messages sent to this list will be publicly archived and cannot be