Opened 22 years ago

Closed 21 years ago

Last modified 21 years ago

#713 closed defect (fixed)

qlyxkeysym does not work properly with non-latin1 encodings

Reported by: levon Owned by: levon
Priority: high Milestone: 1.3.0
Component: frontend-qt2 Version: 1.3.0cvs
Severity: blocker Keywords: patch VERIFIED
Cc:

Description

need getISOEncoded to do something properly

Change History (9)

comment:1 by levon, 22 years ago

Milestone: 1.3.0

comment:2 by levon, 21 years ago

Severity: normalblocker

comment:3 by Lars Gullik Bjønnes, 21 years ago

I do not think that we can let this case be a blocker for 1.3.0.

We should probably document the limited usefullness of the qt frontend and
also flag a warning/error message if anyting other than latinX (x==1?) is
used.

When working towards we can change the innards of LyX so that we don't have to
use the latin1 stuff at all, and rather use unicode internally. (That should
help right?)

comment:4 by levon, 21 years ago

Milestone: 1.3.0

OK. Reset target. Still a blocker as a subset of users cannot use
Qt LyX (blocks testing)

comment:5 by levon, 21 years ago

Milestone: 1.3.0

My patch changes this so it works correctly for the user's
locale, but they cannot mix and match encodings (yet).

comment:6 by levon, 21 years ago

Keywords: patch added

get in

comment:7 by levon, 21 years ago

Status: newassigned

get in

comment:8 by levon, 21 years ago

Resolution: fixed
Status: assignedclosed

f

comment:9 by levon, 21 years ago

Keywords: VERIFIED added

mass verify. grep -v ApplesWin

Note: See TracTickets for help on using tickets.