REMINDER: Release 3.3.4-rc1 from libreoffice-3-3 branch

l10n
#1

Hi,

please note that the commit deadline for 3.3.4-rc1 is on Monday, Aug 1,
2011.

The branch libreoffice-3-3-4 is going to be created the day after and
only commits with 3 reviewers will be allowed for that branch.

See also
http://wiki.documentfoundation.org/ReleasePlan#3.3_release
http://wiki.documentfoundation.org/Release_Criteria
http://wiki.documentfoundation.org/Development/Branches

Best Regards,
Petr

#2

Hi Petr,

2011.07.29. 12:03 keltezéssel, Petr Mladek írta:

please note that the commit deadline for 3.3.4-rc1 is on Monday, Aug 1,
2011.

I pushed the l10n fixes to libreoffice-3-3.

As there were very few fixes, may I ask you localizers, if you still
want to work on LibreOffice 3.3.x translations? I would like to remove
the files from Pootle, if there are no objections. Most of our users
will migrate to 3.4.x in the coming months and sooner or later we can
start to work on LibreOffice 3.5 strings.

Thanks,
Andras

#3

Þann sun 31.júl 2011 15:53, skrifaði Andras Timar:

I pushed the l10n fixes to libreoffice-3-3.

As there were very few fixes, may I ask you localizers, if you still
want to work on LibreOffice 3.3.x translations?

No objections from me (IS-team).

I would like to remove
the files from Pootle, if there are no objections. Most of our users
will migrate to 3.4.x in the coming months and sooner or later we can
start to work on LibreOffice 3.5 strings.

One thought; does anyone know whether *buntu LTS editions stick to a given version of LO or if they upgrade individual applications during the support cycle (3 years)?
We may have to take such long-term support into account.

#4

Hi Andras,

For pt we arent changing nothing, so its safe to delete 3.3 strings

#5

Hi Andras,

-------- Original-Nachricht --------

Von: Andras Timar <timar74@gmail.com>

As there were very few fixes, may I ask you localizers, if you still
want to work on LibreOffice 3.3.x translations?

Fine with me for DE :slight_smile:

I would like to remove
the files from Pootle, if there are no objections. Most of our users
will migrate to 3.4.x in the coming months and sooner or later we can
start to work on LibreOffice 3.5 strings.

Would like so see 3.5 strings rahter sooner than later :wink:

Regards,

André

#6

Hi Andras, all,

Hi Andras,

-------- Original-Nachricht --------

Von: Andras Timar<timar74@gmail.com>

As there were very few fixes, may I ask you localizers, if you still
want to work on LibreOffice 3.3.x translations?

Fine with me for DE :slight_smile:

+1 for FR

I would like to remove
the files from Pootle, if there are no objections. Most of our users
will migrate to 3.4.x in the coming months and sooner or later we can
start to work on LibreOffice 3.5 strings.

Would like so see 3.5 strings rahter sooner than later :wink:

+1 :slight_smile:

Kind regards
Sophie

#7

Hi,
2011.08.01. 13:19 keltezéssel, Sophie Gautier írta:

Hi Andras, all,

Would like so see 3.5 strings rahter sooner than later :wink:

+1 :slight_smile:

I understand your concern about translating large amount of new strings
in a short time. But as trends show, this is not the case. I compared
3.4.x and master strings today. Changed and new word counts are low
(<1000).

Best regards,
Andras

#8

Hello Andras

Hi Petr,

2011.07.29. 12:03 keltezéssel, Petr Mladek írta:
> please note that the commit deadline for 3.3.4-rc1 is on Monday, Aug 1,
> 2011.

I pushed the l10n fixes to libreoffice-3-3.

As there were very few fixes, may I ask you localizers, if you still
want to work on LibreOffice 3.3.x translations? I would like to remove
the files from Pootle, if there are no objections.

I have. Please -1.

Unless these strings takes too much space or performance on pootle I would
like to keep them there until we reach the last 3.3.x release, as I don't
want to bet on 3.4.x for enterprises right now, no matter we call it
enterprise-ready or enterprise whatever. 3.3.x will last more than we
expect. It is my choice at the moment for enterprises.

Most of our users
will migrate to 3.4.x in the coming months and sooner or later we can
start to work on LibreOffice 3.5 strings.

Thanks,
Andras

Thanks

#9

2011.08.01. 23:26 keltezéssel, Olivier Hallot írta:

Hello Andras

As there were very few fixes, may I ask you localizers, if you still
want to work on LibreOffice 3.3.x translations? I would like to remove
the files from Pootle, if there are no objections.

I have. Please -1.

Unless these strings takes too much space or performance on pootle I would
like to keep them there until we reach the last 3.3.x release, as I don't
want to bet on 3.4.x for enterprises right now, no matter we call it
enterprise-ready or enterprise whatever. 3.3.x will last more than we
expect. It is my choice at the moment for enterprises.

OK, fair enough. I'll keep it then.

Best regards,
Andras

#10

Hi,

-------- Original-Nachricht --------

Von: Andras Timar <timar74@gmail.com>

2011.08.01. 13:19 keltezéssel, Sophie Gautier írta:
> Hi Andras, all,

>> Would like so see 3.5 strings rahter sooner than later :wink:
>
> +1 :slight_smile:

I understand your concern about translating large amount of new strings
in a short time. But as trends show, this is not the case. I compared
3.4.x and master strings today. Changed and new word counts are low
(<1000).

Well, it's not my concern to translate lot's of strings in a short time
(we actually have enought tmie and not that many strings). It's more
about the "release early, release often model that should apply for
localized builds as well. Even if we do not provide fully localized
nightly builds, I'd like to do German builds from time to time just
to see if localization gets broken (currently 3.5 localizations are
badly broken but I cannot tell if it is just a problem of missing
translations or soemething else).

regards,

André

#11

Hi,

2011.08.02. 13:17 keltezéssel, Andre Schnabel írta:

Well, it's not my concern to translate lot's of strings in a short time
(we actually have enought tmie and not that many strings). It's more
about the "release early, release often model that should apply for
localized builds as well. Even if we do not provide fully localized
nightly builds, I'd like to do German builds from time to time just
to see if localization gets broken (currently 3.5 localizations are
badly broken but I cannot tell if it is just a problem of missing
translations or soemething else).

In the last few days I exported translations from Pootle, migrated them
to master, and today I pushed them to master. So from now you have more
or less up-to-date translations in master, at least they are much better
than they were.

I used a script to migrate from 3-4 to master, see below. Basically I
handled a few code changes, especially the image path changes in help so
there were less new/fuzzy strings. I'll create 3.5 projects in Pootle
when I'm back from vacation.

FYI, this is the migrating script I used. Feel free to suggest
improvements for the next round.

Best regards,
Andras

#!/bin/bash

WITH_POOR_HELP_LOCALIZATIONS="sh be ss tn te fa lv sa-IN ve af th ku or
sd br xh my ts sr ks sw-TZ pa-IN ast mr ar ta mni nr dgo brx uz ro mn rw
lt sat kok kn kk lo as cy ga st mai oc zu ml nso tt lb gd"
LANGS=$(ls -1 /home/timar/libreoffice-3-4/translations/source/)
PODIR=/home/timar/libreoffice-3-4/translations/source
POTDIR=/home/timar/libreoffice-master/translations/unxlngi6.pro/misc/pot

for i in $LANGS; do
echo "*** migrating $i ***"
cp -r $PODIR/$i $i.old
for j in $(find $i.old/helpcontent2 -name \*.po); do sed -e
"s|res/commandimagelist|cmd|g" <$j >$j.new;mv $j.new $j;done
sed 's/\\r//g'
<$i.old/instsetoo_native/inc_openoffice/windows/msi_languages.po

$i.old/instsetoo_native/inc_openoffice/windows/msi_languages.po.new

mv $i.old/instsetoo_native/inc_openoffice/windows/msi_languages.po.new
$i.old/instsetoo_native/inc_openoffice/windows/msi_languages.po
pomigrate2 -p -q --no-wrap --locale=$i $i.old $i $POTDIR
rm -rf $i.old
done

for i in $WITH_POOR_HELP_LOCALIZATIONS; do
rm -rf $i/helpcontent2
done

for i in `find . -name *.po`;do sed '/#~/,$d' <$i | sed 's/\\r\\n/\\n/g'