John Delacour johndelac...@gmail.com Mar 16 02:07PM writes:
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.
We're dealing with systems, not just web pages. Use of character entities
instead of high ascii reduced issues when processing our html files using
perl and PrinceXML. The team is used to using entities. I could agree it
may be time to revisit legacy workflows but our client determines our
priorities, not me.
The new Zap Gremlins / Replace with Code behavior seems presumptive. The
replacement of certain characters with vanilla ascii equivalents may well
be a useful option, but I would prefer at least the option to hex encode
*all* high ascii, as in, the previous behavior.
-Mike
--
--
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.
