Share

Vade Mecum

Tracker: Bugs

5 Cyrillic symbols are displayed incorrect - ID: 1566210
Last Update: Comment added ( flatworm )

I've created several plucker documents using Sunrise
Desktop. Document's language was russian, codepage:
win-1251.

That documents was displayed correctly on my palm T5
via plucker.

But during reading that documents on iPAQ 1950 (Windows
Mobile 5.0) via Vade Mecum 0.6.6.5 I've found that all
cyrillic symbols are displayed incorrect. Invalid
character encoding is used and instead of russian
symbols there are latin symbols with modifiers (rings,
dots, e.t.c.).

It looks like:
ÖÈÊ îòêàçàë â ïðîâåäåíèè ðåôåðåíäóìà î
òðåòüåì ñðîêå
Â.Ïóòèíà

It seems that instead of win-1251 another encoding is
used (win-1252 or iso-8859-1) and texts in plucker are
stored not in unicode, but in some national encoding.
But in Vade Mecum I didn't find any configuration
option to select text encoding.


Pavel Moukhataev ( pmoukhataev ) - 2006-09-27 08:38

5

Closed

Rejected

Nobody/Anonymous

Reader

None

Public


Comment ( 1 )




Date: 2006-10-05 21:25
Sender: flatworm

Logged In: YES
user_id=1350198

That's the problem with Sunrise, not with VM.
Please, read this:
http://www.mobileread.com/forums/showthread.php?t=5933
(You can read my comment (as "kostix") and the reply of the
Sunrise author).

Read this to get the idea behind PluckerDB and how is it
handled in VM:
http://svn.sourceforge.net/viewvc/*checkout*/vade-mecum/web/trunk/vm-charsets.html

The main idea: the only program that's known to be
rock-solid for encodings is the "official" Python distiller.


Log in to comment.

Attached File

No Files Currently Attached

Changes ( 3 )

Field Old Value Date By
status_id Open 2006-10-05 21:25 flatworm
resolution_id None 2006-10-05 21:25 flatworm
close_date - 2006-10-05 21:25 flatworm