Change History (9)
comment:1 by , 22 years ago
Milestone: | → 1.3.0 |
---|
comment:2 by , 21 years ago
Severity: | normal → blocker |
---|
comment:3 by , 21 years ago
comment:4 by , 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 , 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).
Note:
See TracTickets
for help on using tickets.
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?)