Thank you.
I'm not using JPluck, but Plucker Desktop. I don't see an output encoding option for it in Plucker Desktop, so I'll download JPluck and give that a shot.
Thanks! -Brian
David A. Desrosiers wrote:
...despite appearing normal on the web IE6, Firefox, and under OS X/Safari, on my Palm it gets artifacted characters in place of curly-quotes and "real" apostrophes (not double-primes and single-prime, respectively). He says he writes his pieces on a Mac, under Works or Word, which auto-curly-quotes, then cut-and-pastes it into Blogger. It displays fine in browsers, but Plucker displays something with a euro-denomination character in it.
You will need to make sure you specify that the input encoding is utf-8, and the output encoding is "whatever you want", which is typically going to be Windows-1251 (the encoding the Palm side uses).
I just plucked this with JPluck 2.1.6b, and specified 'utf-8' as the "Input encoding" (second tab), and left the output encoding at the default. It seems to work fine.
I've tried UTF-8, Mac, and default character sets for the plucked file.
I then tried to pluck it with the Python distiller, passing in the right charset, and it fails to parse it properly. I think that might be a bug.
d.
_______________________________________________ plucker-list mailing list [EMAIL PROTECTED] http://lists.rubberchicken.org/mailman/listinfo/plucker-list
_______________________________________________ plucker-list mailing list [EMAIL PROTECTED] http://lists.rubberchicken.org/mailman/listinfo/plucker-list
