Hi!
Goran you don't have to create patch po file. I can put po files
directly to the git tree.
KAMI
2010-10-07 22:59 keltezéssel, Goran Rakic írta:
У чет, 07. 10 2010. у 21:25 +0200, Per Eriksso
n пише:
Can somebody with the appropriate rights please integrate these for us
? :-)
http://erinet.se/ooo-build-sv.rar
Hi Per,
It looks like you did not use the latest lo-build.pot POT file. When
merged there are still some messages not translated. You can get the
updated lo-build-sv.po from here:
http://libreoffice.rs/tmp/lo-build-sv.po.bz2
I can prepare the patch and send it to libreoffice devel list after you
r
update.
Cheers,
Goran
Here are the current stats:
$ msgmerge --previous ooo-build-sv.po lo-build.pot > lo-build-sv.po
.......................................................... Done.
$ pocount lo-build-sv.po
lo-build-sv.po
type strings words (source) words (translation)
translated: 279 ( 83%) 1187 ( 83%) 1059
fuzzy: 23 ( 6%) 54 ( 3%) n/a
untranslated: 32 ( 9%) 179 ( 12%) n/a
Total: 334 1420 1059
--
KAMI911Best regards,
Kálmán „KAMI” Szalai | 神 | kami911 [at]
gmail [dot] com
My favorite projects:
OxygenOffice Professional <http://ooop.sf.net/> - office suite - for ever
ybody | Magyarul <http://hun.sf.net/> - In Hungarian
Blog <http://bit.ly/10ucTR> | Support <http://bit.ly/eYZO6>
Follow me <http://bit.ly/gJuJZ>, if you can <http://bit.ly/kDocB>
--
To unsubscribe, send an empty e-mail to l10n+unsubscribe@libreoffice.org
List archives are available at http://www.libreoffice.org/lists/l10n/
All messages you send 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.