Hi!

Try Document -> Settings... -> Language, uncheck "use language's default encoding", and then see if utf8 appears in the list of Encodings.

I must warn you that (a) I'm not using the Windows version, (b) I have no idea about Japanese, and (c) I'm not sure that switching to utf8 is really the correct thing to do --- with Hebrew, I find that utf8 doesn't help, rather I need to set the encoding to cp1255, so you may have to switch it to whatever encoding is correct for Japanese.

Hope this helps!
Dov

Stacia Hartleben wrote:
Hi, I just installed the LyX1.5.0 beta and I can't figure out how to
get the encoding working. I'm trying to do a document which has
Japanese text in it but it keeps telling me "change the encoding to
"utf8" but I don't know where to do that - help?

On 12/21/06, Niklas Huldén <[EMAIL PROTECTED]> wrote:

Uwe Stöhr wrote:
> [EMAIL PROTECTED] schrieb:
>
>>> I fixed some bugs and changed a lot in the installer, here's the
>>> changelog:
>>> https://developer.berlios.de/project/shownotes.php?release_id=11890
>> have other people been successful with this installer ?
>>
>> I tried the previous version, and the current one. But
>>  - lyx.bat just opens a dos-box, immediately closes it again and dies.
>>  - lyx.exe returns the spartanic error message:
>>   "This application has failed to start, because the applicatioon
>>    configuration is incorrect. Reinstalling the application may fix
>> this problem."
>
> Hmm strange. Are you on Win2000? It seems that there are two extra
> libraries needed that I didn't ship with the installer. The next
> version will have them included, so please test out the next version.
> I'll release it tomorrow or on Friday.
>
> regards Uwe
>
I can confirm this. Same symptoms on a new WinXPhome machine with the
installer from 19.12.

configure.py says this:
 >configure.py
Traceback (most recent call last):
File "C:\Program Files\LyX 1.4.3-5\Resources\configure.py", line 34, in ?
    def writeToFile(filename, lines, append = False):
NameError: name 'False' is not defined


Niklas H.



Reply via email to