Quote:
Originally Posted by Tex2002ans
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).
|
Actually, my experience with stuff written by software engineers is that they usually skip over what they think are obvious steps in the process. So they'll tell you to look in X folder on your computer, but it's actually found in a sub-folder of a sub-folder in X. Drives me nuts.
Quote:
Originally Posted by Tex2002ans
But try to explain something technical (like encoding) to your grandma. There is just no way!
|
I don't even bother. Last night my elderly mom (whom I take care of) asked me what I was doing. "Asking about Unicode characters in ebooks." "What's that?" "Never mind. Eat your dinner."
Quote:
Originally Posted by Tex2002ans
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*"
|
Yes, I think that is often Amazon's strategy. I notice it elsewhere, too.
Quote:
Originally Posted by Tex2002ans
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).
|
The default encoding in all versions of Word shipped in North America is Western European (Windows), aka Windows-1252. You have to deliberately change it to UTF-8 when saving if you want UTF-8. The default encoding in Notepad is ANSI.