On 15/03/2013 22:48, Michael Wiik wrote:
For legacy issues all our html is vanilla ascii. To find non-ascii my
workflow has been:
zap gremlins, replace with code
search for the resulting hex codes
use each in a find/replace to replace all such occurrences with their
mnemonic or numeric equivalent
Why preserve such a bad "legacy"? All you need to do is save the files
as UTF-8 and declare UTF-8 in the headers. The use of "mnemonic or
numeric equivalents" is absolutely unnecessary and often leads to quite
anomalous results, especially when multiple-byte characters are
involved. What you are doing is a quite unnecessary hang-over from the
1990s.
JD
--
--
You received this message because you are subscribed to the
"BBEdit Talk" discussion group on Google Groups.
To post to this group, send email to bbedit@googlegroups.com
To unsubscribe from this group, send email to
bbedit+unsubscr...@googlegroups.com
For more options, visit this group at
<http://groups.google.com/group/bbedit?hl=en>
If you have a feature request or would like to report a problem,
please email "supp...@barebones.com" rather than posting to the group.
Follow @bbedit on Twitter: <http://www.twitter.com/bbedit>
---
You received this message because you are subscribed to the Google Groups "BBEdit Talk" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to bbedit+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
