Quote:
Originally Posted by JSWolf
What's going to happen to high-bit characters?
|
For the time being, exactly what is happening in v0.1. Chars like ΕΙηčθ, which are valid unicode, will be converted to random ascii chars. Mdashes and curly quotes will be unchanged
In the near-ish future see my above post, namely this bit:
Quote:
Originally Posted by jackie_w
I think refining the scrambling algorithm would be the next logical step once the above is nearer to satisfactory - which may take a little while yet.
|
At that point your views on the subject will be most welcome as long as you back them up with specific examples of how the existing algorithm is failing.
One thing to bear in mind is that the calibre tools convert everything to unicode from the outset. For example, any named entities in the source book (e.g.  ), will not be present in the scrambled output. Whether this will confuse, compound or be totally irrelevant to the issue of high bits chars I'm really not sure.
In the meantime maybe you could do some tests with v0.1 to gather some helpful examples of precisely where things go wrong with the current setup. It's always easier to work with facts than vague what-ifs.