Quote:
Originally Posted by Hitch
I haven't yet run into the unicode issue. Is it giving you agita on a specific item?
|
So I went back to reread the section yet again, and they have this sentence right after mentioning the two spaces:
Quote:
|
Originally Posted by AmazonKindlePublishingGuidelines
Use of any other space can break the selection, dictionary lookup, and line-wrap algorithms.
|
I don't have a Kindle on hand, can anyone test Search/Selection (Copy/Paste)/Dictionary when using Thin Spaces? It could be like some devices with Soft Hyphens. Theoretically it shouldn't break anything (and might look ok on the surface), but in reality, many devices/programs don't handle those characters properly in some sub-surface cases.
I must admit, I never looked too closely at actually using Thin Spaces heavily in ebooks (I only worked on one French Canadian book a few years back, where I first came across all that Thin Space intel).
Side Note: IF you want to read about the French punctuation spacing, here is some info:
http://unicode.org/udhr/n/notes_fra.html
https://wiki.openoffice.org/wiki/Non....28U.2B202F.29
https://www.cs.tut.fi/~jkorpela/html/french.html
and here was some Canadian French spacing rules (slightly different from normal French):
http://www.btb.termiumplus.gc.ca/tcd...ect17&info0=17
Quote:
Originally Posted by eggheadbooks1
And the KDP website, like the Publishing Guidelines, are "updated" by software engineers instead of proper writers.
|
LOL I wouldn't say that. If it was written by engineers it would REALLY get down into the nitty gritty (like none of my posts).
But try to explain something technical (like encoding) to your grandma. There is just no way!
Once you get a few paragraphs of technical words, their eyes glaze over.
Easier to just say: "Save it as ASCII/ANSI, if it doesn't work... not supported." Anything outside of (English letters + a few accented characters + most common symbols) turns to mush: "Well, if you keep having trouble, you can pay Createspace to create the file for you. *wink wink*"
Side Note: It reminds me of this topic on the LaTeX Stack Exchange, "How can I explain the meaning of LaTeX to my grandma?":
https://tex.stackexchange.com/questi...-to-my-grandma
Quote:
Originally Posted by eggheadbooks1
Should one change the defaults in Word to export to HTML as UTF-8 when following the workflow of Word to HTML to Sigil to ePub?
|
I am not familiar with the intricacies of Microsoft Word, but by default mine is set to save as UTF-8 (don't know if that was just a setting I set a very long time ago or what, I have 2010 installed if that means anything).
There is just absolutely no reason I can see why any sort of new documents should be non-Unicode in this day and age.