You are not logged in.
Pages: 1
Hi,
Up to now I use poedit. But it reformats po files in a way that produces huge meaningless diffs. E.g. if I compare the Hg version of a po file to the version saved by poedit, I get such things:
[c]< #: index.cgi:227 index.cgi:381 index.cgi:404 index.cgi:714
---
> #: index.cgi:227
> #: index.cgi:381
> #: index.cgi:404
> #: index.cgi:714[/c]
or
[c]< msgid ""
< "Here you can configure a wired connection using DHCP to automatically get a "
< "random IP or configure a static/fixed IP"
---
> msgid "Here you can configure a wired connection using DHCP to automatically get a random IP or configure a static/fixed IP"[/c]
So my question is: what software do you use that doesn't alter po files in this way? Or is there a way to "canonicalize" the output of poedit into the format I find on Hg?
Offline
Poedit developer here. Current versions of Poedit (i.e. 1.8.6 at the time of writing) are much better at this and do not mangle files (with the possible exception of some Really Weird™ files, but as long as you use a formatting that GNU gettext tools can produce, you should be fine).
Offline
Hi vslavik, thanks for the info (looks like you registered just to answer my post, it's kind!).
Since the version in cooking is 1.4.6.1, I'm turning this thread into a support question: may someone update poedit to a more recent version?
Offline
Hi there!
I tried to compile the latest (1.8.6) poedit. So many changes, and as usually I started to determine package's build depends from scratch. I added: automake gettext asciidoc libxslt xmlto util-linux-getopt. I fixed "xmlto" package on the way, and now poedit builds its man file. OK.
[c]compile_rules()
{
./bootstrap &&
./configure \
--prefix=/usr \
--sysconfdir=/etc \
$CONFIGURE_ARGS &&
make &&
make DESTDIR=$DESTDIR install
}[/c]
Unfortunately, no luck in the "configure" stage:
[c]checking whether i486-slitaz-linux-g++ supports C++11 features by default... no
checking whether i486-slitaz-linux-g++ supports C++11 features with -std=gnu++11... no
checking whether i486-slitaz-linux-g++ supports C++11 features with -std=gnu++0x... no
checking whether i486-slitaz-linux-g++ supports C++11 features with -std=c++11... no
checking whether i486-slitaz-linux-g++ supports C++11 features with -std=c++0x... no
configure: error: *** A compiler with support for C++11 language features is required.[/c]
________
PS. I have managed to overcome this problem 
I added "gcc49" and "gcc49-lib-base" to the build dependencies, and exported the variable:
[c] export CXX=/usr/bin/i486-slitaz-linux-g++-49[/c]
(I hope this helps somebody in the similar problem.)
Dependencies search continues…
[c]checking for wxWidgets version >= 3.0.0 (--unicode)... no (version 2.8.12 is not new enough)[/c]
Need to update wxWidgets… Well, compiled version 3.0.2 about 50 minutes, done. I just falling asleep, continue tomorrow…
Offline
Hi Aleksej,
Thanks for your efforts. This problem with gcc is very strange. Here I have the gcc package version 4.6.3 and I routinely compile code with C++11 features. I use the -std=c++0x flag.
Offline
Hi llev,
I used only the simplest compilation rules: something similar to famous "configure && make && make install". All that strangeness about configure script. At least it tried your flag and it not worked for him.
Process continues. I made new "lucene++" package and separated "libboost-chrono" libs from "libboost-dev" package. That "lucene++" was compiled two hours on my netbook, after that I've found it installed by default into /usr/local instead of /usr %-) Seems better I'll work on Cooking server a bit, seems it 4 times powerful: lucene++ compiled in 32 minutes instead of mine 121.
Offline
Pages: 1
[ Generated in 0.015 seconds, 7 queries executed - Memory usage: 1.54 MiB (Peak: 1.77 MiB) ]