Hi Akira,
On Mon, Aug 4, 2014 at 11:42 PM, Akira Kakuto wrote:
> Thanks very much for your great work. r34836 is working fine.
r34831 caused regressions in xdvipdfmx ToUnicode generation, r34848 fixed that.
- Jiang
--
Subscriptions, Archive, an
Hi Jiang,
I will look into these crashes tonight if no one beats me to it.
Fixed as r34836.
Thanks very much for your great work. r34836 is working fine.
Akira
--
Subscriptions, Archive, and List information, etc.:
http://tug.org/mailman/
On Mon, Aug 4, 2014 at 11:22 AM, Jiang Jiang wrote:
> On Mon, Aug 4, 2014 at 10:52 AM, Akira Kakuto wrote:
>> Hi Jiang,
>>
>>
>>> Please let me know if there are any further issues.
>>
>>
>> I think r34832 is great. Thanks a lot.
>> However, if I use TrueType fonts in XeTeX (.ttf or .ttc), xdvipd
On Mon, 4 Aug 2014, Jiang Jiang wrote:
Thanks, we really should build up a better test system for these
common test cases. Khald and Peter, do you have any suggestions? In
specific we want better testing to CID fonts, non-CID OpenType/CFF
font and non-PostScript outline TrueType fonts.
Hi Jian
On Mon, Aug 4, 2014 at 10:52 AM, Akira Kakuto wrote:
> Hi Jiang,
>
>
>> Please let me know if there are any further issues.
>
>
> I think r34832 is great. Thanks a lot.
> However, if I use TrueType fonts in XeTeX (.ttf or .ttc), xdvipdfmx crashes
> with the message:
>
> otf_cmap>> Creating ToUnico
Hi Jiang,
Please let me know if there are any further issues.
I think r34832 is great. Thanks a lot.
However, if I use TrueType fonts in XeTeX (.ttf or .ttc), xdvipdfmx crashes
with the message:
otf_cmap>> Creating ToUnicode CMap for "c:/Windows/fonts/msmincho.ttc"...
I attach a ttctest.tex
On Mon, Aug 4, 2014 at 8:24 AM, Jiang Jiang wrote:
> On Mon, Aug 4, 2014 at 4:45 AM, Akira Kakuto wrote:
>> Hi Jiang ,
>>
>>
I have committed a better fix as r34805.
>>>
>>>
>>> Thanks a lot, Jiang. It works fine for the example.
>>
>>
>> However, unfortunately, invalid toUnicode problem fo
On Mon, Aug 4, 2014 at 4:45 AM, Akira Kakuto wrote:
> Hi Jiang ,
>
>
>>> I have committed a better fix as r34805.
>>
>>
>> Thanks a lot, Jiang. It works fine for the example.
>
>
> However, unfortunately, invalid toUnicode problem for non-CJK fonts,
> fixed by Khaled, has reappeared. I attach a s
Hi Jiang ,
I have committed a better fix as r34805.
Thanks a lot, Jiang. It works fine for the example.
However, unfortunately, invalid toUnicode problem for non-CJK fonts,
fixed by Khaled, has reappeared. I attach a sample.tex.
Thanks,
Akira
sample.tex
Description: Binary data
---
Hi Jiang,
Anyone feel like trying out the following patches?
https://gist.github.com/jjgod/0d4b6339d761a5423f82
Patch 1 will fix the ToUnicode generation for all non-subst glyphs in
a non-XeTeX generated dvi. In our case, non-subst glyphs are the
glyphs that are *NOT* changed by applying OpenT
On Sun, Aug 3, 2014 at 3:59 PM, Akira Kakuto wrote:
> Hi Jiang,
>
>
>> I have committed a better fix as r34805.
>
>
> Thanks a lot, Jiang. It works fine for the example.
Anyone feel like trying out the following patches?
https://gist.github.com/jjgod/0d4b6339d761a5423f82
Patch 1 will fix the T
Hi Jiang,
I have committed a better fix as r34805.
Thanks a lot, Jiang. It works fine for the example.
Thanks,
Akira
--
Subscriptions, Archive, and List information, etc.:
http://tug.org/mailman/listinfo/xetex
On Sun, Aug 3, 2014 at 12:10 PM, Jiang Jiang wrote:
> Possible fix: https://gist.github.com/jjgod/88bb45f2cc7711bf3fd0
I have committed a better fix as r34805. It still doesn't fix the
original warnings with ToUnicode map, which I will look into later.
But at least it doesn't regress.
- Jiang
On Sun, Aug 3, 2014 at 11:55 AM, Jiang Jiang wrote:
> Hi,
>
> On Sun, Aug 3, 2014 at 11:36 AM, Jiang Jiang wrote:
>> On Sun, Aug 3, 2014 at 11:28 AM, Jiang Jiang wrote:
>>> On Sun, Aug 3, 2014 at 11:26 AM, Akira Kakuto
>>> wrote:
Hi Khaled, Jiang,
I found that r34804 of dvipdfmx
Hi,
On Sun, Aug 3, 2014 at 11:36 AM, Jiang Jiang wrote:
> On Sun, Aug 3, 2014 at 11:28 AM, Jiang Jiang wrote:
>> On Sun, Aug 3, 2014 at 11:26 AM, Akira Kakuto
>> wrote:
>>> Hi Khaled, Jiang,
>>>
>>> I found that r34804 of dvipdfmx could not create a pdf
>>> for a simple vertical text by using
On Sun, Aug 3, 2014 at 11:28 AM, Jiang Jiang wrote:
> On Sun, Aug 3, 2014 at 11:26 AM, Akira Kakuto wrote:
>> Hi Khaled, Jiang,
>>
>> I found that r34804 of dvipdfmx could not create a pdf
>> for a simple vertical text by using SourceHanSansJP,
>> while r34711 of dvipdfmx could create a fine pdf
On Sun, Aug 3, 2014 at 11:26 AM, Akira Kakuto wrote:
> Hi Khaled, Jiang,
>
> I found that r34804 of dvipdfmx could not create a pdf
> for a simple vertical text by using SourceHanSansJP,
> while r34711 of dvipdfmx could create a fine pdf for the
> same text.
>
> I attach a file dvipdfmx-test.tar.g
Hi Khaled, Jiang,
I found that r34804 of dvipdfmx could not create a pdf
for a simple vertical text by using SourceHanSansJP,
while r34711 of dvipdfmx could create a fine pdf for the
same text.
I attach a file dvipdfmx-test.tar.gz which contains
(1) UniSourceHanSansJP-UTF16-H
(2) UniSourceHanSan
18 matches
Mail list logo
