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
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 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
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
Turns out we've also been bit by this problem... please see my questions
below.
On 2014-08-04 01:55, Heiko Oberdiek wrote:
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
Turns out we've also been bit by this problem... please see my
questions below.
On 2014-08-04 01:55, Heiko Oberdiek wrote:
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 D
On 04.08.2014 19:50, Stefan Solbrig wrote:
>> Turns out we've also been bit by this problem... please see my
>> questions below.
>>
>> On 2014-08-04 01:55, Heiko Oberdiek wrote:
>>> On 04.08.2014 01:27, Gildas Hamel wrote:
I append the jpg file (tombe.jpg).
>>> The resolution data in tombe.jpg
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
Mike Maxwell (me) wrote:
I'm looking at one of our
jpgs in a text editor, and while I see the string "Exif" near the
top,
I don't see any jfif-like string.
Stefan Solbrig wrote:
You can find 'JFIF' of tombe.jpg at position 6, meaning, there are
six other bytes before the string.
OK, I can
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/
OK, I can see that 'JFIF' in the tombe.jpg file. But it turns out
it's not in my file at all, only the 'Exif' header is there. Our
sysadmin guys haven't installed the suggested exiftool tool yet;
presumably exiftool will be capable of *adding* the JFIF header
(which I gather should come b
2014-08-04 23:52 GMT+02:00 Stefan Solbrig :
>> OK, I can see that 'JFIF' in the tombe.jpg file. But it turns out it's
>> not in my file at all, only the 'Exif' header is there. Our sysadmin guys
>> haven't installed the suggested exiftool tool yet; presumably exiftool will
>> be capable of *addin
12 matches
Mail list logo
