Quote:
Originally Posted by Hitch
Well, this appears to be veering into whether translation supports or needs or requires something other than that which is needed or supported or required for original work...meh.
|
No my point was that when you translate something you are always going to be things that have to be adapted to work. The idea that "it's bad to use fonts because you can't translate a font to Chinese" is a ridiculous argument. I have no interest in commenting further about that because arguing that means you are arguing just for the sake of trolling...
Quote:
Originally Posted by Hitch
Well, "supports" is one of those vague, kinda-nice-to-hear words that doesn't really mean anything. "Supports" implies a level of maintenance, a reliability to the idea, that doesn't really exist. You can't ask KDP what fonts are "supported." For that matter, they can't even give you a comprehensive list that says which fonts are available on what devices.
|
"Supports", in this context, means simply that it has the ability to use. With the rest of my comment I made it clear that I consider it a developing thing, so as it works better now than it used to, I expect it'll work better in the future than it does now.
Quote:
Originally Posted by Hitch
MEH, maybe the Ben Franklins of the world printing their own stuff but the truth is, most authors don't know Times New Roman from Gill Sans, nor why they should and don't care. They ONLY seem to care about the font issue if/when it's something like this. And believe me, this is a conversation, about what fonts, for what layouts, etc. I've had a LOT. I won't even regale some of you with the requests I've had. I told my crew that if a book escapes from my shop with Comic Sans therein, they can commit me. (That's what this town needs; an uber-friendly drop-off committal spot...)
|
Most authors don't care. They don't need to. & no, this isn't a conversation about what fonts for what layouts, it's a discussion about "How to get embedded fonts to work on a Kindle." You're opinions on
IF they
should be used or not are not productive to this thread & are little more than trolling.
Quote:
Originally Posted by Hitch
Well...my concern is or would be, any book that needed that sort of verbiage infrastructure "support." My thinking is, the book--the BOOK--the writing by the author--not fripperies--should tell me what I need to know, about names, characters, who said what, the beats...to me, as a bookmaker, I would have technological and typographical concerns (especially in the eBook realm) around mixing that many main narrative fonts into the stew and as a reader, I would...well, it wouldn't be my cuppa.
|
See, you are making it clear you didn't read what I wrote because I have said
OVER & OVER that that is
in no way what I'm talking about. It's not changing the font every time someone talks, it is almost entirely the
same font
for a whole chapter. I'm done repeating myself, it's a change of author. It's like a family is telling the story of their adventures. Sometimes dad is telling the story, sometimes the daughter. You
can do this without fonts, but you severely loose nuances. With the fonts it's like you see the other font & the voice in your head changes. As this is written like personal accounts any over-narration takes you out of the story. You could say "Jessica takes the pen & takes over writing the story" but it's much more fluid to have the font change than a "Dad is that what you think happened? It wasn't like that at all, here let me tell this part" as that makes it a conversation between them not them telling you their story. It's rare that that's happening, like maybe 3 times in 20+ books.