[NTG-context] Re: Back in the 90s

drive viewers we went from epson dot matrix printer -> early 300 dpi laser -> 600 dpi laser printer -> high speed oce 512 dpi printer (metric) -> high speed oce 600 dpi printer (+ crappy canon color laser printer) -> fast page-wide hp color inkjet office printer in mkii al

[NTG-context] Re: Japanese

justment > > https://www.w3.org/TR/jlreq/#term.line-adjustment > > • aligning of the lines to the Kihon-hanmen (optimizing the code below in > > this regard) > > • positioning and realm of headings https://www.w3.org/TR/jlreq/#fig3_1_9 > > https://www.w3.org/TR/jlreq/#f

[NTG-context] Re: Japanese

igning of the lines to the Kihon-hanmen (optimizing the code below in > > this regard) > > • positioning and realm of headings https://www.w3.org/TR/jlreq/#fig3_1_9 > > https://www.w3.org/TR/jlreq/#fig3_1_15 et al, and > > https://www.w3.org/TR/jlreq/#fig3_1_4 > > • p

[NTG-context] Re: Japanese

rg/TR/jlreq/#fig2_3_24 > • inline cutting note (warichu) https://www.w3.org/TR/jlreq/#fig2_4_1 > • emphasis with sesame dot or bullet > • itemization https://www.w3.org/TR/jlreq/#fig2_5_6 > • indenting of quotation paragraphs > https://www.w3.org/TR/jlreq/#f

[NTG-context] Re: Japanese

/jlreq/#fig2_3_24 * inline cutting note (warichu) https://www.w3.org/TR/jlreq/#fig2_4_1 * emphasis with sesame dot or bullet * itemization https://www.w3.org/TR/jlreq/#fig2_5_6 Circled numbered are easy and achieved by adding additional number conversions. * indenting of quotation

[NTG-context] Re: Japanese

* inline cutting note (warichu) https://www.w3.org/TR/jlreq/#fig2_4_1 * emphasis with sesame dot or bullet * itemization https://www.w3.org/TR/jlreq/#fig2_5_6 * indenting of quotation paragraphs https://www.w3.org/TR/jlreq/#fig2_5_7 * tab setting https://www.w3.org/TR/jlreq

[NTG-context] Re: Japanese

/#fig2_3_24 inline cutting note (warichu) https://www.w3.org/TR/jlreq/#fig2_4_1 emphasis with sesame dot or bullet itemization https://www.w3.org/TR/jlreq/#fig2_5_6 indenting of quotation paragraphs https://www.w3.org/TR/jlreq/#fig2_5_7 tab setting https://www.w3.org/TR/jlreq/#fig2_6_1 furiwake https

[NTG-context] Re: [External] Re: Looking for itemize help

(+), Rogers, Michael K wrote: > Hi Jim, > I think you want alternative “a”, if the dot instead of a letter is the > problem and not the whitespace: > %% > \starttext > This is a short paragraph. > This is a line before a {\bf packed, joinedup} itemization. >

[NTG-context] Re: [External] Re: Looking for itemize help

Hi Jim, I think you want alternative “a”, if the dot instead of a letter is the problem and not the whitespace: %% \starttext This is a short paragraph. This is a line before a {\bf packed, joinedup} itemization. \startitemize[a,packed,joinedup] \item First item. \item Second item

[NTG-context] Re: QR Code

lders in environment variables, it is best to use UNIX-style (TeX usually expects and prefers directories to be separated by "/" rather "\" because the backslash is its control character). Furthermore, "//" at the end cannot be substituted with "\\". The i

[NTG-context] Re: Key distance with enumeration

Fabrice Couvreur schrieb am 27.07.2023 um 20:56: Hi, I don't understand why the distance between the dot and the first letter of the text is not always the same (see with theorem). Add         stretch=0,         shrink=0, to your enumeration setup. Wolfgang

[NTG-context] Key distance with enumeration

Hi, I don't understand why the distance between the dot and the first letter of the text is not always the same (see with theorem). Thanks Fabrice \setupenumerations [before={\blank}, after={\blank}, alternative=serried, distance=1cm, title=yes, titleleft=, titleright

[NTG-context] Re: \showmakeup adds unwanted space despite accurate readings; \qquad mandatory before \TeX\

phg/context-mirror/commits/ > wiki : https://contextgarden.net > _______ > -- [From the operation manual for the CI-300 Dot Matrix Line Printer, made in Japan]: The excellent output machine of MODEL CI-300 as e

Re: [NTG-context] Fallbacks in text font interfere with math accents

ms remain (e.g. breve, check, dot, widehat). It also affects the sizing of limiters and e.g. underbraces. Why do font fallbacks for non-math fonts affect math at all? Hraban ___ If your question is of interest

Re: [NTG-context] \writetolist not writing the number to the TOC

gger via ntg-context wrote: >> Hello Hraban, >> thank you. I missed this point. However, adding a dot behind the number does >> not appear to solve the problem. The title’s text still starts at the left >> margin which looks very odd. >> Kind regards >> Willi >&

Re: [NTG-context] \writetolist not writing the number to the TOC

On 3/26/2023 3:10 PM, Willi Egger via ntg-context wrote: Hello Hraban, thank you. I missed this point. However, adding a dot behind the number does not appear to solve the problem. The title’s text still starts at the left margin which looks very odd. Kind regards Willi On 26 Mar 2023

Re: [NTG-context] \writetolist not writing the number to the TOC

Hello Hraban, thank you. I missed this point. However, adding a dot behind the number does not appear to solve the problem. The title’s text still starts at the left margin which looks very odd. Kind regards Willi > On 26 Mar 2023, at 12:51, Henning Hraban Ramm via ntg-context >

Re: [NTG-context] \writetolist not writing the number to the TOC

.” https://wiki.contextgarden.net/Command/writetolist So maybe you need a dot? Otherwise I don’t know. Hraban ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context

[NTG-context] Fwd: BachoTeX 2023: invitation and call for papers

Contributions should be sent by email to the Program Committee:     prog-2023 at gust.org.pl. The Program Committee is chaired by Bogusław Jackowski (b_jackowski at gust dot org dot pl). For other conference details see http://gust.org

Re: [NTG-context] autospacing and colonequals (was Lucida-1.901 (2023-01-21) available)

around >>> the math axis, as explained in the article. For instance in the following >>> example >>> >>> \setupbodyfont[lucidaot,12pt] >>> \starttext >>> \startformula >>> f(x) := -(u|x) := - \langle u, x \rangle >>> \stopform

Re: [NTG-context] Lucida-1.901 (2023-01-21) available

\startformula f : A \longrightarrow B \stopformula \stoptext it seems to me that the lower dot (or square…) in the semicolumn of the first formula (in front of the equal sign) is lower than in the second formula. Best regards: Otared Thank you for the kind words, Otared, Regarding the colons

Re: [NTG-context] Lucida-1.901 (2023-01-21) available

x \rangle > \stopformula > \stopformula > \startformula > f : A \longrightarrow B > \stopformula > \stoptext > > it seems to me that the lower dot (or square…) in the semicolumn of the first > formula (in front of the equal sign) is lower than in the second formula. > >

Re: [NTG-context] Lucida-1.901 (2023-01-21) available

. For instance in the following example \setupbodyfont[lucidaot,12pt] \starttext \startformula f(x) := -(u|x) := - \langle u, x \rangle \stopformula \stopformula \startformula f : A \longrightarrow B \stopformula \stoptext it seems to me that the lower dot (or square…) in the semicolumn

Re: [NTG-context] Unconnected \mathboxanchored produces unexpected results

ded not to use this connector, producing unexpected results. \startformula \mathboxanchored[nucleus]{c1}{e}^{\dot\alpha} \mathboxanchored[nucleus]{c2}{e}_{\mu} \mathboxanchored[nucleus]{c3}{e}^{\beta} = \frac{1}{\sqrt{2}} \bar\sigma^{\dot\alpha\beta}_{\mu} \stopformula \stopboxanchor

[NTG-context] Unconnected \mathboxanchored produces unexpected results

lts. \startformula \mathboxanchored[nucleus]{c1}{e}^{\dot\alpha} \mathboxanchored[nucleus]{c2}{e}_{\mu} \mathboxanchored[nucleus]{c3}{e}^{\beta} = \frac{1}{\sqrt{2}} \bar\sigma^{\dot\alpha\beta}_{\mu} \stopformula \stopboxanchoring \stoptext anchors-002-copy.pdf Description: Adobe

[NTG-context] Accent wrecking \mathboxanchored

kinds of connections! Gavin \starttext \startboxanchoring[+] \connectboxanchors[top][top][distance=1ex,arrow=no] {c1}{c2} \connectboxanchors[bottom] [bottom] [distance=1ex,arrow=no] {c2}{c3} \startformula \mathboxanchored[nucleus]{c1}{e}^{\dot\alpha} %\mathboxanchored[nucleus]{c2}{e}

[NTG-context] issues with variable fonts in latest

] {\tt áéíóúijrf} \scale[width=\textwidth] {\hw áéíóúijrf} \scale[width=\textwidth] {\cg áéíóúijrf} \stopTEXpage \stoptext 'mono=1' misplaces the dot in i and j and the accent in i (all to the left). It also misses bottom lines in i, r and f. And it also misses the upper left stroke in r

Re: [NTG-context] Mathematical MetaFun Mania

\starttext \startboxanchoring[+] \connectboxanchors[top][top][distance=1ex,arrow=no] {c1}{c2} \connectboxanchors[bottom] [bottom] [distance=1ex,arrow=no] {c2}{c3} \startformula \mathboxanchored[nucleus]{c1}{e}_{\alpha} \mathboxanchored[nucleus]{c2}{e}^{\mu} \mathboxanchor

Re: [NTG-context] \hpos in math - Half solved

=1ex] {d1}{d2} \startformula \mathboxanchored[nucleus]{c1}{e}_{\alpha} \mathboxanchored[nucleus]{c2}{e}^{\mu} \mathboxanchored[nucleus]{d1}{todo} \mathboxanchored[nucleus]{d2}{e}_{\dot{\beta}} = \frac{1}{\sqrt{2}} \sigma_{\alpha,\dot{\beta}}^{\mu} \stopformula \stopboxanchoring

Re: [NTG-context] \hpos in math

athboxanchored{X}{e}_\alpha \mathboxanchored{Y}{e}^\mu \mathboxanchored{Z}{e}_{\dot\beta} = \textfrac{1}{\sqrt{2}}\sigma_{\alpha\dot\beta}^\mu \stopformula I added code to turn the arrow produced by \connectboxanchors into my contraction overlay, but that doesn’t affect these issues. > in your exa

Re: [NTG-context] \hpos in math

and Rindler in their 1985 books “Spinors and Space-time.” In the typesetting example above, the e_\alpha and e_{\dot\beta} are basis spinors (one left-handed, one right-handed). The e^\mu is the Infeld-van der Waerden symbol relating the spin basis to the coordinate basis. The connections are spinor

[NTG-context] \hpos in math

rather than tensors, following the methods of Penrose and Rindler in their 1985 books “Spinors and Space-time.” In the typesetting example above, the e_\alpha and e_{\dot\beta} are basis spinors (one left-handed, one right-handed). The e^\mu is the Infeld-van der Waerden symbol relating the spin

Re: [NTG-context] Spacing in \unit

> On 25 Sep 2022, at 14:30, Gavin via ntg-context wrote: > > Hello list, > > I have a few questions about space produced by the unit command. Consider > this MWE > > \starttext > \unit{3.00e8 kg m/s} > > $\unit{3.00e8 kg m/s}$ > \stoptext > >

Re: [NTG-context] Spacing in \unit

about space produced by the unit command. Consider >> this MWE >> \starttext >> \unit{3.00e8 kg m/s} >> $\unit{3.00e8 kg m/s}$ >> \stoptext >> The dot between “kg” and “m” has different spacing depending on whether the >> \unit command is in text or math mode.

Re: [NTG-context] Spacing in \unit

On 9/25/2022 3:30 PM, Gavin via ntg-context wrote: Hello list, I have a few questions about space produced by the unit command. Consider this MWE \starttext \unit{3.00e8 kg m/s} $\unit{3.00e8 kg m/s}$ \stoptext The dot between “kg” and “m” has different spacing depending on whether

[NTG-context] Spacing in \unit

Hello list, I have a few questions about space produced by the unit command. Consider this MWE \starttext \unit{3.00e8 kg m/s} $\unit{3.00e8 kg m/s}$ \stoptext The dot between “kg” and “m” has different spacing depending on whether the \unit command is in text or math mode. I think

Re: [NTG-context] Graphviz and ConTeXt

] [cache=yes, readcommand=\ReadFigure, output={\externalfilterbasefile.pdf}, filtercommand={dot -Tpdf -o "\externalfilterbasefile.pdf" "\externalfilterinputfile"}] \starttext \startTEXpage \startgraphviz digraph G { main -> parse -> execute; main -&

[NTG-context] Graphviz and ConTeXt

Dear all, I have a legacy project that I shall convert to a new ConTeXt project. There are a lot of Graphviz dot-files. What shall I do with these? Any hints? juh -- Autoren-Homepage: . http://literatur.hasecke.com Satiren & Essays: . http://www.sudelbuch.de Privater

Re: [NTG-context] new upload

] \placeRussian \stoptitle \stoptext Regarding the implementation: I've just tried it, and I wondered whether the stacking of bars should not happen the other way round. As in \underbar{\underdot{asdf}} I would have expected the bar to be below the dot. But maybe that's wrong expectations

Re: [NTG-context] new upload

round. As in \underbar{\underdot{asdf}} I would have expected the bar to be below the dot. But maybe that's wrong expectations... Denis > -Ursprüngliche Nachricht- > Von: ntg-context Im Auftrag von Hans Hagen > via ntg-context > Gesendet: Dienstag, 30. November 2021 19:56 &

Re: [NTG-context] ConTeXt inserts additional dots for Iosevka font

alternate, but only partially. > > > \definefont > >[SomeFont] > >[name:iosevka*default:test] > > \starttext > > \SomeFont > > I live in a dot-heavy world. > > \stoptext > > > > has six dots inst

Re: [NTG-context] ConTeXt inserts additional dots for Iosevka font

\definefontfeature [default:test] [default] [cv36=2,cv26=6] What is the number supposed to indicate ? It is not an alternate, right? \definefont [SomeFont] [name:iosevka*default:test] \starttext \SomeFont I live in a dot-heavy world

[NTG-context] ConTeXt inserts additional dots for Iosevka font

=6] \definefont [SomeFont] [name:iosevka*default:test] \starttext \SomeFont I live in a dot-heavy world. \stoptext has six dots instead of one dot over each "i". Tests with multiple other font shapers and inspection of the font file

Re: [NTG-context] Unicode normalization and Hebrew in ConTeXt

If a *shin *with a *sin *dot (שׂ) is pointed with a *holam *(the vowel point placed high and on the left), then the *shin*, *sin *dot, and *holam *are combined into a single ligature that depicts the *sin *dot and *holam *merged into a single point. 2. If a *shin *with a *shin *dot (ש

Re: [NTG-context] Question about \groupedcommand{}{}

Hi Wolfgang, Thank you for this nice solution. Fabrice Le mar. 27 juil. 2021 à 21:31, Wolfgang Schuster via ntg-context < ntg-context@ntg.nl> a écrit : > Fabrice Couvreur via ntg-context schrieb am 27.07.2021 um 18:57: > > Hi, > > The name of the environment must alway

Re: [NTG-context] Question about \groupedcommand{}{}

Fabrice Couvreur via ntg-context schrieb am 27.07.2021 um 18:57: Hi, The name of the environment must always end with a dot both with a title and without title. How to do ? Thanks Fabrice [...] You can create simple dummy environments to test the parameters. \defineenumeration

[NTG-context] Question about \groupedcommand{}{}

Hi, The name of the environment must always end with a dot both with a title and without title. How to do ? Thanks Fabrice \setupenumerations [before={\blank}, after={\blank}, alternative=serried, title=yes, titleleft={(}, titleright={)}, titlestyle=normal, titlecommand

Re: [NTG-context] Issue running ConTeXt from TeX Live 2019 on Alpine Linux 3.12

shell_escape_commands = \ bibtex,bibtex8,\ extractbb,\ gregorio,\ kpsewhich,\ makeindex,\ repstopdf,\ r-mpost,\ texosquery-jre8,\ % we'd like to allow: % dvips - but external commands can be executed, need at least -R1. % epspdf, ps2pdf, pstopdf - need to respect openout_any, % and gs -dSAFER must

Re: [NTG-context] Hyphenation patterns

are seven patterns involved in hyphenating the word applicable: 4p1, 1p2l2, pli2c1ab, 1ca, ca1bl, b2l2, and b4le. (the final dot is part of that last pattern). The pattern responsible for the break applic-able is pli2c1ab. If we now refer to the source repository for hyphenation patterns (since

Re: [NTG-context] composing commands

comma below ş hook ȥ ring above å ring below ḁ dot above ṁ middle dot ŀ dot below ṃ breve ă inverted breve ȃ caron ǩ stroke ø Best, Richard -Original Message- From: Hans Hagen Reply-To: mailing list for ConTeXt

[NTG-context] Minor issue with font kern amount being doubled

Dear list, Rare cases only but I thought it’d worth reporting this difference I could not understand.Could reproduce this problem with a simple MWE below. Kerning between ‘v’ and dot is doubled if \feature macro is used. Thanks \definefontfeature[xvicentury][mode=node]\definefontfeature[default

Re: [NTG-context] upload / metafun

Hi Hans, Thanks for the new upload. With your comments, I understand that, following the discussion with Aditya, when using the new version I should not define in Metafun a new function named dotlabel in order to have a square dot… Actually I called it mydotlabel in order to be able

Re: [NTG-context] Metafun: is it possible to redefine dotlabel to draw a square ?

On 12/10/2020 8:37 PM, Aditya Mahajan wrote: On Thu, 10 Dec 2020, Hans Hagen wrote: dotlabel uses a pen to draw the dot, and I am not sure why it uses that rather than a path. Here is a (to me) simpler definition, where you can change the shape: just look in the pdf ... in your case the dot

Re: [NTG-context] Metafun: is it possible to redefine dotlabel to draw a square ?

On Thu, 10 Dec 2020, Hans Hagen wrote: > > dotlabel uses a pen to draw the dot, and I am not sure why it uses that > > rather > > than a path. Here is a (to me) simpler definition, where you can change the > > shape: > > just look in the pdf ... in your case t

Re: [NTG-context] Metafun: is it possible to redefine dotlabel to draw a square ?

On 12/10/2020 6:44 PM, Aditya Mahajan wrote: On Thu, 10 Dec 2020, Otared Kavian wrote: Hi all, In Metafun when representing a point I woul dlike to have some dots represented by a square (or even by another scalable symbol): for instance in the following I would like the dot at the point B

Re: [NTG-context] Metafun: is it possible to redefine dotlabel to draw a square ?

I woul dlike to have some dots >> represented by a square (or even by another scalable symbol): for instance >> in the following I would like the dot at the point B to be a square: >> >> \starttext >> \startMPcode >> draw (2cm,3cm) -- (3cm,5cm) ; >> dotla

Re: [NTG-context] Metafun: is it possible to redefine dotlabel to draw a square ?

On Thu, 10 Dec 2020, Otared Kavian wrote: > Hi all, > > In Metafun when representing a point I woul dlike to have some dots > represented by a square (or even by another scalable symbol): for instance in > the following I would like the dot at the point B to be a square:

[NTG-context] Metafun: is it possible to redefine dotlabel to draw a square ?

Hi all, In Metafun when representing a point I woul dlike to have some dots represented by a square (or even by another scalable symbol): for instance in the following I would like the dot at the point B to be a square: \starttext \startMPcode draw (2cm,3cm) -- (3cm,5cm) ; dotlabel(textext

Re: [NTG-context] defining font family for several options

, The tilde ~ in {\bf\ss #1.~#2} is only there to have an unbreakable fixed space between the dot and the first character of the chapter title. Also in this way one can see that one has put a space there… :-) Best tegards: Otared On 2 Sep 2020, at 23:29, jbf wrote: Thanks Otared, Still off

Re: [NTG-context] No dots in \dotfill with new font

On 6/16/2020 11:13 PM, James Withers wrote: Many thanks Hans. That has made the dots appear. If possible I would like to use the dot from the same font, especially if using a font where full stops are diamond shaped rather than circular. Is there any way to map the dot from the external font so

Re: [NTG-context] No dots in \dotfill with new font

Many thanks Hans. That has made the dots appear. If possible I would like to use the dot from the same font, especially if using a font where full stops are diamond shaped rather than circular. Is there any way to map the dot from the external font so that it can be used by the \dotfill command

Re: [NTG-context] 'debug' version of METAPOST draw?

where each pair in teh path is also drawn as a dot and maybe teh directions drawn as small arrows. Does someone have such a beast lying around? G ___ If your question is of interest to others as well, please add

[NTG-context] 'debug' version of METAPOST draw?

I would like to be able (during development) to draw paths where the points of the path (and maybe thing slike directions) are visualised. E.g. a path where each pair in teh path is also drawn as a dot and maybe teh directions drawn as small arrows. Does someone have such a beast lying around

Re: [NTG-context] Strangely placed dot

placement of the dot in this example, and how > can I avoid it? > > \starttext > \startTEXpage[offset=3bp] > $E_tE_s=E_{\min(t,s)}$. > > \switchtobodyfont[stixtwo]$E_tE_s=E_{\min(t,s)}$. > > \switchtobodyfont[lucidaot]$E_tE_s=E_{\min(t,s)}$. > \stopTEXpage >

[NTG-context] Strangely placed dot

Hi, what is going on with the placement of the dot in this example, and how can I avoid it? \starttext \startTEXpage[offset=3bp] $E_tE_s=E_{\min(t,s)}$. \switchtobodyfont[stixtwo]$E_tE_s=E_{\min(t,s)}$. \switchtobodyfont[lucidaot]$E_tE_s=E_{\min(t,s)}$. \stopTEXpage \stoptext Output attached

[NTG-context] Fwd: Unicode normalization and Hebrew in ConTeXt

. 2. Shin dot and sin dot (05C1-05C2) should be next, but Unicode places them in combining classes 24 and 25, after the characters in recommended classes 3-5 and many of the characters in recommended class 6. 3. Dagesh / mapiq (05BC) should be next, but Unicode assigns it a combining class of 21

Re: [NTG-context] Setting up macvim in mac os catalina to work with LMTX

ypically located at $HOME/.vim/vimrc (note that the filename does *not* start with a dot, only the directory's name does). Good ConTeXt typesetting in Vim! Nicola ___ If your question is of interest to other

Re: [NTG-context] Official file ending?

On 2/5/2020 11:00 AM, Henning Hraban Ramm wrote: Am 2020-02-05 um 10:24 schrieb Hans Hagen : On 2/4/2020 8:27 PM, kaddour kardio wrote: Since ConTeXT is closer to plain TeX than LaTeX, it is more legitimate to got the "dot tex" than latex :) I always wonder where such info

Re: [NTG-context] Official file ending?

> Am 2020-02-05 um 10:24 schrieb Hans Hagen : > > On 2/4/2020 8:27 PM, kaddour kardio wrote: >> Since ConTeXT is closer to plain TeX than LaTeX, it is more legitimate to >> got the "dot tex" than latex :) > I always wonder where such info c

Re: [NTG-context] Official file ending?

han LaTeX, it is more legitimate > > to got the "dot tex" than latex :) > > > > Le mar. 4 févr. 2020 à 17:57, Pablo Rodriguez > <mailto:oi...@gmx.es>> a écrit : > > > > On 2/3/20 3:28 PM, Hans Hagen wrote: > > > On 2/3/2020 3:07 P

Re: [NTG-context] Official file ending?

On 2/4/2020 8:27 PM, kaddour kardio wrote: Since ConTeXT is closer to plain TeX than LaTeX, it is more legitimate to got the "dot tex" than latex :) I always wonder where such info comes from. Plain tex is a 45K file that is described in the tex book and serves as template for Don

Re: [NTG-context] Official file ending?

On 2/4/2020 8:27 PM, kaddour kardio wrote: Since ConTeXT is closer to plain TeX than LaTeX, it is more legitimate to got the "dot tex" than latex :) Le mar. 4 févr. 2020 à 17:57, Pablo Rodriguez <mailto:oi...@gmx.es>> a écrit : On 2/3/20 3:28 PM, Hans Hagen wrote:

Re: [NTG-context] Official file ending?

> Am 2020-02-04 um 20:27 schrieb kaddour kardio : > > Since ConTeXT is closer to plain TeX than LaTeX, it is more legitimate to got > the "dot tex" than latex :) I’d suggest to start

Re: [NTG-context] Official file ending?

Since ConTeXT is closer to plain TeX than LaTeX, it is more legitimate to got the "dot tex" than latex :) Le mar. 4 févr. 2020 à 17:57, Pablo Rodriguez a écrit : > On 2/3/20 3:28 PM, Hans Hagen wrote: > > On 2/3/2020 3:07 PM, Philipp A. wrote: > >> Hi! > >&

[NTG-context] Impacts Project

Hi list! Thank you for helping to answer so many questions and remove so many roadblocks with my project. The result is a photobook written in Markdown, piped through pandoc to generate ConTeXt code, then stylized using a series of .tex files. The coolest ConTeX part, IMO, is the orange dot

[NTG-context] Indenting number in TOC, particular numbering scheme, and other questions

module. I have looked into m-subsub.mkiv and saw no difference at all between the different levels defined there. 3. Is it possible to indent not only the section name but also the number in the TOC? Moreover, I would like to have a dot after the first three levels, but not the other ones

Re: [NTG-context] Referencing equation, missing dot

On 11/13/2019 9:20 PM, Mikael P. Sundqvist wrote: Hi, The following example used to work. But with an LMTX updated today, the numbering \eqref produces is (11) instead of the expected (1.1). The numbering in the equation itself is fine. Did something change on purpose? /Mikael %%% TEST

[NTG-context] Referencing equation, missing dot

Hi, The following example used to work. But with an LMTX updated today, the numbering \eqref produces is (11) instead of the expected (1.1). The numbering in the equation itself is fine. Did something change on purpose? /Mikael %%% TEST FILE \definereferenceformat[eqref][left=(,right=)]

Re: [NTG-context] metafun 2

uot;, xlabels = "yes", ylabels = "yes", ycaption = "\strut\tfd \rotate[rotation=90]{vertical}", xcaption = "\strut\tfd horizontal", pointsymbol = "dot", pointsize = 4, pointcolor = "orange", sx = 2mm, sy = 4mm, li

Re: [NTG-context] metafun 2

yticks = "left", ysmall = 40, ylarge = 4, code = "1.5 * math.sin(2*x^2)", xlabels = "yes", ylabels = "yes", ycaption = "\strut\tfd \rotate[rotation=90]{vertical}", xcaption = "\strut\tfd horizontal&q

Re: [NTG-context] metafun 2

all = 40, ylarge = 4, code = "1.5 * math.sin(2*x^2)", xlabels = "yes", ylabels = "yes", ycaption = "\strut\tfd \rotate[rotation=90]{vertical}", xcaption = "\strut\tfd horizontal", pointsymbol = "dot&qu

Re: [NTG-context] metafun 2

ge = 4, code = "1.5 * math.sin(2*x^2)", xlabels = "yes", ylabels = "yes", ycaption = "\strut\tfd \rotate[rotation=90]{vertical}", xcaption = "\strut\tfd horizontal", pointsymbol = "dot", poin

[NTG-context] translating LyX/LaTex book into ConTeXt (was Re: [Context] Xindy)

onts which cover those diacritics well? When using LaTeX, accents were just handled by putting e.g. dot over 'm'. Any hint how to easily enter such things in one's editor? Now, I wonder how can one "define one's own sort order" since I'd like that words containing e.g. 'ṁ' are to be sor

Re: [NTG-context] devanagari is missing an accent in newest beta

urved stroke between two letters. Thanks Benct, but the little dot I think I see (actually a square shape) does not look like that. >Googling "eyelash repha" I found this: > > http://unicode.org/~emuller/iwg/p8/utcdoc.html The source standar

Re: [NTG-context] devanagari is missing an accent in newest beta

ing “accent” is a repha, a form of the consonant ra. It seems > > to have been replaced by a middle dot, to the right of the base > > consonant. I can’t be completely sure because it’s protruding into the > > next consonant so it’s almost indistinguishable from it, but I think > &

Re: [NTG-context] devanagari is missing an accent in newest beta

e older (perfect) output is in a comment above >> https://github.com/u-fischer/luaotfload/issues/9#issuecomment-426978522 > > The missing “accent” is a repha, a form of the consonant ra. It seems > to have been replaced by a middle dot, to the right of the base > consonant

Re: [NTG-context] devanagari is missing an accent in newest beta

the older (perfect) output is in a comment above > https://github.com/u-fischer/luaotfload/issues/9#issuecomment-426978522 The missing “accent” is a repha, a form of the consonant ra. It seems to have been replaced by a middle dot, to the right of the base consonant. I can’t be completely sure be

Re: [NTG-context] decomposed and precomposde glyphs

do it. The B with dot below (U+1E04) ends as BU+0323 in the pdf. But how does context does it? It uses the Unicode composition information (part of UnicodeData.txt), they’re made into a Lua table in ConTeXt (named char-def.lua, if it hasn’t changed). I know of char-def.lua but the question

Re: [NTG-context] decomposed and precomposde glyphs

Am Thu, 23 Feb 2017 17:20:05 +0100 schrieb Arthur Reutenauer: >> I looked at the code and it actually uses an idea that I had already >> tried. The problem I couldn't solve was do decompose a glyph. >> Looking at an context example it seems that context can do it. The B >>

Re: [NTG-context] decomposed and precomposde glyphs

> I looked at the code and it actually uses an idea that I had already > tried. The problem I couldn't solve was do decompose a glyph. > Looking at an context example it seems that context can do it. The B > with dot below (U+1E04) ends as BU+0323 in the pdf. But how does &g

Re: [NTG-context] decomposed and precomposde glyphs

decompose a glyph. Looking at an context example it seems that context can do it. The B with dot below (U+1E04) ends as BU+0323 in the pdf. But how does context does it? It doesn't happen with a similar latex example. There the U+1E04 is simply missing. And why is the dot of the first B better placed than

Re: [NTG-context] decomposed and precomposde glyphs

was do decompose a glyph. Looking at an context example it seems that context can do it. The B with dot below (U+1E04) ends as BU+0323 in the pdf. But how does context does it? It doesn't happen with a similar latex example. There the U+1E04 is simply missing. And why is the dot of the first B better plac

Re: [NTG-context] decomposed and precomposde glyphs

On 2/23/2017 3:05 PM, Ulrike Fischer wrote: Am Thu, 23 Feb 2017 14:08:54 +0100 schrieb Hans Hagen: btw, i suppose most context enter composed glyphs anyway instead of separate thingies But as my example (for the B with dot below) shows that this fails if the font hasn't the precomposed glyph

Re: [NTG-context] decomposed and precomposde glyphs

Am Thu, 23 Feb 2017 14:08:54 +0100 schrieb Hans Hagen: > btw, i suppose most context enter composed glyphs anyway instead of > separate thingies But as my example (for the B with dot below) shows that this fails if the font hasn't the precomposed glyph. Also the problem is not s

Re: [NTG-context] decomposed and precomposde glyphs

ed B+U+0323 for the B. >> >> With context (and lualatex) one get a rather bad looking -- as the >> dot is misplaced -- output for the A0323 input and no output at >> all for 1e04. >> >> As the coverage for precomposed glyphs varies a lot across fonts >> t

Re: [NTG-context] decomposed and precomposde glyphs

On 2/23/2017 11:58 AM, Ulrike Fischer wrote: When using input like the following with xetex then harfbuzz kicks in and one would always get the good looking precomposed U+1EA0 for the A and the decomposed B+U+0323 for the B. With context (and lualatex) one get a rather bad looking -- as the dot

[NTG-context] decomposed and precomposde glyphs

When using input like the following with xetex then harfbuzz kicks in and one would always get the good looking precomposed U+1EA0 for the A and the decomposed B+U+0323 for the B. With context (and lualatex) one get a rather bad looking -- as the dot is misplaced -- output for the A0323 input

Re: [NTG-context] Dot fills shifted down

Hello, the solution works fine, thank you! Best regards, Lukas On Tue, 31 Jan 2017 13:08:28 +0100, Otared Kavian wrote: Hi Lukas, Maybe you can use symbol=\lower.25em\hbox{.}, instead of what you set in your \definefiller definition is what you need? Best

Re: [NTG-context] Dot fills shifted down

Hi Lukas, Maybe you can use symbol=\lower.25em\hbox{.}, instead of what you set in your \definefiller definition is what you need? Best regards: OK > On 31 Jan 2017, at 12:33, Procházka Lukáš Ing. wrote: > > Hello, > > the following code: > > > \definefiller

[NTG-context] Dot fills shifted down

Hello, the following code: \definefiller [DotFill] [alternative=symbol, symbol=., width=.5em, style=\txx] Fill here: \filler[DotFill]{} produces filler with dots on the baseline. Is there a way to shift the dots a bit lower, bellow the baseline, e.g. to 0.25em

  1   2   3   4   5   6   >