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


On Tue, Oct 26, 2010 at 3:01 PM, Cor Nouws <oolst@nouenoff.nl> wrote:
Cor Nouws wrote (26-10-10 14:45)

OK, should the pot-file start with
#. extracted from (input file name not known)

and the po-file with
# translation of ooo-build.nl.po to Dutch

Then I'll copypaste from my browser

$ msgmerge -U --previous lo-build-nl.po lo-build.pot

lo-build-nl.po:546:1: syntax error
lo-build-nl.po:559:1: syntax error
lo-build-nl.po:727:1: syntax error

using $ pot2po -t lo-build-nl.po -i lo-build.pot -o new.tmp
processing 1 files...
[###########################################] 100%

and opening in Gtranslator shows file with only 334 lines. Not what I would
expect.

Any hints, or someone able to merge and mail to me?

Wait, I'll give it a try
Sophie

thnx - Cor

--
 - giving openoffice.org its foundation :: The Document Foundation -


--
E-mail to l10n+help@libreoffice.org for instructions on how to unsubscribe
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





-- 
Founding member of The Document Foundation

--
E-mail to l10n+help@libreoffice.org for instructions on how to unsubscribe
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.