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)
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 of
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:
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 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 Aug 3, 2014, at 6:27 PM, Gildas Hamel gwel...@ucsc.edu wrote:
% !TEX TS-program = xelatexmk
% !TEX encoding = UTF-8 Unicode
\documentclass[12pt]{article}
\usepackage{fontspec}
\usepackage{lipsum}
\usepackage{graphicx}
\begin{document}
\lipsum
\begin{figure}[h]
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
On 4 Aug 2014, at 00:48, Herbert Schulz he...@wideopenwest.com wrote:
On Aug 3, 2014, at 6:27 PM, Gildas Hamel gwel...@ucsc.edu wrote:
% !TEX TS-program = xelatexmk
% !TEX encoding = UTF-8 Unicode
\documentclass[12pt]{article}
\usepackage{fontspec}
\usepackage{lipsum}
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
On Aug 3, 2014, at 17:48, Elliott Roper elli...@yrl.co.uk wrote:
On 4 Aug 2014, at 00:48, Herbert Schulz he...@wideopenwest.com wrote:
On Aug 3, 2014, at 6:27 PM, Gildas Hamel gwel...@ucsc.edu wrote:
% !TEX TS-program = xelatexmk
% !TEX encoding = UTF-8 Unicode
On Aug 3, 2014, at 17:48, Elliott Roper elli...@yrl.co.uk wrote:
On 4 Aug 2014, at 00:48, Herbert Schulz he...@wideopenwest.com wrote:
On Aug 3, 2014, at 6:27 PM, Gildas Hamel gwel...@ucsc.edu wrote:
% !TEX TS-program = xelatexmk
% !TEX encoding = UTF-8 Unicode
On 04.08.2014 01:27, Gildas Hamel wrote:
I append the jpg file (tombe.jpg).
The resolution data in tombe.jpg are inconsistent:
* JFIF header: 72 DPI
* EXIF header: 300 DPI
Apparently XeTeX uses the EXIF header, whereas xdvipdfmx the JFIF header
(or vice versa).
It would be nice, if the TeX
13 matches
Mail list logo
