Thank you for building this. I'm not familiar with w32tex, can users
replace the same file from their TexLive 2017 installation?
On Mon, Jun 12, 2017 at 3:31 PM, Akira Kakuto wrote:
> Hi Jiang,
>
>> So there might still be value to fix the ToUnicode map, don't you think?
ctually you can ignore rest of the change and only take the
is_PUA_or_presentation() change.)
On Mon, Jun 12, 2017 at 6:59 AM, Jiang Jiang <gzjj...@gmail.com> wrote:
>
> On Mon, Jun 12, 2017 at 12:38 AM Akira Kakuto <kak...@fuk.kindai.ac.jp>
> wrote:
>>
>
On Mon, Jun 12, 2017 at 12:38 AM Akira Kakuto
wrote:
> Dear Jiang,
>
> > There has been a report
> >
> > https://github.com/CTeX-org/ctex-kit/issues/286
>
> % XeTeX
> \XeTeXgenerateactualtext=1
> \font\1="Source Han Sans SC"
> \font\2="Source Han Serif SC"
>
Hi,
There has been a report
https://github.com/CTeX-org/ctex-kit/issues/286
(in Chinese)
in summary, fonts such as Source Han Sans/Serif encoded U+5B50 and
U+2F74 using the same glyph so that our reverse ToUnicode CMap
building seems to prefer U+2F74 which is not the expected result.
(U+2F74
Hi Jonathan,I suppose not everyone have a chance to build and try this yet. By
any chance you can provide a PDF test case demonstrating the feature? Then
perhaps more people can comment.- Jiang
_
From: Jonathan Kew
Sent: 星期四, 二月 18, 2016 7:00
On Mon, Apr 27, 2015 at 8:14 AM, Jiang Jiang gzjj...@gmail.com wrote:
Hi Simon,
On Mon, Apr 27, 2015 at 5:57 AM, Simon Cozens si...@simon-cozens.org wrote:
On 26/04/2015 23:18, Zdenek Wagner wrote:
I pushed a fix in r37053, both ITF Devanagari and Kohinoor Devanagari
works for me now.
I'm
Hi Simon,
On Mon, Apr 27, 2015 at 5:57 AM, Simon Cozens si...@simon-cozens.org wrote:
On 26/04/2015 23:18, Zdenek Wagner wrote:
I pushed a fix in r37053, both ITF Devanagari and Kohinoor Devanagari
works for me now.
I'm still seeing problems with Kohinoor Devanagari, even after the two
Hi Akira,
On Mon, Aug 4, 2014 at 11:42 PM, Akira Kakuto kak...@fuk.kindai.ac.jp wrote:
Thanks very much for your great work. r34836 is working fine.
r34831 caused regressions in xdvipdfmx ToUnicode generation, r34848 fixed that.
- Jiang
--
On Mon, Aug 4, 2014 at 4:45 AM, Akira Kakuto kak...@fuk.kindai.ac.jp 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
On Mon, Aug 4, 2014 at 8:24 AM, Jiang Jiang gzjj...@gmail.com wrote:
On Mon, Aug 4, 2014 at 4:45 AM, Akira Kakuto kak...@fuk.kindai.ac.jp wrote:
Hi Jiang ,
I have committed a better fix as r34805.
Thanks a lot, Jiang. It works fine for the example.
However, unfortunately, invalid
On Mon, Aug 4, 2014 at 10:52 AM, Akira Kakuto kak...@fuk.kindai.ac.jp 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
On Sun, Aug 3, 2014 at 11:26 AM, Akira Kakuto kak...@fuk.kindai.ac.jp 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
On Sun, Aug 3, 2014 at 11:28 AM, Jiang Jiang gzjj...@gmail.com wrote:
On Sun, Aug 3, 2014 at 11:26 AM, Akira Kakuto kak...@fuk.kindai.ac.jp 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
On Sun, Aug 3, 2014 at 11:55 AM, Jiang Jiang gzjj...@gmail.com wrote:
Hi,
On Sun, Aug 3, 2014 at 11:36 AM, Jiang Jiang gzjj...@gmail.com wrote:
On Sun, Aug 3, 2014 at 11:28 AM, Jiang Jiang gzjj...@gmail.com wrote:
On Sun, Aug 3, 2014 at 11:26 AM, Akira Kakuto kak...@fuk.kindai.ac.jp
wrote
On Sun, Aug 3, 2014 at 3:59 PM, Akira Kakuto kak...@fuk.kindai.ac.jp 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
On Mon, Jul 28, 2014 at 3:52 AM, Akira Kakuto kak...@fuk.kindai.ac.jp wrote:
Hi Khaled,
Let hope we have enough time before the next release to make sure it is :)
xdvipdfmx r34745 (after applying the patch by Jiang) sometimes
crashes at
--- cff.c.origMon Jul 28 08:50:32 2014
+++
Hi Akira,
On Mon, Jul 28, 2014 at 8:10 AM, Jiang Jiang gzjj...@gmail.com wrote:
Thank you Akira, I can reproduce this, will take a look.
https://gist.github.com/jjgod/cf39032b839bb3542107 should fix the
crashes for you.
- Jiang
On Mon, Jul 28, 2014 at 6:28 PM, Khaled Hosny khaledho...@eglug.org wrote:
On Mon, Jul 28, 2014 at 05:45:38PM +0900, Akira Kakuto wrote:
Hi Khaled,
This is a development tree after all, so bugs are to be expected. Lets
debug those issues first then decide what we want to do.
OK, agreed.
On Thu, Jul 24, 2014 at 8:28 PM, Khaled Hosny khaledho...@eglug.org wrote:
On Thu, Jul 24, 2014 at 07:18:10PM +0200, Jiang Jiang wrote:
On Thu, Jul 24, 2014 at 6:27 PM, Khaled Hosny khaledho...@eglug.org wrote:
On Thu, Jul 24, 2014 at 09:01:32AM +0200, Jiang Jiang wrote:
Hi,
On Thu, Jul
Since the old patches no longer apply, I updated
https://gist.github.com/jjgod/c1194a9b371848aaa746 with first patch
rewritten.
As you all can see, it is possible to do it in legacy dvipdfm-x code,
just more tedious, I'm not sure what benefit that gives. Then again, I
don't care that much as long
On Thu, Jul 24, 2014 at 6:27 PM, Khaled Hosny khaledho...@eglug.org wrote:
On Thu, Jul 24, 2014 at 09:01:32AM +0200, Jiang Jiang wrote:
Hi,
On Thu, Jul 24, 2014 at 8:07 AM, Peter Breitenlohner p...@mppmu.mpg.de
wrote:
On Wed, 23 Jul 2014, Jiang Jiang wrote:
Since Peter
Hi Khaled,
Since Peter is not responding, what do you think of this patch? Should
I go ahead and commit this to TeXLive repository? People had been
using it for a few days with various CID-keyed fonts and haven't
reported any more issue.
- Jiang
Hi Akira,
On Sat, Jul 19, 2014 at 1:29 AM, Akira Kakuto kak...@fuk.kindai.ac.jp wrote:
Dear Jiang Jiang,
In case you or anyone else are interested, I just posted two patches
to xdvipdfmx to fix this problem:
https://gist.github.com/jjgod/c1194a9b371848aaa746
Thanks very much.
I've
On Sat, Jul 19, 2014 at 1:40 PM, Akira Kakuto kak...@fuk.kindai.ac.jp wrote:
Dear Jiang Jiang,
But there are many warnings, probably for non-CJK fonts:
The warnings disappear if I apply an attached
patch: type0.c.diff.
I'm not sure if the last section is correct as it will very likely
Hi,
On Sat, Jul 19, 2014 at 3:12 PM, Akira Kakuto kak...@fuk.kindai.ac.jp wrote:
Dear Jiang Jiang ,
I will take a look at the warnings for non-CJK fonts.
Thanks.
In addition, I think it is necessary to refine for dvipdfmx.
The patched sources do not compile as dvipdfmx.
Right, I can
On Sat, Jul 19, 2014 at 4:11 PM, Akira Kakuto kak...@fuk.kindai.ac.jp wrote:
Dear Jiang Jiang ,
I will take a look at the warnings for non-CJK fonts.
If I use your
Type0Font_create_ToUnicode_stream(font);
for
case CIDFONT_TYPE2:
and the original
otf_create_ToUnicode_stream
On Sat, Jul 19, 2014 at 4:34 PM, Akira Kakuto kak...@fuk.kindai.ac.jp wrote:
Dear Jiang Jiang,
Yes, if you look at the logic there, it was trying to resolve the
ToUnicode CMap by first attempting to load SourceHanSansJP-UTF16-H in
texmf tree (with kpathsea), if this couldn't be found
On Sun, Jul 20, 2014 at 12:50 AM, Akira Kakuto kak...@fuk.kindai.ac.jp wrote:
Dear Jiang Jiang,
I updated the gist
(https://gist.github.com/jjgod/c1194a9b371848aaa746) again to fix the
following issues:
Thank you very much.
I think all is ok now. It compiles as the driver dvipdfmx
On Fri, Jul 18, 2014 at 10:52 AM, Dohyun Kim nomosno...@gmail.com wrote:
2014-07-18 0:00 GMT+09:00 Jiang Jiang gzjj...@gmail.com:
Hi,
I wonder if this has been discussed before but I have been wondering
if CID-keyed fonts are supported by XeTeX/xdvipdfmx at all.
Recent release of Source Han
Hi,
I wonder if this has been discussed before but I have been wondering
if CID-keyed fonts are supported by XeTeX/xdvipdfmx at all.
Recent release of Source Han Sans [1] brought up the question again.
If you install Source Han Sans CN Regular for instance, the following document:
On Wed, Jun 5, 2013 at 3:30 AM, Wilfred van Rooijen
wvanrooi...@yahoo.com wrote:
I prefer memoir. In fact, this is one of the things I remember from when I
was looking at gloss-japanese. the problem is that for instance the
chapter headings need to become 第1章, but most documentclasses
31 matches
Mail list logo