On 1/15/2024 7:57 PM, Thomas A. Schmitz wrote:
Hi all,
not a complaint, just a question (for Hans and Wolfgang, I guess): in
recent versions of lmtx, Greek named characters (constructs such as
\greekdasiatonos) don't work any more. Which means I have to adapt some
of my older macros
Hi all,
not a complaint, just a question (for Hans and Wolfgang, I guess): in
recent versions of lmtx, Greek named characters (constructs such as
\greekdasiatonos) don't work any more. Which means I have to adapt some
of my older macros. Is this an oversight or did they get axed?
All best
44:38 AM
Subject [NTG-context] Re: Toggling the symbol for the zero-width joiner and
related Unicode control characters
(It seems he never considered making it an opentype feature in the font itself,
but since his focus is/was XeTeX/HB (HB is rather rigid and dictatorial) I
guess that's not surprising.
g the symbol for the zero-width joiner and
related Unicode control characters
** Caution: EXTERNAL Sender **
On 9/22/2023 2:39 PM, Hamid,Idris wrote:
b. we want all Unicode control symbols to be suppressed in final pdf output
(for, e.g., printing).
they basically are unless some font features
-- Original Message --
From "Hans Hagen" mailto:j.ha...@xs4all.nl>>
To "ntg-context@ntg.nl<mailto:ntg-context@ntg.nl>"
mailto:ntg-context@ntg.nl>>
Date 9/22/2023 7:15:25 AM
Subject [NTG-context] Re: Toggling the symbol for the zero-width joiner a
-- Original Message --
From "Hans Hagen" mailto:j.ha...@xs4all.nl>>
To "ntg-context@ntg.nl<mailto:ntg-context@ntg.nl>"
mailto:ntg-context@ntg.nl>>
Date 9/22/2023 7:03:34 AM
Subject [NTG-context] Re: Toggling the symbol for the zero-width joiner a
themselves with this issue.
?
Not really -) This brings us to the point of consistency: For Arabic-script fonts, hard
symbolic rendering of the Unicode control characters is the rule, not the exception. So
not "an inconsistent mess" -- at least not as far as Arabic-script typography
is
Hi,
I found it ...
\startbuffer
\definedfont[almfixed*default]hello w\zwnj o\zwj r\zwnj l\zwj d
\stopbuffer
\getbuffer
\start
\setcharacterstripping[1]
\getbuffer
\stop
so now, being its only user, you have to wikify it ...
Hans
53:03 AM
Subject [NTG-context] Re: Toggling the symbol for the zero-width joiner and
related Unicode control characters
1. Can this approach be generalized to get what we want, viz., a way to toggle
the symbols?
given the inconsistency in what is or is not in a font the only way out
is to have ou
/21/2023 3:29:22 PM
Subject Re: [NTG-context] Re: Toggling the symbol for the zero-width joiner and
related Unicode control characters
Many thanks, Hans. The method appears to work only for nbsp, not zwj etc.
Here is the updated MWE:
===
\startTEXpage[offset=1em]
\disabletrackers[typesett
e: Toggling the symbol for the zero-width joiner and
related Unicode control characters
Many thanks, Hans. The method appears to work only for nbsp, not zwj etc.
Here is the updated MWE:
===
\startTEXpage[offset=1em]
\disabletrackers[typesetters.directions]
\disabletrackers[typesetters.zwj]
\di
Toggling the symbol for the zero-width joiner and
related Unicode control characters
** Caution: EXTERNAL Sender **
On 9/21/2023 3:31 PM, Hamid,Idris wrote:
Dear gang,
Within a font, relevant Unicode control characters such as the zero-width
joiner usually have symbolic representation, but in printi
-- Original Message --
From "Hans Hagen" mailto:j.ha...@xs4all.nl>>
To "ntg-context@ntg.nl<mailto:ntg-context@ntg.nl>"
mailto:ntg-context@ntg.nl>>
Date 9/21/2023 8:52:45 AM
Subject [NTG-context] Re: Toggling the symbol for the zero-width joiner a
On 9/21/2023 3:31 PM, Hamid,Idris wrote:
Dear gang,
Within a font, relevant Unicode control characters such as the zero-width
joiner usually have symbolic representation, but in printing the symbols are
usually suppressed, while the effect of each character is maintained.
In some text
Dear gang,
Within a font, relevant Unicode control characters such as the zero-width
joiner usually have symbolic representation, but in printing the symbols are
usually suppressed, while the effect of each character is maintained.
In some text editors, such as Windows Notepad (Uniscribe
On 8/13/2023 12:56 AM, Hamid,Idris wrote:
On Aug 12, 2023, 4:20 PM -0600, Hans Hagen , wrote:
btw, no need for squeezine as there are virtual commands for scaling; not for
rotating
From your original CLD template:
local function topthing(characters,target,base,accent
On Aug 12, 2023, 4:20 PM -0600, Hans Hagen , wrote:
> btw, no need for squeezine as there are virtual commands for scaling; not for
> rotating
From your original CLD template:
local function topthing(characters,target,base,accent)
--if not characters[target] then
local
More precise \rlaps for the previous MWE:
\hbox{\rlap{\ruledhbox {\transparentgreen\tfx c\symbol{glottalhamzah}c}}%
\hskip-.075em \ruledhbox {\transparentred c\symbol{glottalhamzah}c}}
\hbox{\rlap{\ruledhbox {\transparentgreen\tfx c\symbol{glottalayn}c}}%
\hskip-.075em
r results. The overwhelming majority of hq fonts
don't have them, and the few that do do them poorly, etc.
(So there is no substitute for full control of these transliteration
characters.)
So even if we use symbols, would like to feed these setups to the CLD template
you provided some days ago
the templates that you provided - many, many thanks! - have what is needed
to care of everything except for two characters: 02BE and 02BF.
you'll figure it out, right?
For one of those two remaining characters we also need scaling, for the other
we also need scaling + rotation
needed
to care of everything except for two characters: 02BE and 02BF.
For one of those two remaining characters we also need scaling, for the other
we also need scaling + rotation. It is not clear to me whether the
scaling/rotation commands should fall under the character function, e.g.,
=
On 8/12/2023 8:05 PM, Hamid,Idris wrote:
On Aug 12, 2023, 9:35 AM -0600, Hans Hagen , wrote:
** Caution: EXTERNAL Sender **
On 8/12/2023 4:03 PM, Hamid,Idris wrote:
\tfx causes a switch to computer modern.
Indeed. Something I need to discuss with Wolfgang as double checking is needed
before
in the new regime -)]
Now the templates that you provided - many, many thanks! - have what is needed
to care of everything except for two characters: 02BE and 02BF.
For one of those two remaining characters we also need scaling, for the other
we also need scaling + rotation. It is not clear to me
On 8/12/2023 4:03 PM, Hamid,Idris wrote:
\tfx causes a switch to computer modern.
Indeed. Something I need to discuss with Wolfgang as double checking is
needed before I patch.
But what if we want to scale independently of font switching?
There is no need to go lua here (esp when you have
riments:
https://www.dropbox.com/scl/fi/dggj3ypgjjeia1bo4eelb/test-scaling.tex?rlkey=hcky6ol594mw8u0j2j1z22heh=0
https://www.dropbox.com/scl/fi/o2u1tsq515ycyoeup43qg/test-scaling.pdf?rlkey=h7gof1vyq3r0bh72qynh71apc=0
IV. Objective:
I need to be able to define a couple of characters in CLD -- glot
Ṣ {\d{S}}
\defineactivecharacter ṣ {\d{s}}
\stoptext
This should not produce any typeset output but in lmtx it does.
Background: The following characters are essential for Arabic transliteration
(assuming your email client has the chars):
Ṯṯ Ḥḥ Ḫḫ Ḏḏ Šš Ṣṣ Ḍḍ Ṭṭ Ẓẓ Ġġ Āā Īī Ūū ʿ ʾ
I'd use
any typeset output but in lmtx it does.
Background: The following characters are essential for Arabic transliteration
(assuming your email client has the chars):
Ṯṯ Ḥḥ Ḫḫ Ḏḏ Šš Ṣṣ Ḍḍ Ṭṭ Ẓẓ Ġġ Āā Īī Ūū ʿ ʾ
I'd use a different font but as you want to go cheap ... attached gets
you going
.
Background: The following characters are essential for Arabic transliteration
(assuming your email client has the chars):
Ṯṯ Ḥḥ Ḫḫ Ḏḏ Šš Ṣṣ Ḍḍ Ṭṭ Ẓẓ Ġġ Āā Īī Ūū ʿ ʾ
But most really good fonts don't have them, so we have to compose them. Now
there are other methods, e.g,
1) \definecharacter
On Tue, 9 Aug 2022, Henning Hraban Ramm via ntg-context wrote:
> Am 09.08.22 um 18:57 schrieb Wolfgang Schuster via ntg-context:
> > Henning Hraban Ramm via ntg-context schrieb am 09.08.2022 um 16:51:
> >> I actually never really looked into the nodes module, but I guess that
> >> would work.
>
Am 09.08.22 um 18:57 schrieb Wolfgang Schuster via ntg-context:
Henning Hraban Ramm via ntg-context schrieb am 09.08.2022 um 16:51:
I actually never really looked into the nodes module, but I guess that
would work.
There is a simple LaTeX / plain TeX package [1] for this but I don't
know if
Henning Hraban Ramm via ntg-context schrieb am 09.08.2022 um 16:51:
Am 08.08.22 um 08:01 schrieb Alan Braslau:
On 05/08/22 05/08/22, 12:13, Henning Hraban Ramm via ntg-context wrote:
I recently had the same problem and was wondering if there isn’t a
Metapost module for directory trees?
Am 08.08.22 um 08:01 schrieb Alan Braslau:
On 05/08/22 05/08/22, 12:13, Henning Hraban Ramm via ntg-context wrote:
I recently had the same problem and was wondering if there isn’t a
Metapost module for directory trees?
There is a Metapost/Context module for drawing flow charts that should
On 05/08/22 05/08/22, 12:13, Henning Hraban Ramm via ntg-context wrote:
I recently had the same problem and was wondering if there isn’t a
Metapost module for directory trees?
There is a Metapost/Context module for drawing flow charts that should
handle this nicely.
There is also a
I guess that I could define a fallbackfont. Do anyone know the unicode
range that should be covered and the font that has these characters?
You need box drawing [1] characters.
When you need fonts with a wide range of character the Noto [2] family
is a good choice.
Yes, also e.g. Segoe
juh+ntg-context--- via ntg-context schrieb am 05.08.2022 um 19:04:
Dear all,
I have this:
\starttext
\starttyping
foo
└── bar
├── baz
│ └── index.html
└── index.html
\stoptyping
\stoptext
The source code is generated with the linux command "tree".
The special
Dear all,
I have this:
\starttext
\starttyping
foo
└── bar
├── baz
│ └── index.html
└── index.html
\stoptyping
\stoptext
The source code is generated with the linux command "tree".
The special characters which indicate the folder depth are not displayed.
I gu
Hello all,
typesetting accented characters in eulernova font does not seem
possible to me. Is it really impossible? The other math fonts
(stix/xits) do it. I'm using Context LMTX 2022.01.21 20:13
\starttext
\switchtobodyfont[eulernova]
\startlines
euler:
1 - č
2 - \ccaron
3 - \v{c}
\stoplines
\noligature{Th}is
\noligature{Th}at
\noligature{Th}en
\stoptext
Von: ntg-context Im Auftrag von Ben Moon via
ntg-context
Gesendet: Freitag, 13. Mai 2022 15:30
An: Context Mailing List
Cc: Ben Moon
Betreff: Re: [NTG-contex
I've just update and blockligatures=yes is working again; thanks very much Hans.
Ben
On Fri, 13 May 2022, at 14:29, Ben Moon via ntg-context wrote:
> Thanks Hans,
>
> I tried to modify your example for preventing the capital-Th ligature but
> this doesn't seem to work. The 'fi' ligature is
Thanks Hans,
I tried to modify your example for preventing the capital-Th ligature but this
doesn't seem to work. The 'fi' ligature is prevented, but 'Th' still appears as
a ligature. This occurs with the original lowercase version too. Have I missed
something?
```
\startluacode
local
. Mai 2022 15:03
> An: ntg-context@ntg.nl
> Cc: Hans Hagen
> Betreff: Re: [NTG-context] blockligatures removing characters
>
> On 5/9/2022 9:56 AM, Denis Maier via ntg-context wrote:
> > Happens here as well, already on ConTeXt ver: 2022.03.12 17:56 LMTX.
> >
>
On 5/9/2022 9:56 AM, Denis Maier via ntg-context wrote:
Happens here as well, already on ConTeXt ver: 2022.03.12 17:56 LMTX.
By the way, this even happens without special fonts:
\blockligatures[Th]
\definefontfeature[default:blocklig][default][liga=yes,blockligatures=yes]
*default:blocklig]
The This These are missing the `h'
\stoptext
Von: ntg-context Im Auftrag von Ben Moon via
ntg-context
Gesendet: Samstag, 7. Mai 2022 17:49
An: Context Mailing List
Cc: Ben Moon
Betreff: [NTG-context] blockligatures removing characters
Hi List,
I'm using blockligatures to avoid
Hi List,
I'm using blockligatures to avoid the 'Th' ligature in some fonts but keep
others. Recently I've found this removes the 'h' completely, i.e. 'Th' is
changed to 'T', 'The' becomes 'Te' etc.
Is there a way to restore the blockligatures functionality? I'm on ConTeXt
version 2022.05.02
On the rare chance that someone else stumbles across this problem ...
By default, Java's Xalan transformer for creating XML documents does not
correctly encode emojis. Instead of for the thumbs up emoji,
Xalan encodes it as . As Arthur pointed out, this is not a
valid entity encoding.
One
On Wed, Mar 30, 2022 at 12:32:11AM -0700, Thangalin via ntg-context wrote:
> An XML document includes the emoji, as shown in the following snippet:
>
>
>
>
>
> Thumbs up emoji:
Try the correct escape sequence :-) That’s -- or
equivalently
Best,
Hi list,
An XML document includes the emoji, as shown in the following snippet:
Thumbs up emoji:
The document is typeset using ConTeXt, but the thumbs up emoji isn't in the
PDF. Neither Noto Emoji nor Open Sans Emoji fonts will render.
Does anyone have a minimal
Hi Hans,
ok, thank you, lmtx is a good way.
Tomáš
> I would like to ask what is the cause of this behavior and how to
> use the \doifinstring to prevent the "fbf@" on the output.
partial expansion of a protected macro where one doesn't expect it
before i patch i let wolfgang check it
btw, you
On 10/31/2021 11:53 PM, Tomas Hala via ntg-context wrote:
I would like to ask what is the cause of this behavior and how to
use the \doifinstring to prevent the "fbf@" on the output.
btw, you can prevent it by using lmtx
Hans
-
On 10/31/2021 11:53 PM, Tomas Hala via ntg-context wrote:
Hi all,
I noticed that \doifinstring produces quite strange output if a command
follows immediately (or with any amount of spaces) after the substring
I am searching for:
-MWE
\starttext
\def\xxx{asdf
Hi all,
I noticed that \doifinstring produces quite strange output if a command
follows immediately (or with any amount of spaces) after the substring
I am searching for:
-MWE
\starttext
\def\xxx{asdf \bf Z:\bf asdf} % strange
\def\xxx{asdf \bf Z:
Benct Philip Jonsson schrieb am 11.03.2021 um 18:37:
In a program I'm writing I have a function for escaping characters which
are reserved or problematic in LaTeX. I would like to have a
corresponding function for ConTeXt, so I'm wondering which ones are
different/superfluous/missing from
In a program I'm writing I have a function for escaping characters which
are reserved or problematic in LaTeX. I would like to have a corresponding
function for ConTeXt, so I'm wondering which ones are
different/superfluous/missing from a ConTeXt perspective in the following
list (sorry about
Pablo Rodriguez schrieb am 11.11.2020 um 16:37:
On 11/11/20 10:08 AM, n...@scorecrow.com wrote:
Sorry for this really, really basic question but...
I have the following 3 line source file:
\starttext
\typefile{test-listing.txt}
\stoptext
Hi Bruce,
a MWE that shows your problem would be:
On 11/11/20 10:08 AM, n...@scorecrow.com wrote:
> Sorry for this really, really basic question but...
>
> I have the following 3 line source file:
>
> \starttext
> \typefile{test-listing.txt}
> \stoptext
Hi Bruce,
a MWE that shows your problem would be:
\setupbodyfont[cursor]
\starttext
Sorry for this really, really basic question but...
I have the following 3 line source file:
\starttext
\typefile{test-listing.txt}
\stoptext
The file "test-listing.txt" is UTF-8 and includes the character U+25B8 (black
right-pointing small triangle) which is being dropped from the output.
Dear List,
Is there any way to give a sequence of fonts to context and let it try one
after another in case of missing characters? Ideally it should be something
like \usefallback[font1,font2,font3,...]
The methods I've found are all way too complicated for someone who does not
really care about
Arg, it's getting uglier...
I've been playing around with the replacement patterns.
```
\replaceword[replace][auff][au{ff}]
\replaceword[replace][Aufl][Au{fl}]
\replaceword[replace][aufl][au{fl}]
\setreplacements[replace]
\starttext
auffasste
auffasse
Auflage
aufliegen
auffliegen
On 10/8/2020 3:15 PM, Denis Maier wrote:
Ok,
I've commented the whole nolig-german-wordlist out piece by piece, and
it looks like it comes down to this:
```
\replaceword[eka][auffasse][au{ff}asse]
\replaceword[eka][auffasst][au{ff}asst]
\setreplacements[eka]
\starttext
auffasste
auffasse
Next try,
the compact syntax gives the same weird result:
```
\replaceword[replace][au{ff}asse au{ff}asst]
\setreplacements[replace]
\starttext
auffasste
auffasse
\stoptext
```
I would really like to have correct ligatures. What can I do to help
finding the reason for this? (Or is
> Am 08.10.2020 um 13:04 schrieb Hans Hagen :
>
> On 10/8/2020 12:02 PM, Denis Maier wrote:
>> Hi,
>> I do as adviced on the Wiki and input the nolig-german-wordlist.tex to
>> suppress wrong ligatures. However, I'm seeing strange results:
>> ```
>> \input nolig-german-wordlist.tex
>>
Hi,
I do as adviced on the Wiki and input the nolig-german-wordlist.tex to
suppress wrong ligatures. However, I'm seeing strange results:
```
\input nolig-german-wordlist.tex
\starttext
auffasste
auffasse
\stoptext
```
gives me "auffasse auffasse" (see attachment.)
I don't really
Ok,
I've commented the whole nolig-german-wordlist out piece by piece, and
it looks like it comes down to this:
```
\replaceword[eka][auffasse][au{ff}asse]
\replaceword[eka][auffasst][au{ff}asst]
\setreplacements[eka]
\starttext
auffasste
auffasse
\stoptext
```
Uncommenting one of the
Am 08.10.2020 um 13:04 schrieb Hans Hagen:
On 10/8/2020 12:02 PM, Denis Maier wrote:
Hi,
I do as adviced on the Wiki and input the nolig-german-wordlist.tex
to suppress wrong ligatures. However, I'm seeing strange results:
```
\input nolig-german-wordlist.tex
\starttext
auffasste
auffasse
On 10/8/2020 12:02 PM, Denis Maier wrote:
Hi,
I do as adviced on the Wiki and input the nolig-german-wordlist.tex to
suppress wrong ligatures. However, I'm seeing strange results:
```
\input nolig-german-wordlist.tex
\starttext
auffasste
auffasse
\stoptext
```
gives me "auffasse auffasse"
Am 07.10.2020 um 17:19 schrieb Wolfgang Schuster:
Denis Maier schrieb am 07.10.2020 um 17:16:
Am 07.10.2020 um 16:47 schrieb Wolfgang Schuster:
Denis Maier schrieb am 07.10.2020 um 15:42:
[...]
Unfortunately, the clickable link is still not correct. What am I
doing wrong?
Add
Denis Maier schrieb am 07.10.2020 um 17:16:
Am 07.10.2020 um 16:47 schrieb Wolfgang Schuster:
Denis Maier schrieb am 07.10.2020 um 15:42:
Hi,
I'm struggling with getting hyphenated URLs to work from XML input.
How do you enter ampersands and percent signs correctly so that they
can be used
Am 07.10.2020 um 16:47 schrieb Wolfgang Schuster:
Denis Maier schrieb am 07.10.2020 um 15:42:
Hi,
I'm struggling with getting hyphenated URLs to work from XML input.
How do you enter ampersands and percent signs correctly so that they
can be used in links?
This here doesn't really works:
Denis Maier schrieb am 07.10.2020 um 15:42:
Hi,
I'm struggling with getting hyphenated URLs to work from XML input.
How do you enter ampersands and percent signs correctly so that they
can be used in links?
This here doesn't really works:
\startxmlsetups xml:test
Hi,
I'm struggling with getting hyphenated URLs to work from XML input.
How do you enter ampersands and percent signs correctly so that they can
be used in links?
This here doesn't really works:
\startxmlsetups xml:test
\xmlsetsetup{#1}{*}{-}
% Hauptgruppen
4/23/2020 17:50, Wolfgang Schuster wrote:
>> Benjamin Buchmuller schrieb am 23.04.2020 um 23:16:
>>> Hi Rik,
>>>
>>> Thanks for the fast reply! Your example works indeed nicely. However,
>>> within this solution my problem has shifted now (fully) towards
On 4/23/2020 17:50, Wolfgang Schuster wrote:
Benjamin Buchmuller schrieb am 23.04.2020 um 23:16:
Hi Rik,
Thanks for the fast reply! Your example works indeed nicely. However,
within this solution my problem has shifted now (fully) towards
breaking after the same number of characters, which
nicely. However, within
>> this solution my problem has shifted now (fully) towards breaking after the
>> same number of characters, which seems to work for your sample string, but
>> not for the sequences that I need to place.
>> What I would like to achie
Benjamin Buchmuller schrieb am 23.04.2020 um 23:16:
Hi Rik,
Thanks for the fast reply! Your example works indeed nicely. However, within
this solution my problem has shifted now (fully) towards breaking after the
same number of characters, which seems to work for your sample string
Hi Rik,
Thanks for the fast reply! Your example works indeed nicely. However, within
this solution my problem has shifted now (fully) towards breaking after the
same number of characters, which seems to work for your sample string, but not
for the sequences that I need to place.
What I would
” the default \setbreakpoints[compound]?
On 23 Apr 2020, at 20:46, Benjamin Buchmuller
wrote:
Hi again,
I am reading a CSV file into ConTeXt which contains long DNA sequences (>> 40
characters) to place in xtables. So far, this works fine. However, I need to
uppercase the entries an
23 Apr 2020, at 20:46, Benjamin Buchmuller
> wrote:
>
> Hi again,
>
> I am reading a CSV file into ConTeXt which contains long DNA sequences (>> 40
> characters) to place in xtables. So far, this works fine. However, I need to
> uppercase the entries and need to \
Hi again,
I am reading a CSV file into ConTeXt which contains long DNA sequences (>> 40
characters) to place in xtables. So far, this works fine. However, I need to
uppercase the entries and need to \tt them. When I do this inside \WORD
however, they don’t hyphenate any more.
I’m
Wolfgang Schuster
>>>>> >>>> <mailto:wolfgang.schuster.li...@gmail.com>> wrote:
>>>>>
>>>>> Gerben Wierda schrieb am 29.03.2020 um 12:52:
>>>>>> I am using MetaFun (Lua code) to create METAPOST commands from a
t; wrote:
Gerben Wierda schrieb am 29.03.2020 um 12:52:
I am using MetaFun (Lua code) to create METAPOST commands from an
XML file. One of the issues I am running into that in METAPOST I
have to handle strings with " characters in them and METAPOST
doesn’t like those. The argument using th
am using MetaFun (Lua code) to create METAPOST commands from an XML
>>>> file. One of the issues I am running into that in METAPOST I have to
>>>> handle strings with " characters in them and METAPOST doesn’t like those.
>>>> The argument using the string
&
> On 29 Mar 2020, at 12:58, Wolfgang Schuster
> wrote:
>
> Gerben Wierda schrieb am 29.03.2020 um 12:52:
>> I am using MetaFun (Lua code) to create METAPOST commands from an XML file.
>> One of the issues I am running into that in METAPOST I have to handle
>
strings with "
characters in them and METAPOST doesn’t like those. The argument using the string
Foo "Bar” Foo
^^^
Use correct left quotation marks or \quotation{…}.
I’m not hard coding the string, I’m reading it from an XML. So, whatever I do,
I need to do it by manipulating
I am using MetaFun (Lua code) to create METAPOST commands from an XML file. One
of the issues I am running into that in METAPOST I have to handle strings with
" characters in them and METAPOST doesn’t like those. The argument using the
string
Foo "Bar” Foo
turns into
someCall( &quo
Gerben Wierda schrieb am 29.03.2020 um 12:52:
I am using MetaFun (Lua code) to create METAPOST commands from an XML file. One of
the issues I am running into that in METAPOST I have to handle strings with "
characters in them and METAPOST doesn’t like those. The argument using the string
illa
and have included the following with my setups:
% Additional Characters
\definecharacter llowmacron {\buildtextmacron l}
\definecharacter Llowmacron {\buildtextmacron L}
\definecharacter nlowmacron {\buildtextmacron n}
\definecharacter Nlowmacron {\buildtextmacron N}
\definecharacter rlowma
onal Characters
\definecharacter llowmacron {\buildtextmacron l}
\definecharacter Llowmacron {\buildtextmacron L}
\definecharacter nlowmacron {\buildtextmacron n}
\definecharacter Nlowmacron {\buildtextmacron N}
\definecharacter rlowmacron {\buildtextmacron r}
\definecharacter Rlowmacron {\buildtextmacr
I am using Latin Modern Roman to typeset some proceedings and need the
following characters in regular, italic, and small caps:
Character: ṉ U+1E49
Name: LATIN SMALL LETTER N WITH LINE BELOW
Character: Ṉ U+1E48
Name: LATIN CAPITAL LETTER N WITH LINE BELOW
Character: ḻ U+1E3B
Name: LATIN SMALL
Dear list,
I have the following sample:
\setupbodyfont[gentium, 60pt]
\starttext
Combined: τῇ
Precomposed: τῇ
\stoptext
Is there an automatic way in LuaTeX to get the precomposed character
from combining ones without having to add a feature?
Many thanks for your help,
Dear Hans,
Thank you so much for a new code which works fine.
It can be used for the title of chapters.
I will play with this to make a nice title.
Thank you again.
Best regards,
Dalyoung
> 2018. 9. 28. 오전 12:43, Hans Hagen 작성:
>
> On 9/27/2018 5:06 PM, Jeong Dal wrote:
>> Dear Hans,
>>
On 9/27/2018 5:06 PM, Jeong Dal wrote:
Dear Hans,
First, I appreciate for your concerning and sharing your valuable time on this
matter.
I think that there is no one who has an interest in outlining Korean letters.
It is my self-interest to use outlined text for titles of chapters.
As we
> <mailto:j.ha...@xs4all.nl>> 작성:
>>>
>>> On 9/26/2018 2:14 PM, Jeong Dal wrote:
>>>> Dear Hans,
>>>> I tested for more characters and found an interesting fact.
>>>> If the first consonant and the vowels are connected in a glyph, the
On 9/26/2018 11:38 PM, Jeong Dal wrote:
Dear Hans,
2018. 9. 26. 오후 9:24, Hans Hagen <mailto:j.ha...@xs4all.nl>> 작성:
On 9/26/2018 2:14 PM, Jeong Dal wrote:
Dear Hans,
I tested for more characters and found an interesting fact.
If the first consonant and the vowels are connected i
Dear Hans,2018. 9. 26. 오후 9:24, Hans Hagen <j.ha...@xs4all.nl> 작성:On 9/26/2018 2:14 PM, Jeong Dal wrote:Dear Hans,I tested for more characters and found an interesting fact.If the first consonant and the vowels are connected in a glyph, then the outlining works OK, otherwise, it makes o
On 9/26/2018 2:14 PM, Jeong Dal wrote:
Dear Hans,
I tested for more characters and found an interesting fact.
If the first consonant and the vowels are connected in a glyph, then the
outlining works OK, otherwise, it makes outline of the first consonant only.
you need to send a file
Dear Hans,
I tested for more characters and found an interesting fact.
If the first consonant and the vowels are connected in a glyph, then the
outlining works OK, otherwise, it makes outline of the first consonant only.
Here is a MWE.
Thank you.
Best regards,
Dalyoung
Dear Hans,
I have tested using your code. I just replace “N”, “T” with Korean letters.
Here is an MWE which is a simplified version of your code.
I tested using two fonts, and the outputs are different.
Thank you for your concern.
Best regards,
Dalyoung
%%%
fi ;
draw pathpart i
withpen pencircle scaled 1/10
withcolor KoreanColors[n] ;
endfor ;
enddef ;
% entered as three characters: ᄅ ᅡ ᆺ (mail collapses)
KoreanOutline("\KoreanFont 랏") ;
\stopMPpage
\stoptext
The prescr
On 9/26/2018 1:48 AM, Jeong Dal wrote:
Dear Hans,
First, it is great to know a new method of drawing an outlined font!
I have applied it to Korean fonts. As you know, every Korean character is
composed with “consonant+vowel(+consonant)” type. If consonant and vowel are
connected (for
Dear Hans,
First, it is great to know a new method of drawing an outlined font!
I have applied it to Korean fonts. As you know, every Korean character is
composed with “consonant+vowel(+consonant)” type. If consonant and vowel are
connected (for example, “호”), then it draws correctly,
1 - 100 of 549 matches
Mail list logo
