Date: prev next · Thread: first prev next last
2013 Archives by date, by thread · List index


Hi :)
I like the idea of a veto but only if it's used for when a particular language has had it's 
translations broken or corrupted in some way.  Obviously the example of "French" was a bit daft 
because the French translation is always excellent.  However, it's difficult to see a good example 
of when a veto might be needed or might have been good.  You always seem to fix any problems.  
Perhaps having a formal veto option "written up" as a rule might encourage the very problem it's 
trying to forestall?
Regards from
Tom :)  





________________________________
From: Sophie <gautier.sophie@gmail.com>
To: Martin Srebotnjak <miles@filmsi.net> 
Cc: l10n@global.libreoffice.org 
Sent: Monday, 22 July 2013, 21:56
Subject: Re: [libreoffice-l10n] Fwd: Re: issue 67093: mix between Title and Header in various l10n


Le 22/07/2013 22:26, Martin Srebotnjak a écrit :
I do believe that l10n language leaders should have a right to veto
the release in certain language (i.e. yes, you can have 4.1.0, but
without French packages etc.).

Yes I agree with you

So the first release gets released, but no damage is made to a certain
language community.

Well, I don't like it in fact, I want my language to be part of the 
release party ;) So I prefer we be all together to release our version.

Kind regards
Sophie

Lp, m.

2013/7/22 Sophie <gautier.sophie@gmail.com>:

Hi all,
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.
Kind regards
Sophie
-------- 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 <lohmaier+libreoffice@googlemail.com>
Pour : Sophie <gautier.sophie@gmail.com>
Copie à : libreoffice-dev <libreoffice@lists.freedesktop.org>

Hi Sophie, *,

On Mon, Jul 22, 2013 at 4:47 PM, Sophie <gautier.sophie@gmail.com> wrote:


I've seen this patch
https://gerrit.libreoffice.org/4994

correcting this issue for French
https://bugs.freedesktop.org/show_bug.cgi?id=67093

But much more locale than French seems to be affected from the tests made
by
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
modified.
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
be/sw/source/ui/utlui.po-msgstr "Загаловак"
bn-IN/sw/source/ui/utlui.po-msgstr "শিরোনাম"
bn/sw/source/ui/utlui.po-msgstr "শিরোনাম"
bo/sw/source/ui/utlui.po-msgstr "ཁ་བྱང་།"
bs/sw/source/ui/utlui.po-msgstr "Naslov"
hi/sw/source/ui/utlui.po-msgstr "शीर्षक"
hr/sw/source/ui/utlui.po-msgstr "Naslov"
id/sw/source/ui/utlui.po-msgstr "Judul"
kok/sw/source/ui/utlui.po-msgstr "मथळो"
ko/sw/source/ui/utlui.po-msgstr "제목"
mai/sw/source/ui/utlui.po-msgstr "शीर्षक"
mni/sw/source/ui/utlui.po-msgstr "মিংথোল"
mn/sw/source/ui/utlui.po-msgstr "Гарчиг"
my/sw/source/ui/utlui.po-msgstr "ခေါင်းစဉ်"
ne/sw/source/ui/utlui.po-msgstr "शीर्षक"
nn/sw/source/ui/utlui.po-msgstr "Overskrift"
oc/sw/source/ui/utlui.po-msgstr "Títol"
om/sw/source/ui/utlui.po-msgstr "Mataduree"
or/sw/source/ui/utlui.po-msgstr "ଶୀର୍ଷକ"
sa-IN/sw/source/ui/utlui.po-msgstr "शीर्षकः"
sid/sw/source/ui/utlui.po-msgstr "Umo"
tg/sw/source/ui/utlui.po-msgstr "Сарлавҳа"
ug/sw/source/ui/utlui.po-msgstr "ماۋزۇ"

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
ug

ciao
Christian



--
To unsubscribe e-mail to: l10n+unsubscribe@global.libreoffice.org
Problems?
http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
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
deleted


-- 
To unsubscribe e-mail to: l10n+unsubscribe@global.libreoffice.org
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
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 deleted



-- 
To unsubscribe e-mail to: l10n+unsubscribe@global.libreoffice.org
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
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 deleted

Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.