to figure it out).
The only problem is that the offsets of glyphs are a bit inaccurate,
which may be related to the font,
and I will look into it further.
in the vertical feature one can tune a bit.
The examples I have adjusted are attached,
and the output PDF of them is not attached
need to add it as a
feature if it's not already available in some way.
—
Bruce Horrocks
Hampshire, UK
___
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist : ntg-context@nt
On 7/20/2022 9:40 PM, Bruce Horrocks via ntg-context wrote:
On 20 Jul 2022, at 05:31, Michael Urban via ntg-context
wrote:
Aside from purchasing a real font product from Linotype at enormous expense and
hoping it is better equipped, is there a way to coerce ConTeXt into using the
ve a lot of features in the first place I've so far
>> not noticed any problems. I'm sure a real expert could tell you how to
>> retain 'default' and add the ligatures, if needed.
>
> Hi Bruce, you can simply inherit your feature sets from default:
>
> \definefontfeature [venetian
the ligatures, if needed.
Hi Bruce, you can simply inherit your feature sets from default:
\definefontfeature [venetian-301-demi-ligatures][default][v1=yes,v3=yes]
\definefontfeature [venetian-301-BT-ligatures][default][v2=yes,v3=yes]
I’d like to borrow your example for my book, if you don’t object.
Hraban
> On 20 Jul 2022, at 05:31, Michael Urban via ntg-context
> wrote:
>
> Aside from purchasing a real font product from Linotype at enormous expense
> and hoping it is better equipped, is there a way to coerce ConTeXt into using
> the ligature glyphs for fi and fl?
Yes - I had to do the same
On 7/20/2022 6:31 AM, Michael Urban via ntg-context wrote:
I downloaded something that purports to be Century Expanded from fontsgeek.com.
Although the font has fi and fl ligature glyphs, it does not have a ligature
font feature and ConTeXt does not use those glyphs.
Aside from purchasing
I downloaded something that purports to be Century Expanded from fontsgeek.com.
Although the font has fi and fl ligature glyphs, it does not have a ligature
font feature and ConTeXt does not use those glyphs.
Aside from purchasing a real font product from Linotype at enormous expense
not
change to medium indentation. Is this a bug or a feature (i.e., should I
change something to work properly in both environments)?
___
If your question is of interest to others as well, please add an entry
quot;thank you" for everyone's feedback! We've implemented the first
point as suggested, with the second still in discussion. The next pandoc
version will also feature better table support for ConTeXt.
Thanks again, ConTeXt is a wonderful tool!
Best,
Albert
PS: For completeness, this
That is progress, Garulfo, and real progress! I'm sorry I have not been
any help to you in achieving this... a bit beyond my skill set. But I
have long regarded this particular 'feature' to be a quite important
'missing' feature of ConTeXt, since I occasionally get requests from
authors
at this is the cleanest way. Probably it's better to
define a separate font feature for microtypography rather than
overwriting the default set, but this definitely works:
\definefontfeature[default][default]
[protrusion=quality,
expansion=quality]
\setupbodyfont[modern] % or whatever
tivate the
> > microtypography functionality in a ConTeXt document.
> >
> > My question is: what is the most correct and clean way to do it?
>
> I do not claim that this is the cleanest way. Probably it's better to
> define a separate font feature for microtypography rathe
t and clean way to do it?
I do not claim that this is the cleanest way. Probably it's better to
define a separate font feature for microtypography rather than
overwriting the default set, but this definitely works:
\definefontfeature[default][default]
[protrusion=quality,
Dear list,
I wonder whether there is a conditional for font features similar to
\doifelseitalic.
\doifelsecurrentfonthasfeature checks whether the font supports an
OpenType feature.
\doifunknownfontfeature checks whether the font feature has been defined.
It seems that \doifelsefontfeature
}
{yes}{no}\\
\feature[+][asc]
text
\doifelsecurrentfonthasfeature{asc}
{yes}{no}
\doifelsefontfeature{asc}
{yes}{no}
\doifunknownfontfeature{asc}
{yes}{no}
\stopTEXpage
\stoptext
Sorry, but which is the right way to check when the font feature is
being deployed?
Many thanks
More a feature as \define defines a protected macro.
\starttext
\define\somelist{foo,bar,baz}
{\tt\meaningasis\somelist}
\getcommacommandsize[\somelist] \commalistsize
\defineexpandable\somelist{foo,bar,baz}
{\tt\meaningasis\somelist}
\getcommacommandsize[\somelist] \commali
ean things like grid typesetting,
pagecolumns, bidirectional text, etc. I haven't tested lwc with every
possible ConTeXt feature, so there may be some adverse interaction. If
you are using something like this, try disabling it and see if that solves
anything (then let me know so that I can fix it!)
Quick question before I begin: are you using any especially "interesting"
ConTeXt features? By "interesting" I mean things like grid typesetting,
pagecolumns, bidirectional text, etc. I haven't tested lwc with every
possible ConTeXt feature, so there may be some adverse
t.
While I can work around this "feature", the behaviour is different from
earlier versions. Can’t check with MkIV, since that doesn’t work any
more, as reported by Pablo et al.
Hraban
___
If your que
On 4/15/22 20:24, Hans Hagen via ntg-context wrote:
> Hi,
>
> I uploaded a new lmtx. Apart from a experimental intersection feature in
> the mp library (and metafun, more will be revealed when MS an I are okay
> with it) there is not that much news.
Many thanks for the new upl
the "oversized" factor is
nulled by the crop offset.
While I can work around this "feature", the behaviour is different from
earlier versions. Can’t check with MkIV, since that doesn’t work any
more, as reported by P
Hi,
I uploaded a new lmtx. Apart from a experimental intersection feature in
the mp library (and metafun, more will be revealed when MS an I are okay
with it) there is not that much news.
I decided to turn some test code into a mechanism which is illustrated
below. Adaptive boxes are hboxes
texts,
at least in France.
Using the “columns" feature is one way to go
Might be, but I do not always give the same
number of answers on both columns
Something I forgot to put in my MWE is that I
randomize both lists. Messing the answers is a
good way to prevent pupils from cheating,
espec
Thank you for all your answers.
I will have a deeper look at them.
My first comments:
> If you are certain that the there will be no
> multi-line item
Unfortunately there are often some. History
teachers are not known for loving short texts,
at least in France.
> Using the “columns
Dear Damien,
Using the “columns" feature is one way to go if you don’t mind the vertical
alignment mismatch in the third items.
Best regards,
Dalyoung
\starttext
\startitemize [8,columns]%,two]
\startitem Nietzsche \stopitem
\startitem Woody Allen \stopitem
\startitem God \stopitem
\star
> > The second feature would be the addition of an "emoji" range for font
> > fallbacks.
>
> +2
+π
___
If your question is of interest to others as well, please add an entry to the
W
Am 06.04.22 um 17:02 schrieb Pablo Rodriguez via ntg-context:
The first one is to allow that ConTeXt LMTX also downloads the available
modules.
The second feature would be the addition of an "emoji" range for font
fallbacks.
Hi Hans,
I have a couple of suggestions to be added to a not so distant release
The first one is to allow that ConTeXt LMTX also downloads the available
modules.
The second feature would be the addition of an "emoji" range for font
fallbacks.
Many thanks for your he
definefontfeature[ktest][ktest=yes]
\definefontfeature[onum][onum=yes]
\starttext
Default: «Questo è successo nel ’48».
Desired: «Questo è successo nel ’\kern-.1em 48».
Solved: \feature[+][ktest]«Questo è successo nel ’48».
Onum: \feature[+][onum]«Questo è
can define a kern
pair positioning feature than you enable for just that font
Thanks Hans, here's the working MWE:
---
\mainlanguage[it]
% from http://www.pragma-ade.com/context/latest/cont-tst.zip
% file doc/context/tests/mkiv/fonts
On 4/5/2022 1:45 PM, mf via ntg-context wrote:
It's defined in typo-fkr.lua, but I can't understand what parameters to
pass and whether it's the right macro. It looks like it's not.
look at the extension examples in the test suite: you can define a kern
pair positioning feature than you enable
remember
how it is called. Can anybody help here?
Second are there any limits in how large files exproted to XML, XHTML
etc can be. Does the exporter automatically try to split huge documents
into multiple exported documents when some size is exceeded or was or
is such a feature allways
remember
how it is called. Can anybody help here?
Second are there any limits in how large files exproted to XML, XHTML
etc can be. Does the exporter automatically try to split huge documents
into multiple exported documents when some size is exceeded or was or
is such a feature allways
in each case for my particular situation.
The one common factor in all four contributions is the use of setups, so
a light has begun flashing for me: setups are such an important feature
of ConTeXt for solving many problems!
Thanks to all,
Julian
On 7/3/22 18:01, śrīrāma wrote:
On Monday
/reihen/eka/lauf-los-buch/ :
\startsetups eka:normalheader
\setupheadertexts[chapter][{\feature[=normnum]\pagenumber}][{\feature[=normnum]\pagenumber}][]
\stopsetups
\startsetups eka:noheader
\setupheadertexts[][][][]
\stopsetups
\startsetups eka:imagechapter
\setupalign[flushleft]
\doifelse
=deva]
> \definefontfeature[devaB][default]
> [script=deva]
> \definefontfeature[colored][harf]
> [language=dflt,script=arab,
>colr=yes] %doesn't do anything
Wouldn't you also have to enable the colored feature somewhere?
> \starttext
> {\righttoleft\definedfont[file:Ami
On Sat, Jan 22, 2022 at 06:01:42PM +0530, kauśika via ntg-context wrote:
> Recently when we were troubled by incorrect rendering of certain conjuncts in
> malayalam, Hans added a new font-feature. More below*, but first some
> background: from my testing, the main reason for the
ort .. recent indic (font)
> experiences and transliteration tricks will be eplained by kauśika
Recently when we were troubled by incorrect rendering of certain
conjuncts in
malayalam, Hans added a new font-feature. More below*, but first some
background: from my testing, the main reason for the pr
juncts in
malayalam, Hans added a new font-feature. More below*, but first some
background: from my testing, the main reason for the problems with fonts seems
to come from the varied interpretations and/or implementations of OTF
specification. To add to this complexity there are two script tags (
typesetting Hindi works with ConTeXt,
but I don't get the correct output.
Input: आदित्य (See complete attached file)
Output: See attached.
Note that ि "vowel sign I" should be attached to द "letter da" but it is attached to
य "letter ya". Do I need to enable a partic
)
Output: See attached.
Note that ि "vowel sign I" should be attached to द "letter da" but it is
attached to य "letter ya". Do I need to enable a particular feature?
Unfortunately some fonts don't work properly in ConTeXt. Noto Sans Devanagari
is one of them. The
temporarily switch to the devanagari-two feature set as
follows
{\feature[=][devanagari-two] छ्री}
which can be wrapped into a macro.
Otherwise, all the features work well.
Best,
kauśika
___
If your question is of interes
output.
>
> Input: आदित्य (See complete attached file)
>
> Output: See attached.
>
> Note that ि "vowel sign I" should be attached to द "letter da"
> but it is
> attached to य "letter ya". Do I need to enable a particular
> feature?
U
ttached.
>
> Note that ि "vowel sign I" should be attached to द "letter da" but it is
> attached to य "letter ya". Do I need to enable a particular feature?
Unfortunately some fonts don't work properly in ConTeXt. Noto Sans Devanagari
is one of them. The accompa
orrect output.
Input: आदित्य (See complete attached file)
Output: See attached.
Note that ि "vowel sign I" should be attached to द "letter da" but it is
attached to य "letter ya". Do I need to enable a particular feature?
Thanks,
Aditya
test.tex
Description:
the danger of disabling some feature)
Hans
This is still a problem using yesterday's upload.
I'll check it but you anyway need SansBold (B)
Thank you for the fix.
___
If your question is of interest to others as well
size
letters as a work-around, but that means lack of coordination with
custom sizes in \definebodyfontenvironment.
fixed in the next upload (which is a bit experimental in the sense
that some low level consistency renaming happened which always has the
danger of disabling some feature)
Hans
, but that means lack of coordination with
custom sizes in \definebodyfontenvironment.
fixed in the next upload (which is a bit experimental in the sense
that some low level consistency renaming happened which always has the
danger of disabling some feature)
Hans
This is still a problem using
that covers pages across multiple books?
in principle one can load an index but you want some prefixing ... i
suppose that we can make some more native feature (some weekend
challenge i guess)
Hans
> Le 11 janv. 2022 à 17:56, Gavin via ntg-context a écrit :
>
> Thanks Hans! This is great. I made a slight change to add an additional
> feature. By moving the “mysolution” definition out of \startmode[solution], I
> can now use mysolution in either mode. I’d use this if I
Thanks Hans! This is great. I made a slight change to add an additional
feature. By moving the “mysolution” definition out of \startmode[solution], I
can now use mysolution in either mode. I’d use this if I want to give my
solution to one of the problems, as an example, on the handout.
-Gavin
[default][default][compose=yes]
\starttext
ṥ
\stoptext
this feature has been there quite from the start of mkiv because
otherwise mojca couldn't deal with her language
Hans
-
Hans Hagen
with lots of ligatures)
doing a fallback can interfere with these features especially when
they have been put in the private areas which are basically
'undefined'
you're accessing an st ligature directly but normally you will do that
by enabling a font feature
Thank you Hans, for your response
ts of ligatures)
> doing a fallback can interfere with these features especially when
> they have been put in the private areas which are basically
> 'undefined'
>
> you're accessing an st ligature directly but normally you will do that
> by enabling a font feature
Thank you Hans, for
a fi ligature but not as feature so you need to add it:
\startluacode
fonts.handlers.otf.addfeature {
name = "xlig",
type = "ligature",
data = {
[64257] = { "f", "i" },
}
}
\stopluacode
\definefontfea
hen you use a complex font (in this case with lots of ligatures) doing
a fallback can interfere with these features especially when they have
been put in the private areas which are basically 'undefined'
you're accessing an st ligature directly but normally you will do that
by enabling
to font feature so that won't happen .. the
whole idea is to *not* scale the font and delay that
the three scales are realtime scales and absolute values
\starttext
{test {\glyphxscale\numexpr 2*\glyphxscale\relax} test}
\fontspecdef\MyFont \font xscale 500 yscale 2000 % currentfont
On Saturday, January 1, 2022 3:45:36 PM IST Hans Hagen wrote:
> \starteffect is kind of old (comes from mkii), but you could use the
> pseudo font feature effect in mkiv / lmtx which then makes a real font
> instance instead of mixing in some pdf magic
Thanks for the explanations Hans!
uest your kind help in understanding why this is happening
and/or if I am doing something wrong.
\starteffect is kind of old (comes from mkii), but you could use the
pseudo font feature effect in mkiv / lmtx which then makes a real font
instance in
Marco
Thanks a lot. It works. Such a solution had briefly crossed my mind but I
had left it aside, hoping there was some feature I had missed.
Em qua., 29 de dez. de 2021 10:40, Marco Patzer via ntg-context <
ntg-context@ntg.nl> escreveu:
> On Wed, 29 Dec 2021 08:29:34 -0300
> Yo
{
type = "substitution",
data = {
[ "f_i" ] = { "f", "i" }
}
}
},
data = {
rules = {
{
after = { { "o" } },
current = { { "f_i" } },
added a simple levels feature ... the
best i can do for now is:
\placelist[chapter,section,subsection][levels=2]
keep in mind that all should work with the already present selective
placement and filtering (criterium)
uploaded
t your ConTeXt to compile if
> you follow your \autocite command with punctuation or some form of
> whitespace (which is why a double newline works, as you've discovered,
> while a single newline does not).
>
> I'd like to keep the intelligent trailing punctuation adjustment feature
> if p
(which is why a double newline works, as you've discovered, while a single newline does not).
I'd like to keep the intelligent trailing punctuation adjustment feature if possible, but this problem definitely needs to be fixed. If anyone has any suggestions, I welcome
>
> That said, I think you should be able to get your ConTeXt to compile if
> you follow your \autocite command with punctuation or some form of
> whitespace (which is why a double newline works, as you've discovered,
> while a single newline does not).
>
> I'd like to keep the i
ich is why a double newline works, as you've discovered, while a single
newline does not).
I'd like to keep the intelligent trailing punctuation adjustment feature if
possible, but this problem definitely needs to be fixed. If anyone has any
suggestions, I welcome them! My hope is that this can b
\head Head One \par Something bla bla.
>> \starthead Head Two \stophead Other bla bla. % Even worse: No inline any
>> more.
>> \stopitemize
>>
>> However, headstyle= and headcolor= seem to spill all over … Is it a feature
>> or a bug?
>
> No bug, just
One \par Something bla bla.
\starthead Head Two \stophead Other bla bla. % Even worse: No inline any more.
\stopitemize
However, headstyle= and headcolor= seem to spill all over … Is it a feature or
a bug?
No bug, just a user error. When you put the head text in the argument of
\starthead
… Is it a feature or
a bug?
Thanks
Benjamin
___
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http
]
\samplefile{ward}\par
\stop
\stoptext
Thanks Wolfgang.
I tried this:
\definefontfeature [tightlines] [dimensions={*,0,0}]
\starttext
\samplefile{ward}\par
\blank
\start
\setupinterlinespace[line=5pt]
\feature[+][tightlines]
\samplefile{ward}\par
\stop
\stoptext
but it doesn't
.
I tried this:
\definefontfeature [tightlines] [dimensions={*,0,0}]
\starttext
\samplefile{ward}\par
\blank
\start
\setupinterlinespace[line=5pt]
\feature[+][tightlines]
\samplefile{ward}\par
\stop
\stoptext
but it doesn't add the feature to the current font.
I understand I need
On 12/15/2021 9:16 PM, Marco Patzer via ntg-context wrote:
On Wed, 15 Dec 2021 20:48:29 +0100
Hans Hagen wrote:
You can check in the next upload:
- The 'failure' that you saw was actually a real lua error because I
hadn't adapted some fancy, a very old 'around' 2006 feature, seldom
used
up xml and json keys, but i'm not sure if that was fixed of
became bug=feature for practical reasons)
i never came to a 'download option' because it was ot clear where to
download from .. are there zips?
Not sure if it's for every package, but should be just
"http://mirrors.cta
es to
> > > add more modules to the default list, I'll be happy to do that.
> > Just curious ... we have this
> >
> > >mtxrun --script ctan --packages --pattern=tikz
> >
> > which just gives info (at the time i made that the ctan api was bugged
> > as
On Wed, 15 Dec 2021 20:48:29 +0100
Hans Hagen wrote:
> You can check in the next upload:
>
> - The 'failure' that you saw was actually a real lua error because I
> hadn't adapted some fancy, a very old 'around' 2006 feature, seldom
> used as it's more 'an example of poss
s --pattern=tikz
>
> which just gives info (at the time i made that the ctan api was bugged
> as it mixed up xml and json keys, but i'm not sure if that was fixed of
> became bug=feature for practical reasons)
>
> i never came to a 'download option' because it was ot clear where
apted some fancy, a very old 'around' 2006 feature, seldom used
as it's more 'an example of possibilities' code to luametatex yet ...
fwiw, we still share some lua files between engines.
- Afaiks you should now get return code 1 for other cases (say you give
\foo without meaning). It's a
rn=tikz
>
> which just gives info (at the time i made that the ctan api was bugged
> as it mixed up xml and json keys, but i'm not sure if that was fixed of
> became bug=feature for practical reasons)
>
> i never came to a 'download option' because it wa
tan --packages --pattern=tikz
which just gives info (at the time i made that the ctan api was bugged
as it mixed up xml and json keys, but i'm not sure if that was fixed of
became bug=feature for practical reasons)
i never came to a 'download option' because it was ot clear where to
download f
gt;
> The file handle \pgfutil@auxout is used in the macro \pgfutil@writetoaux
> which gets used in the driver files to write absolute positioning stuff to
> file. For example, pgfsys-luatex.def has:
>
> \def\pgfsys@markposition#1{%
> \savepos%
> \edef\pgf@temp{#1}%
> \e
tuc file using two-pass data, but I don't use
this feature of tikz, so don't have examples to test this.
@HenriMenke: Do you know if it is save to not create the `.pgf` file and
rewrite the above macro to read store the \pgfsyspdfmark t
On 12/10/21 6:37 PM, Hans Hagen via ntg-context wrote:
> On 12/10/2021 6:04 PM, Pablo Rodriguez via ntg-context wrote:
>> [...]
>> I’m afraid I’m not getting anything different.
>> [...]
>> I wonder whether there has been an LMTX update or something else that
>> I’m missing (Linux64).
>
>
]
[--permissions="see context --help --expert"]
Many thanks for the new feature, Hans.
I’m afraid I’m not getting anything different.
Here is the source:
\nopdfcompression
\starttext
\null
\stoptext
"context --purgeall --userpassword=foo a" outputs
https://pdf.ousia.t
t --help --expert"]
Many thanks for the new feature, Hans.
I’m afraid I’m not getting anything different.
Here is the source:
\nopdfcompression
\starttext
\null
\stoptext
"context --purgeall --userpassword=foo a" outputs
https://pdf.ousia.tk/enc.pdf.
"context --purgeall
ormance,
> simplifications of the code, and new feature additions are still desirable,
> the module is in working condition and can now be incorporated in a future
> ConTeXt update. The new .lua and .mkvi files for the SBL rendering, updated
> publ-aut.lua and publ-imp-author
> On 10 Dec 2021, at 11:46, Hans Hagen via ntg-context
> wrote:
>
> Hi,
>
> This time the lmtx upload has a (for some maybe) interesting new features:
> runtime pdf encryption.
>
>
> I would be surprised if the native apple viewer works but I can't test that.
Apple Preview works without
o" userpassword="" permissions="print,extract,quality"
Now, this is a feature that relies on the viewer to deal properly with
it as we only support the not depricated method (why bother with the old
stuff).
acrobat : it took some effort (and trial and error) to make
es, uppercase ß (ẞ, U1E9E) would be even better, even according to
the official German orthography rules since 2017, but there are still
not many fonts that have it.
if needed we could catch that with a fallback featu
, simplifications of the code, and new feature additions are
still desirable, the module is in working condition and can now be
incorporated in a future ConTeXt update. The new .lua and .mkvi files for
the SBL rendering, updated publ-aut.lua and publ-imp-author.mkvi files, and
some new code intended
sizes in \definebodyfontenvironment.
fixed in the next upload (which is a bit experimental in the sense that
some low level consistency renaming happened which always has the danger
of disabling some feature)
Hans
...
that would become rather messy and hard to analyze (this is already a
runtime consuming feature) and never be consistent, think of
\underbar{%
\underdot{}
x
\underdot{
g-context
> Gesendet: Sonntag, 28. November 2021 08:42
> An: ntg-context@ntg.nl
> Cc: Maier, Denis Christian (UB)
> Betreff: Re: [NTG-context] Have a cell span multiple columns with tabulate
>
> Thanks, Hraban. That's really helpful. I'll have a look at this feature.
>
> Denis
&g
Thanks, Hraban. That's really helpful. I'll have a look at this feature.
Denis
> -Ursprüngliche Nachricht-
> Von: ntg-context Im Auftrag von Henning
> Hraban Ramm via ntg-context
> Gesendet: Samstag, 27. November 2021 22:23
> An: ntg-context@ntg.nl
> Cc: Henning Hrab
Am 27.11.21 um 21:49 schrieb Denis Maier via ntg-context:
Hans added a short while ago a span feature to tabulate but it works
only for simple tables (e.g. single line cells).
You mean every cell has to be a single line cell? Or the ones where this
span features applies ? That would be enough
Am 27.11.21 um 18:40 schrieb Aditya Mahajan via ntg-context:
On Sat, 27 Nov 2021, Wolfgang Schuster via ntg-context wrote:
The option is no longer part of the default feature set.
Personally, I think that that is a bit extreme. An apostrophe is a really
common construct and I suspect
https://wiki.contextgarden.net/Tables_Overview
currently says: extremetables are said to be better when page breaking is
involved.)
Have you ever noticed problems in that area?
Hans added a short while ago a span feature to tabulate but it works only for
simple tables (e.g. single line cel
ally straight into curly apostrophes ?
> > > >
> > > > \starttext
> > > > John's
> > > > \stoptext
> > >
> > > The option is no longer part of the default feature set.
> >
> > Personally, I think that that is a bit extreme.
version of ConTeXt, I now get a straight apostrophe. Is there a
new option to convert automatically straight into curly apostrophes ?
\starttext
John's
\stoptext
The option is no longer part of the default feature set.
Personally, I think that that is a bit extreme. An apostrophe is a really
eXt, I now get a straight apostrophe. Is there
>> a new option to convert automatically straight into curly apostrophes ?
>>
>> \starttext
>> John's
>> \stoptext
>
> The option is no longer part of the default feature set. To enable the
> feature add &qu
201 - 300 of 4843 matches
Mail list logo
