View Single Post
Old 03-14-2016, 01:55 PM   #10
KevinH
Sigil Developer
KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.
 
Posts: 8,859
Karma: 6120478
Join Date: Nov 2009
Device: many
Hi sdjskr,

Quote:
3. Are you seeing this in Code View or Book View or both?
In Book View
That is strange. CodeView input works perfectly but BookView editing has a cursor problem but only when "enter" is pressed, is that correct? Does switching from CodeView and back to BookView impact the problem?

Quote:
5. Are you saying you can see nothing in BookView if you do not add the xml:lang attribute or are you saying that some epub readers will not show the text without the xml:lang attribute on the html tag?

Yes I am talking about the final epub that is produced by the editor. Not the editor itself. Without the tag, nothing is showing on page when it should have shown all Korean paragraphs. Adobe Editions shows just blank pages. When it comes to English, it works fine
Then that is a bug in the Adobe Editions reader as only standalone html files need the xml:lang setting. What version are you using? Have you validated your epub in FlightCrew or epubcheck? Do you have the proper dc:language tag set in your OPF metadata?

KevinH

Edit:

Will you please open a blank epub in Sigil and go to BookView and start typing Korean and hit enter. Repeat as needed until the cursor disappears. Then immediately after the cursor disappears save the epub as is (do not move back to CodeView) and post that resulting buggy epub for me.

I should be able to open it and examine exactly what unicode character code is being generated when you hit enter by looking at it in a hex editor.

Thanks

Last edited by KevinH; 03-14-2016 at 02:18 PM. Reason: Added Request for a bug sample
KevinH is offline   Reply With Quote