Hi, - ConTeXt ver: 2008.06.22 17:38 MKII fmt: 2008.6.23 ( ctx minimal) - XeTeX, Version 3.1415926-2.2-0.999.1 (Web2C 7.5.6) When using (1) \setupinteraction[state=start, title={éèçàù}, subtitle={éèçàù}, author={éèçàù}, keyword={éèçàù}] the accented characters get al scrambled up in the pdf document properties fields while in the document itself all is ok. Qué passa ? (2) \pdfminorversion=5 (or whatever) gives ! Undefined control sequence. l.31 \pdfminorversion =5 ? ! Emergency stop. l.31 \pdfminorversion =5 What's the alternative ? Thanks, Alan
In addition to question (1)...
Compiling
\setupinteraction[state=start,
title=éèçàù,
subtitle=éèçàù,
author=éèçàù,
keyword=éèçàù]
with xetex doesn't work either - still scrambled. :O(
With texexec --autopdf --pdf, accented characters
are displayed correctly. It seems to be something with
xetex...
2008/6/27 Alan Stone
Hi,
- ConTeXt ver: 2008.06.22 17:38 MKII fmt: 2008.6.23 ( ctx minimal) - XeTeX, Version 3.1415926-2.2-0.999.1 (Web2C 7.5.6)
When using
(1) \setupinteraction[state=start, title={éèçàù}, subtitle={éèçàù}, author={éèçàù}, keyword={éèçàù}]
the accented characters get al scrambled up in the pdf document properties fields while in the document itself all is ok.
Qué passa ?
(2) \pdfminorversion=5 (or whatever) gives
! Undefined control sequence. l.31 \pdfminorversion =5 ? ! Emergency stop. l.31 \pdfminorversion =5
What's the alternative ?
Thanks, Alan
Re (1)
Would somebody please de so kind to compile this minimal example
with XeTeX and inform me what you see in the pdf's document
properties for: title, subject, author and keywords ?
The good looking characters or the messed up ones ?
--- begin code ---
\mainlanguage[fr]
\setupinteraction[
title=ÀÂÆ ÇÉÈÊË ÎÏÔŒ ÙÜŸ,
subtitle=àâæ çéèêë îïôœ ùûüÿ,
author=àâæ ÀÂÆ,
keyword=àâæ çéèêë îïôœ ùûüÿ]
\starttext
À Â Æ Ç É È Ê Ë Î Ï Ô Œ Ù Ü Ÿ
à â æ ç é è ê ë î ï ô œ ù û ü ÿ
\stoptext
--- end code ---
Thanks on beforehand,
Alan
2008/6/27 Alan Stone
Hi,
- ConTeXt ver: 2008.06.22 17:38 MKII fmt: 2008.6.23 ( ctx minimal) - XeTeX, Version 3.1415926-2.2-0.999.1 (Web2C 7.5.6)
When using
(1) \setupinteraction[state=start, title={éèçàù}, subtitle={éèçàù}, author={éèçàù}, keyword={éèçàù}]
the accented characters get al scrambled up in the pdf document properties fields while in the document itself all is ok.
Qué passa ?
(2) \pdfminorversion=5 (or whatever) gives
! Undefined control sequence. l.31 \pdfminorversion =5 ? ! Emergency stop. l.31 \pdfminorversion =5
What's the alternative ?
Thanks, Alan
I'm getting a bunch of ��ï symbols. On Fri, Jun 27, 2008 at 04:22:14PM +0200, Alan Stone wrote:
Re (1)
Would somebody please de so kind to compile this minimal example with XeTeX and inform me what you see in the pdf's document properties for: title, subject, author and keywords ?
The good looking characters or the messed up ones ?
--- begin code ---
\mainlanguage[fr]
\setupinteraction[ title= Ԍ , subtitle= , author= , keyword= ]
\starttext
\stoptext
--- end code ---
Thanks on beforehand, Alan
2008/6/27 Alan Stone
: Hi,
- ConTeXt ver: 2008.06.22 17:38 MKII fmt: 2008.6.23 ( ctx minimal) - XeTeX, Version 3.1415926-2.2-0.999.1 (Web2C 7.5.6)
When using
(1) \setupinteraction[state=start, title={ }, subtitle={ }, author={ }, keyword={ }]
the accented characters get al scrambled up in the pdf document properties fields while in the document itself all is ok.
Qu passa ?
(2) \pdfminorversion=5 (or whatever) gives
! Undefined control sequence. l.31 \pdfminorversion =5 ? ! Emergency stop. l.31 \pdfminorversion =5
What's the alternative ?
Thanks, Alan
___________________________________________________________________________________ If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context webpage : http://www.pragma-ade.nl / http://tex.aanhet.net archive : https://foundry.supelec.fr/projects/contextrev/ wiki : http://contextgarden.net ___________________________________________________________________________________
-- Khaled Hosny Arabic localizer and member of Arabeyes.org team
Thanks Khaled. In the meantime found http://wiki.contextgarden.net/PDF_Bookmarks_and_Headers#PDF_Headers so... --- begin code --- \mainlanguage[fr] \setupinteraction[ state=start, title={ÀÂÆ ÇÉÈÊË ÎÏÔŒ ÙÜŸ}, subtitle={àâæ çéèêë îïôœ ùûüÿ}, author={àâæ ÀÂÆ}, keyword={àâæ çéèêë îïôœ ùûüÿ}] \starttext À Â Æ Ç É È Ê Ë Î Ï Ô Œ Ù Ü Ÿ à â æ ç é è ê ë î ï ô œ ù û ü ÿ \stoptext --- end code --- Still scramled pdf headers. Looking for an enlightened and enlightening soul... Alan
FYI, log file in attachment. There's a ( for me obscure ) warning message... Have a good weekend everybody, Alan
Alan Stone wrote:
FYI, log file in attachment. There's a ( for me obscure ) warning message...
you mean ... [1.1] ** WARNING ** Could not open config file "dvipdfmx.cfg". stdin -> minifr.pdf [1] 5366 bytes written probably harmless Hans ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com | www.pragma-pod.nl -----------------------------------------------------------------
Yep Hans, that one. Ok I won't bother about it any longer.
Any clues regarding the other issues, i.e.
(1) the scrambled PDF headers ?
(2) the inability to lower the \pdfminorversion setting ?
using
- ConTeXt ver: 2008.06.22 17:38 MKII fmt: 2008.6.23 ( ctx minimal)
- XeTeX, Version 3.1415926-2.2-0.999.1 (Web2C 7.5.6)
Best,
Alan
On Fri, Jun 27, 2008 at 11:00 PM, Hans Hagen
Alan Stone wrote:
FYI, log file in attachment. There's a ( for me obscure ) warning message...
you mean ...
[1.1] ** WARNING ** Could not open config file "dvipdfmx.cfg". stdin -> minifr.pdf [1] 5366 bytes written
probably harmless
Hans
Alan Stone wrote:
Yep Hans, that one. Ok I won't bother about it any longer.
Any clues regarding the other issues, i.e.
(1) the scrambled PDF headers ?
(2) the inability to lower the \pdfminorversion setting ?
using
- ConTeXt ver: 2008.06.22 17:38 MKII fmt: 2008.6.23 ( ctx minimal) - XeTeX, Version 3.1415926-2.2-0.999.1 (Web2C 7.5.6)
in pdf traditionally there was only pdf doc encoding; this is supported by default when unicode encoding was added to the spec, i started supporting it too and given that one enables it, traditional tex should work out ok (for instance chinese bookmark were possible) i've now enabled it for luatex (context mkiv) and when that works ou ok i'll see if i can support it for xet ex too (the problem is that i need to rework some code in the spec drivers and that was not on my current agenda) (it means that i need to replace defaults for pdftex/xetex/luatex and since luatex is experimental anyway, let's start there) Hans ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com | www.pragma-pod.nl -----------------------------------------------------------------
Ok Hans. Thanks for taking it into consideration. Take your time do to
whatever you intended to do first. It'll be worthwhile waiting for
sure.
The more I dig into ConTeXt the more I like it ( compared to LaTeX ) -
although the font handling is quite a tough nut to crack. XeTeX makes
it a bit more comprehensible, though I don't have a clue what I'm
doing. I just try different things and keep what works.
Thanks for all that you do.
Have a great weekend,
Alan
On Sat, Jun 28, 2008 at 1:29 PM, Hans Hagen
Alan Stone wrote:
Yep Hans, that one. Ok I won't bother about it any longer.
Any clues regarding the other issues, i.e.
(1) the scrambled PDF headers ?
(2) the inability to lower the \pdfminorversion setting ?
using
- ConTeXt ver: 2008.06.22 17:38 MKII fmt: 2008.6.23 ( ctx minimal) - XeTeX, Version 3.1415926-2.2-0.999.1 (Web2C 7.5.6)
in pdf traditionally there was only pdf doc encoding; this is supported by default
when unicode encoding was added to the spec, i started supporting it too and given that one enables it, traditional tex should work out ok (for instance chinese bookmark were possible)
i've now enabled it for luatex (context mkiv) and when that works ou ok i'll see if i can support it for xet ex too (the problem is that i need to rework some code in the spec drivers and that was not on my current agenda)
(it means that i need to replace defaults for pdftex/xetex/luatex and since luatex is experimental anyway, let's start there)
Hans
Alan Stone wrote:
Ok Hans. Thanks for taking it into consideration. Take your time do to whatever you intended to do first. It'll be worthwhile waiting for sure.
The more I dig into ConTeXt the more I like it ( compared to LaTeX ) - although the font handling is quite a tough nut to crack. XeTeX makes it a bit more comprehensible, though I don't have a clue what I'm doing. I just try different things and keep what works.
the context fonts system is geared to 'users combining fonts of different nature' and 'multiple such sets in parallel in one document' which is what happens a lot over here in principle font support can be made very simple: - add 500 extra files that we call a style - define a combination of fonts in such a file - expect users to know what file to load to get what they want (my guess is that latex is doing that) however, the downside would be ... - many, many useless files - inconsistent combinations (you really need to scale relatively) - still an additional system to defining your own it's a bit the same with setting up a page .. it takes one command (setuplayout) and putting that in a style would add a file and eventually users would use that same comman dto modify their page anyway Hans ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com | www.pragma-pod.nl -----------------------------------------------------------------
participants (3)
-
Alan Stone
-
Hans Hagen
-
Khaled Hosny