Character conversion: "—" --> "â€”" - Page 2

Valloric · 06-28-2010, 07:41 AM

This has been fixed and the fix will be in the next release.

nyrath · 06-29-2010, 02:41 PM

I recently had another similar problem, which was not Sigil's fault.
I imported a text file, and it was full of bizarre character. There was no BOM marker at the start of the text file, and translating the file into UTF-8 did nothing.

So I looked at one of the garbage characters with a hex editor, and did some research on Google.

As it turns out, the file was in this obsolete format called "Mac OS Roman" or "Macroman".

Lucky for me, Python comes with a codec that understands MacRoman. So I wrote a quick script that opened the file with codecs.open('myfile.txt', "r", 'mac-roman'), read it in, and wrote it out into an output file created with codecs.open('myfile_CLEAN.txt', 'w', 'utf-8') Problem solved.

Fabe · 06-30-2010, 10:44 AM

Quote:

Originally Posted by charleski

Sigil occupies a unique, and very valuable, position in the epub ecosystem.

Yes, ePub as ecosystem. I've been thrashing about in it with my hip-boots. I need to stand still and observe more. Thanks.

edella · 07-06-2010, 06:14 AM

Quote:

Originally Posted by Ivo

There are few minor things not work reporting, and given that it comes for free I certainly like it a lot.

Not quite free, if you make a donation.. .

FizzyWater · 07-08-2010, 04:12 PM

Quote:

Originally Posted by Valloric

This has been fixed and the fix will be in the next release.

Any idea when the next release will be ... uh ... released?

Valloric · 07-08-2010, 04:23 PM

Quote:

Originally Posted by FizzyWater

Any idea when the next release will be ... uh ... released?

Seeing as how I'll be going on a two-week vacation starting tomorrow and that there's quite a bit of work I want to include in the next release, I'd say about a month. Eyeball guesstimate.

FizzyWater · 07-08-2010, 04:38 PM

Quote:

Originally Posted by Valloric

Seeing as how I'll be going on a two-week vacation starting tomorrow and that there's quite a bit of work I want to include in the next release, I'd say about a month. Eyeball guesstimate.

Well, do enjoy your vacation! I wish they'd let me take two weeks in a row at work!

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
"Settings," then "311" - Int'l Kindle searches for wireless providers in the area	Dr. Drib	Amazon Kindle	2	08-28-2011 10:27 AM
Yep. It's official. Sony Reader has "ruined" books for me. A final "review."	WilliamG	Sony Reader	48	01-14-2011 03:49 AM
"Balanced copyright" and feedback from real people (not just corporate "persons")	llreader	News	16	02-15-2010 08:27 AM
"Zeit-Odyssee"-Trilogie droht das "dunkle Turm"-Schicksal	ThR	E-Books	4	02-10-2010 05:18 AM
Question - Does iLiab have the "search" & "annotation, highlighting" features?	HiSoC8Y	iRex	5	07-01-2009 04:37 PM

06-28-2010, 07:41 AM	#16
Valloric Created Sigil, FlightCrew Posts: 1,982 Karma: 350515 Join Date: Feb 2008 Device: Kobo Clara HD	This has been fixed and the fix will be in the next release.

06-29-2010, 02:41 PM	#17
nyrath Addict Posts: 281 Karma: 52007 Join Date: Jun 2010 Device: nook	I recently had another similar problem, which was not Sigil's fault. I imported a text file, and it was full of bizarre character. There was no BOM marker at the start of the text file, and translating the file into UTF-8 did nothing. So I looked at one of the garbage characters with a hex editor, and did some research on Google. As it turns out, the file was in this obsolete format called "Mac OS Roman" or "Macroman". Lucky for me, Python comes with a codec that understands MacRoman. So I wrote a quick script that opened the file with codecs.open('myfile.txt', "r", 'mac-roman'), read it in, and wrote it out into an output file created with codecs.open('myfile_CLEAN.txt', 'w', 'utf-8') Problem solved.

Advert

Advert