- dev-context - NTG Mailing Lists

x-set-11.mkiv
by Wolfgang Schuster 14 Jun '11

14 Jun '11

Hi Hans, the \blank command is ignored when the complete list is printed with \placesetups because packed mode is used, with a normal \vskip this doesn’t happen. I reduced the skip because “.75\lineheight” looks better for commands without optional arguments. \startxmlsetups xml:setups:typeset \getvalue{\e!start setuptext} ... \xmldoif{#1}{/arguments} { \bgroup \enablemode[setups-pass-two] \doglobal\newcounter\currentSETUPargument - \blank[\v!line] + \godown[.75\lineheight] \switchtobodyfont[small] \ignorespaces\xmlfilter{#1}{/arguments/text()}\endgraf \egroup } \getvalue{\e!stop setuptext} \stopxmlsetups Wolfgang

1 0

No updates for SunOS
by Marco 11 Jun '11

11 Jun '11

On my SunOS box I'm still stuck with mtx-context | current version: 2011.05.05 12:10 This is LuaTeX, Version beta-0.66.0-2011041313 What's wrong? Marco

2 2

pack-mis.mkiv
by Wolfgang Schuster 07 Jun '11

07 Jun '11

Hi Hans, there’s a typo in pack-mis.mkvi \def\pack_placement_indeed[#settings]% set test can be sped up but non critical {\iffirstargument - \setupcurrentplacement[#settings]% + \setupplacement[\currentplacement][#settings]% \fi \dowithnextboxcontent{\forgetall}{\pack_placement_flush\egroup}\vbox} Wolfgang

1 1

Structure syntax for enumerations
by Aditya Mahajan 03 Jun '11

03 Jun '11

Hi, I will like to propose a new command, \definestructureenumeration, which is similar to \defineenumeration, but follows the conventions of \definestructuresection, that is, allows one to write \definestructureenumeration[theorem] \starttheorem[title={An important theorem}, list={Not so important}] ... \stoptheorem The \start<enumeration> command takes the same arguments as \startsection. What do you think? Aditya

3 2

\getscaledglyph
by Wolfgang Schuster 29 May '11

29 May '11

Isn’t there a \fontbody missing as first argument of \setscaledstyledsymbolicfont? font-ini.mkiv: \unexpanded\def\getscaledglyph #1#2#3{{\setscaledstyledsymbolicfont{#1}{#2}\doifnumberelse{#3}\char\donothing#3}} Wolfgang

2 1

composing characters in MKIV: adding "mark" feature
by Mojca Miklavec 25 May '11

25 May '11

Dear Hans, as a follow up to the topic I brought up again last week (and as it was partially brought up on the tex-font mailing list as well), here are some of my thoughts (for discussion). When thinking a bit about it, it appears to me that the best approach for fixing accent positioning would be to implement "mark"/"mkmk" feature for both Type1 and OpenType fonts using lfg files. The things that come to my mind and would have to be done are the following: 1.) with some configuration, but universal accross fonts: One might have to copy a normal caron into combining caron (and copy all other accents as well), to enable <c><combining caron> to work properly. (Arthur would probably argue about normalization at this point, but I'm also talking about combinations that don't exist in Unicode; maybe <eogonek><combining caron> etc.) 2.) universal accross fonts: Let TeX determine "bottom marks" and "top marks" for all letters (that is: eogonek and scedilla also need at least the "top mark"). The code to calculate those values is already there. It would be helpful to have both graphical output displaying those marks on top of letters as well as an option to output those settings into a file (to enable easy manual editing of values and loading them again). 3.1.) Allow editing the values that TeX returned (from point 2) and loading them. 3.2.) Allow shifting "top marks" separately on lowercase/uppercase/smallcaps. Among those, allow exceptions for single letters (like lowercase l in Lucida which is taller than uppercase letters and requires special handling). Allow shifting "bottom marks" and allow exceptions. 4.) Allow shifting both marks to left/right (I'm not sure about units, but they may be the same units as used for bounding boxes; people who want to fix that have to experiment anyway). 5.) Allow shifting positioning marks on accents. There is some confusion since some accents come with their "natural bounding box", while combining accents don't. 6.) Low priority: For fonts that do have mark/mkmk feature, allow fixing mark positions on single letters and allow adding new marks on letters that lack them. 7.) Very low priority: Allow "faking accents" (creating bottom circumflex out of top circumflex). 8.) Lower priority, but might be kept in mind: this has to be done for Latin, but other scripts (like Cyrillic) might want to have that functionality on request as well. It makes little sense to add marks on all glyphs, including Chinese etc. The autocomposing feature should probably be switched off by default, but if one wants to switch it on and if one wants to add positioning marks, it might make sense to "ask the user" to which glyphs those marks have to be added. I can try to come up with more precise specification, but to start with: how would one add mark/mkmk features to lfg files? (I'm asking for some minimal example of syntax which doesn't have to work.) Mojca

2 1

Luatex 0.70.1 announcement
by Taco Hoekwater 18 May '11

18 May '11

Hi, I have just uploaded the archives for a new luatex release, 0.70.1. About a dozen or so bugfixes that were mostly discovered while working on TeXLive 2011. News: * fixed: recorder file location from TL. * fixed: missing newline on 'No output' line. * fixed: relative names in synctex file. * fixed: 16bit png images in generated %!PDF-1.4. * fixed: building with (installed) libpng < 1.5.0 * fixed: year in --version output. * fixed: box output to synctex. * fixed: FontDescriptor for non-embedded OpenType fonts has an invalid FontFile3 entry (#654) * fixed: crash on non-existent images. * fixed: small memory leak in the ipc code. * fixed: tex.print() and tex.sprint() don't recognize -2 as the first argument (#659) The archives can be downloaded from supelec as usual: http://foundry.supelec.fr/gf/project/luatex/ You could also check out the sources via anonymous svn: svn co http://foundry.supelec.fr/svn/luatex/tags/beta-0.70.1 Bugs and feature requests can be added to the issue tracker at http://tracker.luatex.org Have fun, Taco

1 0

current
by Hans Hagen 16 May '11

16 May '11

Hi, As I expect some incompatible luatex dev soon (lua level) I'd like to make a current. Any known showstoppers? Hans ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com | www.pragma-pod.nl -----------------------------------------------------------------

2 1

MetaPost 1.504
by Taco Hoekwater 06 May '11

06 May '11

We are happy to announce a new release of MetaPost: ---------------------------------------------------------------------- MetaPost 1.504 ---------------------------------------------------------------------- The standalone distribution package and a win32 binary can be downloaded immediately from http://foundry.supelec.fr/gf/project/metapost/ This is a bugfix release following the major internal rewrite done for 1.500. In fact, this will be the version of metapost that will be on TeXLive 2011. The win32 binary is intended for texlive or a similar web2c-based installation, this executable will *not* work for miktex. Of course, we welcome any comments (either good or bad) that you may have. Simply replying to this message is fine, but see the bottom of the message for a more formal way to report bugs and feature requests. ---------------------------------------------------------------------- What is new in MetaPost version 1.504: ---------------------------------------------------------------------- * A fix to the automatic detection of 'dvitomp' mode based on the executable name (proposed by PEB). * A better way to discover the end of the preload file is used now. * A memory release bug that caused metapost to crash on exit when fontmaking:=1 has been fixed. * A memory leak in the string concatenation code has been removed. * Again, a set of improvements to the manual. * Updated the manual page mpost.man ---------------------------------------------------------------------- Legal notice / license / bug reports ---------------------------------------------------------------------- MetaPost is a system for producing graphics developed by John Hobby at AT&T, based on Donald Knuth's Metafont. The MetaPost home page is http://tug.org/metapost. MetaPost is free software: you can redistribute it and/or modify it under the terms of the GNU Lesser General Public License as published by the Free Software Foundation, either version 2.1 of the License, or (at your option) any later version. The MetaPost development project is currently hosted at Supelec, http://foundry.supelec.fr/gf/project/metapost; with a bug tracker at http://tracker.luatex.org/. Please report bugs and request enhancements through there if possible. Alternatively, you can reach us through the <metapost(a)tug.org> mailing list as well. Have fun! Taco Hoekwater, for the MetaPost team, May 6, 2011.

1 0

Luatex 0.70.0 announcement
by Taco Hoekwater 06 May '11

06 May '11

Hi, I have just uploaded the archives for a new luatex release, 0.70.0. This release will be the one on TeXLive 2011 (barring show-stopping bugs). Compared to 0.66, there is not a lot of news, just a few bug-fixes. News: * fixed: various changes needed for libpng 1.5.2. * fixed: node.fields() for nodes without subtype. * fixed: non-argument use of os.execute(). * fixed: tex.[s|t|]print() with invalid catcode table arguments. * fixed: recorder filename location with --output-directory. * fixed: display alignment in TRT mode. * luatex now uses the standard synctex files from Jérome Laurens. The archives can be downloaded from supelec as usual: http://foundry.supelec.fr/gf/project/luatex/ You could also check out the sources via anonymous svn: svn co http://foundry.supelec.fr/svn/luatex/tags/beta-0.70.0 Bugs and feature requests can be added to the issue tracker at http://tracker.luatex.org Have fun, Taco

1 0