LibreOffice 3.3 string freeze, Pootle update

l10n
#21

Hi Rimas,

2010.11.12 14:21, Rimas Kudelis rašė:

Hi all,

2010.11.12 11:33, Petr Mladek rašė:

I have just pushed the updated lo-build.pot and synced .po files in the
git repo. Please, take them.

André, could you please sync pootle once again?

I'm trying to do that now. Please do not work on those files for now.

Also, I'll try to merge those files with those we had during testing. Hope
there are no objections?

OK, it took me a rediculously long amount of time, but I think I finally
managed to trick Pootle into doing what it should. All files have been
updated from git, and then merged with what we already had in the
libo33_test project. Feel free to continue working on libo33 project, and
report any problems you may find.

As a precaution, I don't suggest using the Update from templates function,
because it seems to misbehave sometimes. Misbehaviour of that function is
exactly what took me so long. Also note that the calculations on the project
page are a bit off. The actual number of strings/words is 377/1877.

Thanks a lot for your work :slight_smile:

Kind regards
Sophie

#22

2010.11.11. 22:57 keltezéssel, Martin Srebotnjak írta:

done

Are you sure this new English entry is correctly formed:
<bookmark_value>colors; default colors; LibreOffice colors; Tango
colors</bookmark_value>

This will make a four level help index entry, all other index entries are
only single and double level ones.

Was your intention something like this:
<bookmark_value>colors; default
colors</bookmark_value><bookmark_value>LibreOffice
colors</bookmark_value><bookmark_value>Tango colors</bookmark_value>

It was my mistake. I pushed the correction to master.
http://cgit.freedesktop.org/libreoffice/help/commit/?id=8dec3bdd5df80e8c1acb01940df4b25d4077b64c
May I apply it to libreoffice-3-3 branch? Petr?

Also, some newly added extension descriptions include references to OOo
instead of LO (see LightProof description etc.).

This is interesting, because the source
(http://cgit.freedesktop.org/libreoffice/bootstrap/tree/scp2/source/extensions/module_extensions.ulf?h=libreoffice-3-3)
does not have the long description, it exists only in the sdf/po
template. You can replace OpenOffice.org to %PRODUCTNAME, that's all.

Thanks for your bug reports!
Andras

#23

Yeah, these descriptions were removed with the latest update of pot
files, so that error report might really be obsolete.

Lp, m.

#24

2010.11.13. 22:24 keltezéssel, Martin Srebotnjak írta:

This is interesting, because the source
(http://cgit.freedesktop.org/libreoffice/bootstrap/tree/scp2/source/extensions/module_extensions.ulf?h=libreoffice-3-3)
does not have the long description, it exists only in the sdf/po
template. You can replace OpenOffice.org to %PRODUCTNAME, that's all.

Yeah, these descriptions were removed with the latest update of pot
files, so that error report might really be obsolete.

Hmm, then lo-build.pot and lo-build.sdf are out of sync. :frowning:

Andras

#25

2010.11.11. 21:24 keltezéssel, Petr Mladek írta:

Andre Schnabel píše v Čt 11. 11. 2010 v 09:33 +0100:

Hi,

now that we have a code branch for LibreOffice 3.3 stable
release, we also have the (almost) final strings.

Petr is going to update the l10n templates and po files
with the new english strings today.

done

#:
instsetoo_native/inc_openoffice/windows/msi_languages/Control.ulf#OOO_CONTROL_124.LngText.text
msgid ""
"Build contributed in collaboration with the community by The Document "
"Foundation. For credits, see: http://www.documentfoundation.org"
msgstr ""

Link is wrong here. It should be:
http://libreoffice.org/credits.html

Andras

#26

In data giovedì 11 novembre 2010 22:02:15, Paolo Pozzan ha scritto:

In data giovedì 11 novembre 2010 09:33:32, Andre Schnabel ha scritto:
[cut]

> For you (translators) this would mean:
>
> - you may do your translation work for the final release
>
> at pootle from tomorrow on (I'll send an update to the list)
>
> - when your translation is done, please send a notice to the
>
> list, so that the modifications can be pushed to the code
> repository

[cut]

I think that a workflow similar to the OOo one would be more efficient: if
we have a deadline we can organize time much better and at the same time
I think a single big export would be much faster to manage than many
small exports. We will also avoid a LOT of messages on this list :wink: .
What do you think?

Paolo

Ciao Paolo,

ci penso io su Pootle?