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

Dear Tadele!
Try using Poedit (Any version above 1.5 is fine).

This tool shows the misbehaving strings in red on top of the list after you
This way you can look at the strings that Virtaal will simply ignore upon
saving (Sorry Friedel ☺).

Another great tool I would suggest you to use (mainly in Ubuntu) is
After you edit the file just go to the command line and type "msgfmt -vco
/dev/null /path/to/your/file.sid.po" (replace the last part with the actual
file location).

If you don't have the msgfmt tool you'll have to install gettext using the
following command:
sudo apt-get install gettext
You will be asked for your password and then the tool will be installed so
you can use it.

Anyways I'm so glad to see this translation completing so fast.
Good job!

Yaron Shahrabani

<Hebrew translator>

On Wed, Jul 31, 2013 at 5:43 PM, Tadele Assefa <> wrote:

Dear Yaron,

I am still struggling with the 'invalid entry' message during LO build.
The followings are things I have done since you advised me last time:

1) corrected all 'critical errors' suggested
2) Tried to build and failed
3) Uploaded all files to Pootle, corrected all errors suggested by pootle
downloaded the translations and tried to build, not OK
4) Pulled the latest source code from git, switched to master and tried to
build, not OK

I did this on both Win and Ubuntu with same result. When I open the files
in Virtaal I cannot see any problem. What shall I do?


On Sun, Jul 28, 2013 at 11:11 AM, Yaron Shahrabani <>wrote:

I attached 2 files.

msgfmtlog.txt - Displays all errors, even the non critical one (these can
be fixed with recursive regex operation).

msgfmtcrit.txt - Displays only the critical errors (grep -v did the job).

The commands I used:
# recursively find all po files and send then to msgfmt for inspection
find . -name *.po -exec msgfmt -vco /dev/null {} \; >& msgfmtlog.txt
# filter out all the non critical messages (usefull only in this case)
and put them in a file
cat msgfmtlog.txt | grep -v 'initial\|translated' > msgfmtcrit.txt

Kind regards,

Yaron Shahrabani

<Hebrew translator>

On Sat, Jul 27, 2013 at 6:10 PM, Zolnai Tamás <>wrote:

Yes, gettext may help, to find the problem, but the "contains invalid
entry" message come from LO specific po checks. The LO used po has some
additional requirements to meet. If you use Pootle, than this problem don't
come up, but If you intend to use "Find and Replace" in a text editor than
you have to be sure that this replacing touch only the lines started with
"msgstr" and not others.

Best regards,

2013/7/27 Yaron Shahrabani <>

It's fairly simple, assuming you have the gettext tools installed, if
not just send me the file and I'll scan it for you.

With gettext the command would be: msgfmt -vco /dev/null base.po (in
the same dir of course)

Yaron Shahrabani

<Hebrew translator>

On Sat, Jul 27, 2013 at 11:37 AM, Tadele Assefa <>wrote:

Dear All,

After we did a 100%, we decided to change some of owr strings to a  new
terminology. As a result I did a "Find and Replace in All Files" using
Sublime Text 2 to change the terms.

After this I started building entire LO,(libreoffice-4-1 branch), but
failed to include the new terms saying invalid entry like
"git/libowin/translations/source/sid/scp2/source/base.po contains

What mistake did I do? How may i resolve this?
Tadele Assefa***

To unsubscribe e-mail to:
Posting guidelines + more:
List archive:
All messages sent to this list will be publicly archived and cannot be

LibreOffice mailing list

Tadele Assefa
Managing Director*

Cell: +25-911-84-13-84*
*Think Green – Please do not print this email unless you really need to*

To unsubscribe e-mail to:
Posting guidelines + more:
List archive:
All messages sent to this list will be publicly archived and cannot be deleted


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.