On 12/10/2021 8:20 AM, Henning Hraban Ramm via ntg-context wrote:
Am 09.12.21 um 19:00 schrieb Henning Hraban Ramm via ntg-context:
\starttext
\WORD{größer}
\stoptext
\WORD used to handle "ß" correctly, i.e. convert it to "SS"; now it
makes "sS".
(If the current font contains an uppercase
Dear list,
I dived into m-grap.mpiv and found that "log" coordinates are now called
"logarithmic". So
setcoords(logarithmic, linear)
is the new way and it works with the last ConTeXt version.
Jean-Philippe,
> Le 8 déc. 2021 à 11:49, Jean-Philippe Rey via ntg-context
> a écrit :
>
>
Am 09.12.21 um 19:00 schrieb Henning Hraban Ramm via ntg-context:
\starttext
\WORD{größer}
\stoptext
\WORD used to handle "ß" correctly, i.e. convert it to "SS"; now it
makes "sS".
(If the current font contains an uppercase ß that would be even better,
but those are rare).
I can’t tell
Dear Hans, Bruce Horrocks,
I test the file using MacVim and confirm that it works fine.
Thus, something happened in my system or environment of vscode.
I may reinstall vscode.
Thank you.
Best regards,
Dalyoung
___
Dear Bruce Horrocks,
Thank you for your test.
I have moved the file to the local and run it. But the result is same.
However, since your try worked well, the problem is mine not LMTX.
I am using the editor “vscode”, and there may be something changed in my system
recently.
I’ll try using other
Dear Hans,
>> Documents/com~apple~CloudDocs/texMain/ColumnsetTest.tex''" terminated
>> with exit code: 1.*
> no clue ... does lmtx also fail? is it an apple binary issue?
I am running LMTX now.
It opens and closes "*-newcolumnsets.mkiv” files(we can find the lines in the
log file).
I also
\starttext
\WORD{größer}
\stoptext
\WORD used to handle "ß" correctly, i.e. convert it to "SS"; now it
makes "sS".
(If the current font contains an uppercase ß that would be even better,
but those are rare).
I can’t tell when it changed (some LMTX versions ago) and can’t check
MkIV,
Am 30.11.21 um 16:17 schrieb Hans Hagen via ntg-context:
Another question: what do you mean with a dy-shift version?
Nested bars have a parameter ‘dy’ which controls the vertical shifts
needed to make sure that they do not overlap. Text backgrounds do not
have that option at all.
i've
> On 9 Dec 2021, at 16:32, Hans Hagen via ntg-context
> wrote:
>
> On 12/9/2021 1:27 PM, Jeong Dal via ntg-context wrote:
>
>> error messages:
>
>> Documents/com~apple~CloudDocs/texMain/ColumnsetTest.tex', result
>> '/Users/graph/Library/Mobile
>
>>
Denis Maier via ntg-context schrieb am 09.12.2021 um 18:24:
Thanks for all the answers. That's helpful. But I think that does not work with
the xml tests, or does it? I mean, is this a general mechanism?
Since you didn't provide a example with your problem there is no way to
tell how to
Thanks for all the answers. That's helpful. But I think that does not work with
the xml tests, or does it? I mean, is this a general mechanism?
Denis
Von: ntg-context im Auftrag von Hans Hagen via
ntg-context
Gesendet: Donnerstag, 9. Dezember 2021
On 12/9/2021 5:30 PM, Joey McCollum via ntg-context wrote:
Thanks for correcting that, Wolfgang. I must have added the other \fi
instances because I was trying to use \orelse in MKIV and couldn't get
it to work. Is it only supported in LMTX?
yes, it's one of the native luametatex features
Thanks for correcting that, Wolfgang. I must have added the other \fi
instances because I was trying to use \orelse in MKIV and couldn't get it
to work. Is it only supported in LMTX?
Joey
On Thu, Dec 9, 2021 at 11:30 AM Hans Hagen via ntg-context <
ntg-context@ntg.nl> wrote:
> On 12/9/2021 5:11
On 12/9/2021 1:27 PM, Jeong Dal via ntg-context wrote:
error messages:
Documents/com~apple~CloudDocs/texMain/ColumnsetTest.tex', result
'/Users/graph/Library/Mobile
Documents/com~apple~CloudDocs/texMain/ColumnsetTest.tex''" terminated
with exit code: 1.*
no clue ... does lmtx also fail?
On 12/9/2021 5:11 PM, Wolfgang Schuster via ntg-context wrote:
Joey McCollum via ntg-context schrieb am 09.12.2021 um 15:08:
I believe \orelse might be what you want. It works with most \if...
macros, and it avoids nesting of \doifelse constructs. Here's an
example, which I use in
Joey McCollum via ntg-context schrieb am 09.12.2021 um 15:08:
I believe \orelse might be what you want. It works with most \if...
macros, and it avoids nesting of \doifelse constructs. Here's an
example, which I use in conditionally removing preceding punctuation
if any other keys are defined
I believe \orelse might be what you want. It works with most \if... macros,
and it avoids nesting of \doifelse constructs. Here's an example, which I
use in conditionally removing preceding punctuation if any other keys are
defined before a specific one in an assignment:
```
% If any of the
Dear all,
I made an exam form by the help of the experts in this list.
However, it was not working after recent update.
Here is a code which I made for the test.
If I use “\startcolumns \stopcolumns”, then it has no problem.
But using “\startcolumnset[exam] … \stopcolumnset” produces error
Hi,
I was wondering whether we have tests similar to or in context's xml processing. (And even in context more general...) I have
found these doifelse tests, but elseif doesn't seem to exist. Is that correct?
If yes, could that be added? Of course, you can always just nest
19 matches
Mail list logo
