On Thursday 02 June 2005 02.16, Eitan Gurari wrote:
_In its default configuration, TeX4ht tries to address a middle road
_with the objective to satisfy large assortment of users, uses, and
_tools. It is difficult to argue a proper way of behavior that will be
_acceptable to all. On the other
tex4ht makes use of unicode letter when this is not needed. This happens when
the latex code contains the sequence ff or fi and maybe other sequences.
For
example, here is a latex code and the html code generated by ht4tex and
htlatex. Note how
the sequence fi was translated to #xFB01;
tex4ht makes use of unicode letter when this is not needed...
In its default configuration, TeX4ht tries to address a middle road
with the objective to satisfy large assortment of users, uses, and
tools. It is difficult to argue a proper way of behavior that will be
acceptable to all. On the
Dear Professor Gurari,
thank you very much. It works like charm.
Rani
On 5/8/05, Eitan Gurari [EMAIL PROTECTED] wrote:
I modified the bugfixes distribution to provide reduced usage of
unicode values in iso-8859-1 output. The requests are to be made
through commands similar to
Dear Eitan,
Thanks for your work on this bug. A couple of things will slow down
the incorporation of these changes into Debian packages.
1. I am currently in transit so I won't really be able to download
the changed files right away.
2. Debian is currently in freeze pending a release so only
I modified the bugfixes distribution to provide reduced usage of
unicode values in iso-8859-1 output. The requests are to be made
through commands similar to
htlatex file iso8859/1/charset/less/!
or by modifying the charset paths in tex4ht.env accordingly.
Currently the only cases
Dear Eitan,
On Thu, May 05, 2005 at 11:34:56PM -0400, Eitan Gurari wrote:
Some background information regarding the problem.
Thanks for this info.
The unicode.4hf mapping currently doesn't allow creation of bitmap
fonts. For that to happen the tex4ht.c code needs to be modified to
provide
Kapil,
I agree the ligatures shouldn't be represented by bitmaps. To deal
just with those cases a nolig file can be a copy of
ht-fonts/iso8859/1/charset/unicode.4hf
stored at
ht-fonts/iso8859/1/charset/nolig/unicode.4hf
augmented with entries similar to
'#xFB01;' '' 'fi' ''
Dear Kapil,
My main goal in using tex4ht is to share documents with people who
do not use TeX, or process the documents by other programs. For this
purpose, the problem I have reported on is important as it prevents
such use. However, for the sake of publishing a document in html
format, this
Dear Rani,
On Thu, May 05, 2005 at 09:06:08AM +0300, Ran Gilad-Bachrach wrote:
My main goal in using tex4ht is to share documents with people who
do not use TeX, or process the documents by other programs. For this
purpose, the problem I have reported on is important as it prevents
such
Kapil,
Some background information regarding the problem.
In the `old days', tex4ht provided for a given (la)tex font different
htf fonts addressing different character sets. For instance, the
(la)tex cmr family of fonts had htf fonts under the unicode and
iso-8859-1 branches. In the iso
Package: tex4ht
Version: 20050402.1817-1
Severity: important
tex4ht makes use of unicode letter when this is not needed. This happens when
the latex code contains the sequence ff or fi and maybe other sequences. For
example, here is a latex code and the html code generated by ht4tex and
Dear Ran Gilad-Bachrach,
Thanks for your report.
On Wed, May 04, 2005 at 03:58:36PM +0300, Ran Gilad-Bachrach wrote:
tex4ht makes use of unicode letter when this is not needed. This happens when
the latex code contains the sequence ff or fi and maybe other sequences.
For
example, here is a
Dear Kapil,
Thank you for the prompt answer. I am not an expert in type-setting
however I have noticed two things which makes the conversion tex4ht
does problematic. First, when you open the html file using a browser,
the ff,fi,... combination look different than the rest of the text
(blurred).
Unfortunately, too many people complain about this and other similar
lack of font support problems by browsers for unicode symbols. I'll
try to `fix' the problem the coming weekend. -eitan
tex4ht makes use of unicode letter when this is not needed. This happens
when
the latex code
however I have noticed two things which makes the conversion tex4ht
does problematic. First, when you open the html file using a browser,
the ff,fi,... combination look different than the rest of the text
(blurred).
This looks like a browser bug to me, if a unicode char is generated for
the
Dear Ran Gilad-Bachrach,
Please see the enclosed mail from the author Eitan Gurari.
He is planning to provide a fix in the next version. For
the time being I think I will agree with Vassilii that this is
really wishlist rather than important (at least as a bug for
tex4ht---I do think it is up to
17 matches
Mail list logo
