For 1.4, I think most of our problems would be solved by using Tex::Encode.
We might want to consider this for 1.3 as well but should consider the issues regarding adding dependencies in a stable branch (given that this certainly affects all prior versions, I am thinking it should be fixed in 1.4 only)
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Also note that Tex::Encode handles UTF-8 for Latin-like languages (meaning that XeTeX becomes necessary only for things with fundamentally different character sets which cannot be managed as LaTeX ligatures).
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
hmm thinking... Wondering if it would be worth auto-discovering Tex::Encode and using it if it exists for 1.3 If so, should certainly put that change in early in the release cycle.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
For 1.4, I think most of our problems would be solved by using Tex::Encode.
We might want to consider this for 1.3 as well but should consider the issues regarding adding dependencies in a stable branch (given that this certainly affects all prior versions, I am thinking it should be fixed in 1.4 only)
Also note that Tex::Encode handles UTF-8 for Latin-like languages (meaning that XeTeX becomes necessary only for things with fundamentally different character sets which cannot be managed as LaTeX ligatures).
hmm thinking... Wondering if it would be worth auto-discovering Tex::Encode and using it if it exists for 1.3 If so, should certainly put that change in early in the release cycle.
LaTeX::Encode in its current version does not work. I have sent a patch to the author.
svn 6489