Bug#404070: oowriter cannot open documents whose file name contains special chars
Package: openoffice.org
Version: 1:3.1.1-1~bpo50+1.321 (lenny-backports)
Followup-For: Bug #404070
I have a similar problem. Trying to open a OO document with special
characters in an encoding other than my systems encoding in konqueror
results in "/path/to/<file>.doc does not exist".
The Systems enconding is isolatin-15, the file i try to open has an utf-8
name.
Konqueror uses the bash script "/usr/bin/ooffice" to open OO documents.
/usr/bin/ooffice:
#!/bin/sh
/usr/lib/openoffice/program/soffice "$@"
This script again starts "/usr/lib/openoffice/program/soffice".
/usr/lib/openoffice/program/soffice:
#!/bin/sh
...
# execute soffice binary
"$sd_prog/$sd_binary" -nologo "$@" &
Both scripts come with openoffice.org-common. I switched to "debug" mode
(set -x) in /usr/lib/openoffice/program/soffice to figure out what happens.
When i open the file utf8-öäü.odt (german umlauts, encoded in utf8)
with konqueror, ~/.xsession-errors says
+ sd_binary=oosplash.bin
+ /usr/lib/openoffice/program/oosplash.bin -nologo -writer '/tmp/utf8-ö�?�?.odt'
+ trap 'kill -9 $!' TERM
That doesn't look good. This file in fact does not exist.
When i change "$@" to $@ in one or both of the start scripts, it works:
+ sd_binary=oosplash.bin
+ /usr/lib/openoffice/program/oosplash.bin -nologo -writer /home/felix/utf8-öäü.odt
+ trap 'kill -9 $!' TERM
So, it seems that while passing the arguments from script to
script the encoding gets broken.
--
Felix Botner
Reply to: