Quote:
Originally Posted by jmacg
OK – I inserted a plain text file into Sigil, rather than an HTML file. I had produced the file as plain text via Word and also via Editpad. But when I loaded either file into Sigil, all my special characters, like apostrophes and dashes, were represented as a white questionmarks on black triangles.
How do I stop this happening?
However – I tried cutting and pasting a few pages from Editpad into Sigil, and this preserved the apostrophes etc. I could try this for the full book, but I’d prefer to load the actual file.
The good news is that this short version produced an ePub file that behaved properly in an eBook reader – i.e. I could change fonts and font size. So that’s progress, and it certainly proves Valloric’s point that Word’s HTML export is not to be trusted.
So a plain text file will work, but I would lose special formatting like italics, and, far worse, I would lose indents on the first line of each paragraph.
|
PLAIN TEXT
You are confused if you think you can see any special formatting (in the editor)
, it uses just those 127 characters that appear in the ASCII chart .
Notepad is a plain text editor. No Bold, Italics, or underline...
As a matter, there is nothing about the file that even tells what
codepage was used to generate it.
HTML is a plain text based Mark-up language. (Word and others are marked up, just not in plain text). Only basic ASCII is permitted, all else is codeded to obtain.
As others suggested: xport as Filtered HTML, That uses an internal converter to translate internal markup to HTML. WYSI (in the source) not always WYG (in the rendered HTML)
