- dev-context - NTG Mailing Lists

[contexttest-Feature Requests][72] Extending \placefloat{top,left}. {bottom,outer}, ...
by contexttest-featurerequests＠foundry.supelec.fr 04 Feb '07

04 Feb '07

Feature Requests item #72, was opened at 2007-02-05 01:12 You can respond by visiting: http://foundry.supelec.fr/tracker/?func=detail&atid=164&aid=72&group_id=21 Or by replying to this e-mail entering your response between the following markers: #+#+#+#+#+#+#+#+#+#+#+#+#+#+#+#+#+ (enter your response here) #+#+#+#+#+#+#+#+#+#+#+#+#+#+#+#+#+ Status: Open Priority: 3 Submitted By: Mojca Miklavec (mojca) Assigned to: Nobody (None) Summary: Extending \placefloat{top,left}. {bottom,outer}, ... Version: None Category: None Initial Comment: (From contextgarden.net) The \placefigure macro should be extended to combinations like \placefigure{top,left} or \placefigure{bottom,outer} The reason for this request is that we use ConTeXt a lot for typesetting books from "arts and humanities". There we often have to place a lot of (more then 100) figures at "fixed" positions like top-outer and bottom-inner, wrapped by text. I guess it's not a trivial feature to be implemented in TeX's paragraph processing, but I know it might be worth the effort: ConTeXt's way to deal with fonts and text is so superior that it should be also accessible for disciplines that besides text also rely on images - as the arts and humanities do. ---------------------------------------------------------------------- You can respond by visiting: http://foundry.supelec.fr/tracker/?func=detail&atid=164&aid=72&group_id=21

1 0

[contexttest-Feature Requests][71] High-level bidirectional support
by contexttest-featurerequests＠foundry.supelec.fr 04 Feb '07

04 Feb '07

Feature Requests item #71, was opened at 2007-02-05 01:08 You can respond by visiting: http://foundry.supelec.fr/tracker/?func=detail&atid=164&aid=71&group_id=21 Or by replying to this e-mail entering your response between the following markers: #+#+#+#+#+#+#+#+#+#+#+#+#+#+#+#+#+ (enter your response here) #+#+#+#+#+#+#+#+#+#+#+#+#+#+#+#+#+ Status: Open Priority: 3 Submitted By: Mojca Miklavec (mojca) Assigned to: Nobody (None) Summary: High-level bidirectional support Version: None Category: Typesetting Initial Comment: (Copied from contextgarden.net) Bidirectional text layout for languages that are written from right to left like Arabic and Hebrew plus glyph shaping for complex script languages like Arabic and Thai. ---------------------------------------------------------------------- You can respond by visiting: http://foundry.supelec.fr/tracker/?func=detail&atid=164&aid=71&group_id=21

1 0

[contexttest-Feature Requests][70] Smooth shading
by contexttest-featurerequests＠foundry.supelec.fr 04 Feb '07

04 Feb '07

Feature Requests item #70, was opened at 2007-02-04 23:40 You can respond by visiting: http://foundry.supelec.fr/tracker/?func=detail&atid=164&aid=70&group_id=21 Or by replying to this e-mail entering your response between the following markers: #+#+#+#+#+#+#+#+#+#+#+#+#+#+#+#+#+ (enter your response here) #+#+#+#+#+#+#+#+#+#+#+#+#+#+#+#+#+ Status: Open Priority: 3 Submitted By: Mojca Miklavec (mojca) Assigned to: Nobody (None) Summary: Smooth shading Version: None Category: Typesetting Initial Comment: (Mojca's summary of needed features - I'll try to implemented, but I need to "save" the requirements somewhere before I forget them ;) Description is missing: this list is really taken "out of context". To implement that, the following is needed: - a well-defined metapost interface accepting optional parameters - "dirty" metapost specials and trickery My idea is to split the examples which have to be handled as streams (goraud shading for triangular meshes) and those that can be handled easily: linear & circular shading. I would worry about goraud shading later, since it's really difficult to make a sensible interface for it (unless it's about a single triangle). At least for linear and circular shading I would propose to split the function and the code which generates linear and circular shadings. That way it will be much easier to support what Peter wants (and what I need for the gnuplot terminal) & plotting a rainbow in a single move. (Type 2) For linear shadings we need: - a closed path to which it has to be applied, to calculate the bounding box (for start and stop point), to crop the shading - optional parameter if shading needs to extend over the two boundaries or not (not so important) - optionally provide the start and stop point for shading (default values: depends on angle; shading has to exactly cover the whole path) - optionally provide the angle (default 0) - provide the function or two colors - if two colors are provided, they should be passed to the function in a proper way (Type 3) For circular shadings we need: - a closed path to which the shading has to be applied: I guess that now the shading needs radius of the first circle - optional centers and radii of the two cicles (default values: both center in path center, one radius zero and one to cover the whole path) - optional parameter if shading needs to extend over the two boundaries or not (not so important; default values probably false?) - provide the function or two colors (Type 4) For "Free-Form Gouraud-Shaded Triangle Meshes" we need: - patched Gnuplot 4.3 (http://bugs.libgd.org/?do=details&task_id=39) m-gnuplot.tex and it's documentation ready; all other shadings functions and shadings listed here implemented; then we'll start discussing it For functions we need: * Type 0: sampled - let's worry about it later, I don't understand how to apply it; it can be mimicked with Type 3+Type 2 (although less efficient, but working OK) * Type 2: exponential interpolation - two colors - optional exponent (default 1) * Type 3: stitching (combining multiple functions) - multiple functions - optional bounds between them (default: evenly distributed) Watch out for alpha channel and CMYK! ---------------------------------------------------------------------- You can respond by visiting: http://foundry.supelec.fr/tracker/?func=detail&atid=164&aid=70&group_id=21

1 0

wandering positional graphic
by Sanjoy Mahajan 02 Feb '07

02 Feb '07

Almost the same test file as I used for testing 'dvipos' produces a wandering positional graphic, in dvi or pdf mode. Here's the test file. The problem is that the positional graphic (a tilted line) (that should be) connecting the '6' and the '8' is several inches too low on the page. I've attached a zip file with all the test files and results of running everything -- see the README in it (or just run 'make view'). I'm using Ubuntu/i386 with: CtxTools | context version: 2007.01.23 13:32 pdfTeX 3.141592-1.40.0-2.2 (Web2C 7.5.6) + patch for the mem corruption MetaPost, Version 0.993 (Web2C 7.5.5) metafun 2007-1-23 17:46 (format remade with latest apt-get) The example is as minimal as I could make it. Remove the \setuppapersize[bookpage][A4] and the graphics come out in the right place. Remove the \completecontent or the \section{Fake} and it also comes out okay. =================== begin: to-pdf.tex ================== \definepapersize[bookpage][width=6.875in,height=9in] \setuppapersize[bookpage][A4] \defineoverlay [foregraphics] [\positionoverlay{foregraphics}] \setupbackgrounds [page] [background={foreground,foregraphics}] \starttext \section{Fake} \completecontent \hpos{r13}{6} \hpos{r23}{7} \quad \hpos{r24}{8} \startMPpositiongraphic{mypos:line} mpprocset := 0; % context doesn't yet handle the new mpprocsets path pa, pb, pab ; numeric na, nb ; initialize_box(\MPpos{\MPvar{from}}) ; na := nxy ; pa := llxy..lrxy..urxy..ulxy..cycle ; initialize_box(\MPpos{\MPvar{to}}) ; nb := nxy ; pb := llxy..lrxy..urxy..ulxy..cycle ; if na=nb : pab := center pa -- center pb ; pab := pab cutbefore (pab intersectionpoint pa) ; pab := pab cutafter (pab intersectionpoint pb) ; pickup pencircle; draw pab; anchor_box(\MPanchor{\MPvar{from}}) ; fi ; \stopMPpositiongraphic \startpositionoverlay{foregraphics} \setMPpositiongraphic{r13}{mypos:line}{to=r24} \setMPpositiongraphic{r23}{mypos:line}{to=r24} \stoppositionoverlay \stoptext =================== end: to-pdf.tex ================== -Sanjoy `A nation of slaves is always prepared to applaud the clemency of their master who, in the abuse of absolute power, does not proceed to the last extremes of injustice and oppression.' (Gibbon)

2 4

New Debian packages
by Norbert Preining 02 Feb '07

02 Feb '07

Hi all! Hi Florent! I have uploaded new context packages 2007.01.23-1 BUT ONLY TO THE tug.org server!! Not to Debian till now. Why? I am a bit nervous with respect to this change in 2007.01.18: Switch to latin modern math fonts. If this gives you trouble, you have to update your latin modern font package, see CTAN Well. This is bad. Simply bad. Without backward compatibility I will not upload this to Debian. I cannot, because Debian currently has the lmodern fonts 1.foobar, but without the math fonts. I don't know whether Florent is planning to do an upload of lmodern with the new math fonts included (Florent?). So to be more specific: Is this an *absolute* dependency, ie setting math in context now *only* works with the lmodern math fonts installed? If yes, then sorry for the Debian using guys, but you have to wait until we have the new lmodern in Debian. Best wishes Norbert ------------------------------------------------------------------------------- Dr. Norbert Preining <preining(a)logic.at> Università di Siena Debian Developer <preining(a)debian.org> Debian TeX Group gpg DSA: 0x09C5B094 fp: 14DF 2E6C 0307 BE6D AD76 A9C0 D2BF 4AA3 09C5 B094 ------------------------------------------------------------------------------- BUDBY A nipple clearly defined through flimsy or wet material. --- Douglas Adams, The Meaning of Liff

6 21

interesting bug in \type ;)
by Mojca Miklavec 28 Jan '07

28 Jan '07

Hello Hans & Taco, I didn't try to inspect the reasons for it (I woulg get lost in the code anyway), but it has brought a smile on my face: \type{btex ... etex} simply "forgets" to typeset "etex". \setupcolors[state=start] \setuptype[option=MP] \starttext \startbuffer This is an example of \type+btex ... etex+ syntax. \stopbuffer \typebuffer \getbuffer \stoptext Is there a chance to typeset the whole comment line with the same font (color) when using TEX or MP for syntax highlighting? Now the comments can hardly be distinguished from the rest of the code. Mojca

1 0

garden: new ConTeXt?
by Patrick Gundlach 26 Jan '07

26 Jan '07

I know I have asked this question before and I know you have been discussing this question and cc'd to me.... but anyway. I think this is definitely time to switch the TeX distribution for garden. I use debian 3.1 there and I don't want to update anything to testing/unstable/... Could you give me an advice? Should i use the minimal ConTeXt distribution from PRAGMA ADE? Patrick -- ConTeXt wiki and more: http://contextgarden.net

5 9

Fix for Footnote Reference problem
by Mike Bird 25 Jan '07

25 Jan '07

Here are a number of repaired functions (and one repaired variable) which together fix the problem of footnote references getting out of step between phases resulting in bogus results from \somewhere. The repairs were made in ConTeXt 2007-01-12. Each repaired function is preceded by a comment explaining the reason for the repair. The repaired functions are followed by a test which generates three pages of output covering many test cases. Additionally, I have tested these repairs on a 50 page document with 185 footnotes. All of the \somewhere's were fixed by these repairs. The only downside that I have noticed is that two column footnotes are now less well balanced. If anyone has any thoughts as to why this might be happening or how to fix it please let me know. I'm just a few days from deadline! Thanks, --Mike Bird

2 4

[contexttest-Feature Requests][54] offsets in TABLE-cells
by contexttest-featurerequests＠foundry.supelec.fr 25 Jan '07

25 Jan '07

Feature Requests item #54, was opened at 2007-01-04 11:23 You can respond by visiting: http://foundry.supelec.fr/tracker/?func=detail&atid=164&aid=54&group_id=21 Or by replying to this e-mail entering your response between the following markers: #+#+#+#+#+#+#+#+#+#+#+#+#+#+#+#+#+ (enter your response here) #+#+#+#+#+#+#+#+#+#+#+#+#+#+#+#+#+ Status: Open Priority: 3 Submitted By: Peter Münster (peter) Assigned to: Nobody (None) Summary: offsets in TABLE-cells Version: None Category: None Initial Comment: It would be nice to have independant horizontal and vertical offsets in TABLE-cells. Or even topoffset, bottomoffset, leftoffset and rightoffset. Peter ---------------------------------------------------------------------- Comment By: Mojca Miklavec (mojca) Date: 2007-01-24 04:05 Message: Here are some macros that Wolfgang Schuster <schuster.wolfgang at googlemail.com> sent me some time ago (shame on me that I didn't do anything about it!) They should probably be integrated, not simply overloaded, but ... I would vote for that feature too. Mojca ---------------------------------------------------------------------- You can respond by visiting: http://foundry.supelec.fr/tracker/?func=detail&atid=164&aid=54&group_id=21

1 0

[contexttest-Feature Requests][54] offsets in TABLE-cells
by contexttest-featurerequests＠foundry.supelec.fr 25 Jan '07

25 Jan '07

Feature Requests item #54, was opened at 2007-01-04 11:23 You can respond by visiting: http://foundry.supelec.fr/tracker/?func=detail&atid=164&aid=54&group_id=21 Or by replying to this e-mail entering your response between the following markers: #+#+#+#+#+#+#+#+#+#+#+#+#+#+#+#+#+ (enter your response here) #+#+#+#+#+#+#+#+#+#+#+#+#+#+#+#+#+ Status: Open Priority: 3 Submitted By: Peter Münster (peter) Assigned to: Nobody (None) Summary: offsets in TABLE-cells Version: None Category: None Initial Comment: It would be nice to have independant horizontal and vertical offsets in TABLE-cells. Or even topoffset, bottomoffset, leftoffset and rightoffset. Peter ---------------------------------------------------------------------- Comment By: Mojca Miklavec (mojca) Date: 2007-01-24 04:05 Message: Here are some macros that Wolfgang Schuster <schuster.wolfgang at googlemail.com> sent me some time ago (shame on me that I didn't do anything about it!) They should probably be integrated, not simply overloaded, but ... I would vote for that feature too. Mojca ---------------------------------------------------------------------- You can respond by visiting: http://foundry.supelec.fr/tracker/?func=detail&atid=164&aid=54&group_id=21

1 0