On my Debian unstable system, odt2txt properly works with the attached
file.
With pt_BR.UTF-8, de_DE and de_DE.UTF-8 I can see Voß without any problems
(running both odt2txt odt2txt_bugreport_example.ods and odt2txt --raw
odt2txt_bugreport_example.ods).
With LC_ALL=C I see Voss instead Voß (but
** Package changed: ubuntu = odt2txt (Ubuntu)
--
tracker / odt2txt get stuck when OpenOffice file has German special character
https://bugs.launchpad.net/bugs/367170
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
I've something similar on two of the three computer I maintain that I've pass
to jaunty. The difference is that odt2txt process are more and more numerous
and quickly the only way to get back to the normal is :
pkill tracker-indexer
pkill odt2txt
I don't know how to find the name of the files
I too updated to Jaunty a few days ago. odt2txt uses 94% of CPU and
tracker-launcher 6% whilst getting stuck on an ods file. The load did
not alter much during this session and my poor little laptop fan was
whirring away in an attempt to prevent a meltdown.
This file is a converted xls containing
** Attachment added: odt2txt_bugreport_example.ods
http://launchpadlibrarian.net/25989468/odt2txt_bugreport_example.ods
--
tracker / odt2txt get stuck when OpenOffice file has German special character
https://bugs.launchpad.net/bugs/367170
You received this bug notification because you are a
