Opened 18 years ago

Closed 17 years ago

Last modified 17 years ago

#3511 closed defect (fixed)

Better errormessage for missing unicodesymbols

Reported by: stacia@… Owned by: lasgouttes
Priority: high Milestone: 1.5.4
Component: general Version: 1.5.0svn
Severity: normal Keywords:
Cc: j.spitzmueller@…, ben.bob@…

Description

This problem is vaguely similar to #3043
however I would say it is more serious...honestly this bug renders the whole
Unicodesymbols file useless. I was told that the file is only used when the
encoding is *not* UTF8, and this was confirmed as I messed with the file and saw
no changes with my UTF8 file. However, changing to any encoding but UTF8 will
give the error message about the text being the wrong encoding. This is wrong,
since the symbols in the file should be getting converted through
unicodesymbols. More information can be found on the mailing list and I will be
attaching an example I found there shortly.

Attachments (1)

unicode_failure.lyx (895 bytes ) - added by stacia@… 18 years ago.
a file that won't compile in lyx but should

Download all attachments as: .zip

Change History (11)

by stacia@…, 18 years ago

Attachment: unicode_failure.lyx added

a file that won't compile in lyx but should

comment:1 by Georg Baum, 18 years ago

Milestone: 1.5.0

I see this, too. I'll have a quick look over the weekend, since it was probably
broken by me.

comment:2 by Georg Baum, 18 years ago

Summary: unicodesymbols file not working - makes you change to UTF8Better errormessage for missing unicodesymbols

This is now fixed: http://www.lyx.org/trac/changeset/18066
The unicodesmymbols file does work, but I entered the schwa command for the
wrong symbol (capital schwa, which is to my knowledge not in tipa), therefore
LyX could not find it. Now you should be able to enter all missing tipa
symbols :-)

You get a messsage on the console in cases like this:

Could not find LaTeX command for character 0x259.
LaTeX export will fail.

I believe that the error box that pops up is suboptimal (since utf8 does not
help in many cases), therefore I leave this bug open with changed summary.

comment:3 by younes, 18 years ago

What do you mean by "the error box that pops up is suboptimal"? Should we popup
an alert box or not?

comment:4 by Juergen Spitzmueller, 18 years ago

Milestone: 1.5.01.5.x

Seems we have to live with the errormessage for the time being.

comment:5 by Juergen Spitzmueller, 17 years ago

Keywords: fixedintrunk added

comment:6 by ben.bob@…, 17 years ago

Resolution: fixed
Status: newclosed

Fixed in branch (r22235) and previously in trunk.

comment:7 by Uwe Stöhr, 17 years ago

Cc: j.spitzmueller@… added

comment:8 by Uwe Stöhr, 17 years ago

Cc: ben.bob@… added

Is this bug eventually related to #4437?

comment:9 by Juergen Spitzmueller, 17 years ago

Milestone: 1.5.x1.5.4

comment:10 by ps@…, 17 years ago

Keywords: fixedintrunk removed
Note: See TracTickets for help on using tickets.