Thread: Those pesky <?> !
View Single Post
Old 01-01-2011, 01:30 AM   #14
DoctorOhh
US Navy, Retired
DoctorOhh ought to be getting tired of karma fortunes by now.DoctorOhh ought to be getting tired of karma fortunes by now.DoctorOhh ought to be getting tired of karma fortunes by now.DoctorOhh ought to be getting tired of karma fortunes by now.DoctorOhh ought to be getting tired of karma fortunes by now.DoctorOhh ought to be getting tired of karma fortunes by now.DoctorOhh ought to be getting tired of karma fortunes by now.DoctorOhh ought to be getting tired of karma fortunes by now.DoctorOhh ought to be getting tired of karma fortunes by now.DoctorOhh ought to be getting tired of karma fortunes by now.DoctorOhh ought to be getting tired of karma fortunes by now.
 
DoctorOhh's Avatar
 
Posts: 9,897
Karma: 13806776
Join Date: Feb 2009
Location: North Carolina
Device: Icarus Illumina XL HD, Kindle PaperWhite SE 11th Gen
Quote:
Originally Posted by p3aul View Post
At last I used --input-encoding "Windows-1252" on the command line to force the encoding to 1252. that was the only thing that would work. Even though FF "said" the encoding was 1252, it wasn't. I will do this from now on when I have an HTML file.

Thanks to all my helpers!
Paul
Automatically setting this encoding may cause more problems then it solves. Just make sure to check for proper quotes and apostrophes after each html conversion.
DoctorOhh is offline   Reply With Quote