On Saturday 21 October 2006 11:12, Georg Baum wrote:
>
> We have more filename encoding problems. Unless there is a very easy fix I
> vote against fixing this in 1.4. In 1.5 we should IMO output all filenames
> to the python script in utf8 encoding and declare that encoding in the
> script.
I ag
Am Samstag, 21. Oktober 2006 02:32 schrieb Uwe Stöhr:
> The problem is that the temporarily generated python files don't have a
> defined encoding. The encoding should be the one of the current OS
> setting. Bo, is this possible to have?
We have more filename encoding problems. Unless there is
Lars Gullik Bjønnes wrote:
Uwe Stöhr <[EMAIL PROTECTED]> writes:
| When I open a LyX-file that is in a path with spaces. I get the
| following error message when included images should be converted to be
| displayed:
|
| ---
| File "C:/Documents and Settings/usti/Local
| Settings/Temp/lyx_tmpd
Uwe Stöhr <[EMAIL PROTECTED]> writes:
| When I open a LyX-file that is in a path with spaces. I get the
| following error message when included images should be converted to be
| displayed:
|
| ---
| File "C:/Documents and Settings/usti/Local
| Settings/Temp/lyx_tmpdir2816a00220/lyxconvert0.py",
When I open a LyX-file that is in a path with spaces. I get the
following error message when included images should be converted to be
displayed:
---
File "C:/Documents and Settings/usti/Local
Settings/Temp/lyx_tmpdir2816a00220/lyxconvert0.py", line 11
SyntaxError: Non-ASCII character '\xfc' i
