View Single Post
Old 05-21-2011, 05:22 AM   #684
FethryDuck
Addict
FethryDuck will become famous soon enoughFethryDuck will become famous soon enoughFethryDuck will become famous soon enoughFethryDuck will become famous soon enoughFethryDuck will become famous soon enoughFethryDuck will become famous soon enough
 
FethryDuck's Avatar
 
Posts: 281
Karma: 520
Join Date: Nov 2010
Location: sometimes Norway, planet Earth
Device: Kindle3, DXG
Quote:
Originally Posted by reprep View Post

I have a turkish-english dictionary working perfectly well (with all the characters we have been talking about) for the original amazon firmware for kindle 3.1.
But i heard it is giving trouble for kindle dx and kindle 2.
Can that differentiate between the different "i" ? This is one problem which 8 bit unicode don't seem able to address ?

Quote:
Originally Posted by reprep View Post
we should let the duokan guys know this problem if they are not already aware. Is there anyone around here who knows chinese?
I have a more then a dozen bug-reports in their "bugzilla" on these issues, for several languages - and the Turkish issue is now included.

However - the German umlauts as well as characters in Norwegian, Danish, Swedish, French, Portogese, Spanish, Italian ... has mostly been fixed for utf-8 text files.
( read earlier postings in this thread ) However, their implementation cause conflicts with dictionaries, something I hope will be corrected.

Text files are the easiest, and the hope is that these solutions will migrate to the other formats. ( some have other ways this is corrected.. ) In other words, there has been a steady progress in .txt documents.

Most formats can be converted to utf-8 text files, and in many cases the results are good. This may be done with many programs, iconv, calibre, web based applications, scripts, etc. Simple scripts may do the job as well. But, this is of course not how it should be.

Last edited by FethryDuck; 05-21-2011 at 05:28 AM.
FethryDuck is offline   Reply With Quote