Hi, I have applied most of patches and suggestions from Hartmut. There are still a few pending issues: 1) while we are renaming some promitives to be consistent, would it be better to change the following as well: pdfoptionpdfminorversion -> pdfminorversion pdfoptionalwaysusepdfpagebox -> pdfforcepagebox pdfoptionpdfinclusionerrorlevel -> ??? 2) what about moving everything from pdfxtex to pdftex and remove pdfxtex? 3) should the pkmode and microinterval patches be in as well? Martin, can you please wait for a few days, I want to make another snapshot this week. Thanh
The Thanh Han wrote:
2) what about moving everything from pdfxtex to pdftex and remove pdfxtex?
ok for me
3) should the pkmode and microinterval patches be in as well?
indeed, also, taco will make a \noligatures\font patch (this is needed because for instance in the popular ec (cork) encoding monospaced fonts have some ligs and therefore verbatim is hacky 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 -----------------------------------------------------------------
On Tue, 17 May 2005, The Thanh Han wrote:
I have applied most of patches and suggestions from Hartmut.
these were just a few clean-up things, e. g. removing the last rest of pdftex.cfg cfg_ stuff (integers were doubly dumped/undumped without need), removing rest of pdfmovechars. Then in mapfile.c the map entry error check is now a separate function to support map primitives, same for the check for 14 standard font names (which also should be faster now). The unknown names in "..." map entry sections are now better reported, and a harmless uninitialized pointer is fixed.
There are still a few pending issues:
1) while we are renaming some promitives to be consistent, would it be better to change the following as well:
pdfoptionpdfminorversion -> pdfminorversion
i would like these shorter names, but apparently Hans is already using this in spec-tpd.tex, so we can count it as frozen.
pdfoptionalwaysusepdfpagebox -> pdfforcepagebox
never seen this in use anywhere. So maybe...
pdfoptionpdfinclusionerrorlevel -> ???
used by Hans.
2) what about moving everything from pdfxtex to pdftex and remove pdfxtex?
i would prefer this
3) should the pkmode and microinterval patches be in as well?
a pkmode facility has been discussed by Karl. It's now a token register so that it is dumped into the format. Makes it maybe a little tedious in pdftexconfig.tex, as one has to assign catcodes for opening and closing braces, but should be ok. Microinterval will be fun, allows checking various performance things...
Martin, can you please wait for a few days, I want to make another snapshot this week.
Regards, Hartmut
On 2005-05-18 12:53:12 +0200, Hartmut Henkel wrote:
On Tue, 17 May 2005, The Thanh Han wrote:
There are still a few pending issues:
1) while we are renaming some promitives to be consistent, would it be better to change the following as well:
How about keeping the old names as well, but undocumenting them (and maybe giving a warning if they are used, i.e. deprecating them)?
pdfoptionpdfminorversion -> pdfminorversion
i would like these shorter names, but apparently Hans is already using this in spec-tpd.tex, so we can count it as frozen.
pdfoptionalwaysusepdfpagebox -> pdfforcepagebox
never seen this in use anywhere. So maybe...
ArtCom uses it. But that's not my problem anymore (and they will probably never upgrade their pdftex). :-}
pdfoptionpdfinclusionerrorlevel -> ???
used by Hans.
We could simply remove the "option"
2) what about moving everything from pdfxtex to pdftex and remove pdfxtex?
Since everybody now is using etex, there shouldn't be a problem if tex becomes experimental. :-)
3) should the pkmode and microinterval patches be in as well?
a pkmode facility has been discussed by Karl. It's now a token register so that it is dumped into the format. Makes it maybe a little tedious in pdftexconfig.tex, as one has to assign catcodes for opening and closing braces, but should be ok.
Microinterval will be fun, allows checking various performance things...
Put them both in. Best regards Martin -- http://www.tm.oneiros.de
Hi,
pdfoptionpdfminorversion -> pdfminorversion
i would like these shorter names, but apparently Hans is already using this in spec-tpd.tex, so we can count it as frozen.
I have a number of documents that use \pdfoptionpdfminorversion, mainly because the release of AR7/Linux took so long, but also to suppress the warnings when including stuff from Distiller. So I prefer a 'deprecated' message instead of actual removal, at least for the next year (or so).
2) what about moving everything from pdfxtex to pdftex and remove pdfxtex?
Since everybody now is using etex, there shouldn't be a problem if tex becomes experimental. :-)
Sounds good. Taco
On 2005-05-18 14:37:31 +0200, Martin Schröder wrote:
On 2005-05-18 12:53:12 +0200, Hartmut Henkel wrote:
On Tue, 17 May 2005, The Thanh Han wrote:
There are still a few pending issues:
1) while we are renaming some promitives to be consistent, would it be better to change the following as well:
How about keeping the old names as well, but undocumenting them (and maybe giving a warning if they are used, i.e. deprecating them)?
pdfoptionpdfminorversion -> pdfminorversion
I've removed the warning for \pdfoptionpdfminorversion and made \pdfoptionpdfminorversion a simple alias of \pdfminorversion, because they could not be used both in a document safely: ---------------- \pdfoptionpdfminorversion=4 \pdfminorversion=5 ---------------- The code from \pdfoptionpdfminorversion always won (I noticed this because the manual stayed at 1.5 although the source had a \pdfminorversion=3). The reason is this code: ---------------- @p procedure check_pdfminorversion; begin if not pdf_minor_version_written then begin if pdf_option_pdf_minor_version <> 0 then begin pdf_warning(0,"Primitive \pdfoptionpdfminorversion is obsolete; use \pdfminorversion instead.",true); pdf_minor_version := pdf_option_pdf_minor_version; end; ---------------- Fixing this properly seems too difficult (and not worth it) to me. :-{ Best Martin -- http://www.tm.oneiros.de
Hartmut Henkel wrote:
pdfoptionpdfinclusionerrorlevel -> ???
used by Hans.
indeed i like the idea of keeping it for one year with obsolete message that should be enough to let users update 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 (5)
-
Hans Hagen -
Hartmut Henkel -
Martin Schröder -
Taco Hoekwater -
The Thanh Han