der-/overfull hboxes
hyphenation.applied.visualize – show hyphenation
https://wiki.contextgarden.net/Trackers/typesetters.suspects
https://wiki.contextgarden.net/Trackers/visualizers.justification
Directives:
pdfview.method=auto (in contextcnf.lua) to change --autopdf default
logs.errors=* – make warnings errors
\stop
Is there a reason why do the alignment change within a local group?
The problem is that is messing with footnotes, causing things like URLS
to run off the page. How can I permit the hyphenation to appear
normally, but only on the footnote text?
\setupalign[verytolerant,nothyphe
hings like URLS to run
off the page. How can I permit the hyphenation to appear normally, but only on
the footnote text?
--Joel
___
If your question is of interest to others as well, please add an entry to the
.
\stoptext
As included in the text, I don’t have the slighliest idea whether the
transliterated text may be Sanskrit.
> What we need are thus three elements: switching the language to
> Sanskrit temporarily (the main language will be english),
\sa is the language switch (which also enab
;>> \setupmarginframed
> >>>> [inmargin]
> >>>> [align={inner,nothyphenated}]
> >>> Does the align parameter of \setupmargindata has any function, then?
> >>> Also, using setupmarginframed leads to other problems:
> >>>
[inmargin]
[location=outer,
style=italic]
\setupmarginframed
[inmargin]
[align={inner,nothyphenated}]
Thanks, that works for the alignment. It does not change the hyphenation.
I would have expected this line breaks in the margin note:
significant
incredible
components
Instead, ConTeXt
>
> The location of the margin block and the style are still controlled by
> \setupmargindata and only the alignment has to be changed with
> \setupmarginframed.
>
> \setupmargindata
>[inmargin]
>[location=outer,
> style=italic]
>
> \setupmargin
9807106 131074 39846
581634219 30 5 12 35183
250250 50 10
system >
------
250250 50 10
system >
-----------
system >
system >
pt pattern --convert --path=./source --destination=./patterns
> >
> > with the file hyph-pt.tex v. 1.4 proposed by Leo Araujo and Aline Benevides,
> > (see:
> > https://github.com/hyphenation/tex-hyphen/pull/62/commits/79f4327c7c94c435cfcb73ea61c001a525fc818e)
>
On 7/16/2024 1:00 AM, Marcus Vinicius Mesquita wrote:
Dear List
When using:
mtxrun --script pattern --convert --path=./source --destination=./patterns
with the file hyph-pt.tex v. 1.4 proposed by Leo Araujo and Aline Benevides,
(see:
https://github.com/hyphenation/tex-hyphen/pull/62/commits
Dear List
When using:
mtxrun --script pattern --convert --path=./source --destination=./patterns
with the file hyph-pt.tex v. 1.4 proposed by Leo Araujo and Aline Benevides,
(see:
https://github.com/hyphenation/tex-hyphen/pull/62/commits/79f4327c7c94c435cfcb73ea61c001a525fc818e)
I got the
Funny idea of replacing hyphenation with LLM-generated alternative
wording, also explains a bit how TeX works:
http://tom7.org/bovex/
(a SIGBOVIK submission)
;) hr
___
If your question is of interest to others as
, ...)
%% \language sets language to use for hyphenation, quote rules, ...
\mainlanguage includes all settings of \language.
As you can see in the following example \mainlanguage change the float
label and the quotation marks but \language changes only the quotation
marks and uses the label of the
Rik Kabel schrieb am 30.05.2024 um 19:21:
From my basic environment file, a useful reminder:
%% \mainlanguage sets language used for labels (TOC, chapters, ...)
%% \language sets language to use for hyphenation, quote rules, ...
\mainlanguage includes all settings of \language.
As
From my basic environment file, a useful reminder:
%% \mainlanguage sets language used for labels (TOC, chapters, ...)
%% \language sets language to use for hyphenation, quote rules, ...
--
Rik
On 2024-05-30 11:34, Peter Münster wrote:
Hi,
When using \start/stopquotation in French
iwan, Hong Kong) are basically
different between the dialects of Chinese. There is no hyphenation difference
in any dialect.
I looked at the rules for linebreaking in chinese a while ago and even
though there are a few guidelines there is no fixed list this. Many
programs let you change th
Hong Kong),
and the expressions used (Chinese mainland, Taiwan, Hong Kong) are basically
different between the dialects of Chinese. There is no hyphenation difference
in any dialect.
As far as I am currently using, the context is not very well set for
localization, and there are many words in la
a new language.
If anyone can give advice, appreciate it
1. It is better to add new languages to Context itself and not just in
your document.
2. Chinese doesn't use hyphenation pattern but has rules where to break
which is enabled with the \setscript command.
3. We should use agree
Joel via ntg-context schrieb am 20.05.2024 um 03:30:
I'm using mostly default ConTeXt settings, but an editor has warned I
should avoid using hyphenation at the end of lines--at least for my
particular audience.
I've found manual text that says how to disable specific words f
ttings, but an editor has warned I should
> avoid using hyphenation at the end of lines--at least for my particular
> audience.
>
> I've found manual text that says how to disable specific words from being
> hyphenated.
>
> Is there a whole-docu
I'm using mostly default ConTeXt settings, but an editor has warned I should
avoid using hyphenation at the end of lines--at least for my particular
audience.
I've found manual text that says how to disable specific words from being
hyphenated.
Is there a whole-document switch to
phens are also configured
as valid hyphenation chars.
Hans
-
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | ww
details about
hyphenation.
\startexceptions[de]
He{k-}{k}{ck}en-e{k-}{k}{ck}en-ze{k-}{k}{ck}en
\stopexceptions
% \registerhyphenationpattern[de][c1k/k=k]
%
% \setuphyphenation[method=traditional]
\mainlanguage[de]
\starttext
Heckeneckenzecken = \hyphenatedword{Heckeneckenzecken}
\stoptext
][
hyphenmin=4,
lefthyphenmin=2,
righthyphenmin=2,
]
\starttext
\hyphenatedfile{aesop-de}
\startcolumns
Funktioniert die Trennung? Heckeneckenzecken
\samplefile{aesop-de}
\stopcolumns
\stoptext
Just as a start, the languages manual provides more details about
hyphenation.
\startexceptions[de
Hi, the sample file aesop-de is in old German orthography, there, ck
should get hyphenated as k-k, this doesn’t work (e.g. Mücke isn’t
hyphenated at all). Is there something I can configure?
Hraban
\mainlanguage[deo]
\setuplanguage[deo][
hyphenmin=4,
lefthyphenmin=2,
righthyphenmin=2,
]
add “force=yes” to your definition of the fallback family:
\definefallbackfamily
[mainface]
[rm]
[Theano Didot]
[preset=range:greek,force=yes]
Your text cannot have two main languages, so
\mainlanguage[fr]
If you want hyphenation for your Greek passages, you can add
\setuplan
will
have to add “force=yes” to your definition of the fallback family:
\definefallbackfamily
[mainface]
[rm]
[Theano Didot]
[preset=range:greek,force=yes]
Your text cannot have two main languages, so
\mainlanguage[fr]
If you want hyphenation for your Greek passages, you can
e terminal!
> Here is how much of TeX's memory you used:
> 16 strings out of 474221
> 403 string characters out of 5750189
> 1922978 words of memory out of 500
> 22371 multiletter control sequences out of 15000+60
> 558069 words of font info for 36 fonts, out of
nd of file on the terminal!
Here is how much of TeX's memory you used:
16 strings out of 474221
403 string characters out of 5750189
1922978 words of memory out of 500
22371 multiletter control sequences out of 15000+60
558069 words of font info for 36 fonts, out of 800 for 9000
1141
eve]/ indicating to the reader how the
>> abbreviation was interpreted.
>> The problem then arises with hyphenation, because /voors[chreeve]/ in the
>> example will not be hyphenated as if the []'s were absent. Which is what I
>> would like to happen.
>&
abbreviation was interpreted.
The problem then arises with hyphenation, because /voors[chreeve]/ in
the example will not be hyphenated as if the []'s were absent. Which is
what I would like to happen.
Question: is it possible to realize this and how?
Like this?
\starttext
\startexceptions
In the 18th century documents I am transcribing often words are abbreviated as
for example voorschreeve becoming voors: In the transcription it is usual to
write this as voors[chreeve] indicating to the reader how the abbreviation was
interpreted.
The problem then arises with hyphenation
Here’s a preliminary schema of LMTX. What do you think?
Is there something important missing?
Maybe add mtxrun, hyphenation patterns, modules. Move the images to the
resources?
Maybe I should replace the “files” within MkXL with the parts like
parser, par builder and whatever?
I don’t want to
bleprime} ist gleichbedeutend mit \m{∃y : ∀x : f(x) = y} \par
> (Beutelspacher [\hyphenatedurl {10},S.54]).
>
> \stoptext
\hyphenatedurl only changes the hyphenation of its content, it doesn’t create a
link. In your example it makes no sense.
Generally, you need an anchor (link target) t
unabhängig von der Wahl\par von
\m{x\doubleprime} ist gleichbedeutend mit \m{∃y : ∀x : f(x) = y} \par
(Beutelspacher [\hyphenatedurl {10},S.54]).
\stoptext
\hyphenatedurl only changes the hyphenation of its content, it doesn’t
create a link. In your example it makes no sense.
Generally, you
On 12/29/2023 9:09 PM, Arthur Rosendahl wrote:
Hi Muhammad,
On Sat, Dec 30, 2023 at 01:08:24AM +0700, Muhammad Rizqi Siregar wrote:
I'd like to ask if ConTeXt LMTX has hyphenation for Indonesian language or
a way to enable it. I think Babel package in LaTeX has some pattern file
Hi Muhammad,
On Sat, Dec 30, 2023 at 01:08:24AM +0700, Muhammad Rizqi Siregar wrote:
> I'd like to ask if ConTeXt LMTX has hyphenation for Indonesian language or
> a way to enable it. I think Babel package in LaTeX has some pattern files
> for the language, although I am no
Hello,
I'd like to ask if ConTeXt LMTX has hyphenation for Indonesian language or
a way to enable it. I think Babel package in LaTeX has some pattern files
for the language, although I am not sure whether they can be borrowed to
work with ConTeXt or not.
Appreciate any help on this. T
On Thu, 16 Nov 2023 21:40:08 +0100
vm via ntg-context wrote:
> Is there a command in context to force every word in a text to
> hyphenate? e.g to typeset a text with "ge-dach-ten-streep-jes"
Like this?
\starttext
\hyphenatedword{\samplefile{knuth}}
\stoptext
Marco
___
Is there a command in context to force every word in a text to
hyphenate? e.g to typeset a text with "ge-dach-ten-streep-jes"
Thanks
.Floris
___
If your question is of interest to others as well, please add an entry t
On 8/22/2023 9:59 AM, Henning Hraban Ramm wrote:
Am 20.08.23 um 08:32 schrieb Wolfgang Schuster:
In the next release you don't need the method=font anymore because the
missing hyphenation
is the result of a old patch which was needed in 2013. Back than there
was no problem
with hyphen
Am 20.08.23 um 08:32 schrieb Wolfgang Schuster:
In the next release you don't need the method=font anymore because the
missing hyphenation
is the result of a old patch which was needed in 2013. Back than there
was no problem
with hyphenation and the patch but since than Hans added a fe
Thomas A. Schmitz schrieb am 19.08.2023 um 18:10:
On 8/19/23 17:51, Wolfgang Schuster wrote:
You can use the font method to have hyphenated words back.
The culprit which prevents hyphenation are the penalty settings
which are added by ConTeXt when the default method is used.
\mainlanguage [de
On 8/19/23 17:51, Wolfgang Schuster wrote:
You can use the font method to have hyphenated words back.
The culprit which prevents hyphenation are the penalty settings
which are added by ConTeXt when the default method is used.
\mainlanguage [de]
\setuppapersize [A6]
\setupquotation[method
have hyphenated words back.
The culprit which prevents hyphenation are the penalty settings
which are added by ConTeXt when the default method is used.
\mainlanguage [de]
\setuppapersize [A6]
\setupquotation[method=text]
\starttext
„Originalgenie“ „Originalgenie“ „Originalgenie“
\quot
Hi,
is this a limitation or a bug? Text inside \quotation{} is not
hyphenated. It appears to be like this for a couple of versions, but I'm
not sure if it has always been the case. Silly example to test:
\mainlanguage [de]
\setuppapersize [A6]
\setupbodyfont [14pt]
\starttext
„Originalgen
On 8/9/2023 12:10 PM, denis.ma...@unibe.ch wrote:
Keith, you can also check hyphenations using a script:
-- check-hyphens.lua
--[[
analyze hyphenations based on a ConTeXt log file
enable hyphenation tracking in the ConTeXt file with
\enabletrackers[hyphenation.applied]
then
Keith, you can also check hyphenations using a script:
-- check-hyphens.lua
--[[
analyze hyphenations based on a ConTeXt log file
enable hyphenation tracking in the ConTeXt file with
\enabletrackers[hyphenation.applied]
then run this script with
lua check-hyphens.lua
right.
> You can try this:
>
> \starttext
>
> \protected\def\ProofOfConcept#1#2%
>{{#1\llap{\effect[hidden]{#2
>
> test test \ProofOfConcept{föö}{foo} test
>
> \stoptext
>
> but forget about hyphenation (actualtext probably also doesn't
about hyphenation (actualtext probably also doesn't always
work well across lines in viewers).
Hans
-
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Nether
e offical tag but for historic reasone we use ua as language; given
>> the uk's exit and ua's entry in the european union we could now consider
>> adapting it; and i'd wonder is anyone would notice - or bother - is we'd use
>> ukrain hyphenation for russ
mf-context/tex/context/patterns/mkiv/lang-uk.lua
>
> uk is the offical tag but for historic reasone we use ua as language; given
> the uk's exit and ua's entry in the european union we could now consider
> adapting it; and i'd wonder is anyone would notice - or both
t the end of lines
similar the way underfull and overfull boxes can be displayed with a
coloured bar at the end of the offending line?
I have looked at the wiki page "Reviewing hyphenation" and it has a
solution for mkii from 2009 which, I would think, won't be suitable
for pr
On 8/1/2023 4:54 PM, Keith McKay wrote:
Hi colleagues,
Is there a tracker for highlighting hyphens at the end of lines similar
the way underfull and overfull boxes can be displayed with a coloured
bar at the end of the offending line?
I have looked at the wiki page "Reviewing hyphen
Hi colleagues,
Is there a tracker for highlighting hyphens at the end of lines similar
the way underfull and overfull boxes can be displayed with a coloured
bar at the end of the offending line?
I have looked at the wiki page "Reviewing hyphenation" and it has a
solution for mkii
Hraban's suggestion works really well. I setup hyphenation rules for the
underfull boxes of Russian names and reduced the \tolerance to 600. I'm
now down to about 20 underfull boxes which to my eyes look fine.
Thanks again Hraban
Best Wishes
Keith
On 28/07/2023 19:20, Keith M
his Honor"
> > in the first png and "Well, you see," in the second png. I not sure a
> > reader would spot the second png badness but the first is noticeable to
> > my eyes.
>
> Hi Keith,
> since both cases are caused by names with accents, did you try t
es with accents, did you try to add
hyphenation exceptions for those? Such cases are probably not covered by
English hyphentation rules.
Hraban
___
If your question is of interest to others as well, please add a
the european union we could now
consider adapting it; and i'd wonder is anyone would notice - or bother
- is we'd use ukrain hyphenation for russian, which could save some
bytes in
> On 19 Jul 2023, at 08:52, Hans Hagen wrote:
>
> so best not mess with setting up languages that already have been set up.
I had no idea I was messing. What am I doing wrong, then. Because in my actual
document with ua language setting it is not hyphenated. This was just a minimal
example
On 7/19/2023 12:36 AM, Gerben Wierda wrote:
This file:
\setupinteraction
[state=start,
color=blue,
style=bold]
\definefallbackfamily
[archimate]
[ss]
[Helvetica]
[preset=range:cyrillic,
tf=style:light,
it=style:lightoblique,
bf=style:regular,
bi=style:obli
This file:
\setupinteraction
[state=start,
color=blue,
style=bold]
\definefallbackfamily
[archimate]
[ss]
[Helvetica]
[preset=range:cyrillic,
tf=style:light,
it=style:lightoblique,
bf=style:regular,
bi=style:oblique,
force=yes,
rscale=1.0]
\definefontfamily [arch
>
> (3) The biggest new feature (already known to some of you as we chat
> about it) is that in addition to the (upto three) passes that create a
> paragraph we can now have extra ones. This is discussed in
> lowlevel-lines.pdf (preliminary). The second pass is the most important
> on
second pass is the most important
one (it uses hyphenation but not yet emergency stretch) and, based on
criteria that can be set, between the second and third pass multiple
attempts can be triggered.
So, for instance one can start careful (pass one), less careful (pass
two), test all kind of
, showing the difference:
and
It looks like every paragraph has been run through par.
This does not seem to create paragraphs with more lines, but they
create a very odd, choppy page. It does not prevent hyphenation, and
sometimes introduces it where none was present before.
Did I miss a change
paragraph has been run through par.
This does not seem to create paragraphs with more lines, but they create
a very odd, choppy page. It does not prevent hyphenation, and sometimes
introduces it where none was present before.
Did I miss a change?
I'll check it (we're experimenting
paragraph has been run through par.
This does not seem to create paragraphs with more lines, but they create
a very odd, choppy page. It does not prevent hyphenation, and sometimes
introduces it where none was present before.
Did I miss a change?
I found the same problem with a \definedescription
create paragraphs with more lines, but they create
a very odd, choppy page. It does not prevent hyphenation, and sometimes
introduces it where none was present before.
Did I miss a change?
--
Rik
___
If your question
On 2/15/2023 6:13 PM, Pablo Rodriguez via ntg-context wrote:
Hi Hans,
with the sample hyphenator from
https://www.pragma-ade.com/general/manuals/languages-mkiv.pdf#page=23,
next letters after hyphenation are missing.
I already reported this
(https://mailman.ntg.nl/pipermail/ntg-context/2023
Hi Hans,
with the sample hyphenator from
https://www.pragma-ade.com/general/manuals/languages-mkiv.pdf#page=23,
next letters after hyphenation are missing.
I already reported this
(https://mailman.ntg.nl/pipermail/ntg-context/2023/107743.html).
Am I missing something or have I hit a bug?
Many
19:06), I get:
cing
anack
I’m missing m and b in the hyphenated words.
I’m afraid that the hyphenator is all Greek to me.
Is there any reason why letters are lost in hyphenation?
I’m afraid (I think) I might have hit a bug
breaks are removing characters.
In the sample below, output from
\hsize\zeropoint
\sha{a1b2c3d4}
reads:
a
_
_
_
_
3d4
I’m afraid \righthyphenmin=-1 prevents hyphenation (it seems to do it
everywhere).
This
\unexpanded\def\sha#1%
{\begingroup
mple below, output from
\hsize\zeropoint
\sha{a1b2c3d4}
reads:
a
_
_
_
_
3d4
I’m afraid \righthyphenmin=-1 prevents hyphenation (it seems to do it
everywhere).
Sorry, but I don’t get what is wrong here.
Many thanks for your help,
Pablo
\startluacode
function document.addf
ed to have mentioned them (afaIk), there are two issues:
1. Hyphenation patterns are different for ancient, monotonic and modern
polytonic Greek. Greek ortography was polytonic before 1982.
ConTeXt includes patterns for ancient and monotonic Greek, but none for
modern polytonic Greek
(http://mirror.ctan.or
n case it might help, I’ve rewritten the Greek entry in the wiki:
https://wiki.contextgarden.net/Greek
Although nobody seemed to have mentioned them (afaIk), there are two issues:
1. Hyphenation patterns are different for ancient, monotonic and modern
polytonic Greek. Greek ortography was polytonic
Dear list,
just in case it might help, I’ve rewritten the Greek entry in the wiki:
https://wiki.contextgarden.net/Greek
Although nobody seemed to have mentioned them (afaIk), there are two issues:
1. Hyphenation patterns are different for ancient, monotonic and modern
polytonic Greek. Greek
(|–|) allows hyphenation after the
% endash. Omitting it and using a bare endash inhibits hyphenation
% ‘twixt the endash and the paren.
% By default, add parens around the dates. If none are needed due to
% the context, use \BDNP.
%
\newif\ifBDParen
\starttexdefinition
% dates are printed only once per person.
% \removeunwantedspaces allows this to directly follow, or follow
% after whitespace, the associated name: Name\BD{1}{2} or
% Name \BD{1}{2}.
% Using the compound indication (|–|) allows hyphenation after the
% endash. Omitting it and using a
to add hyphenation
exceptions for all languages.
I wonder whether Steffen would be fine with this addition.
Many thanks for your help,
Pablo
___
If your question is of interest to others as well, please add an entry
> bookmarks > confusing level change at level 3 around 'Conclusiones'
backend > bookmarks > confusing level change at level 2 around 'Apéndices'
backend > bookmarks > confusing level change at level 3 around 'Notas'
mkiv lua stats &
On 12/8/22 13:14, Hans Hagen via ntg-context wrote:
> [...]
> \setuplanguage
> [explicitrighthyphenchar=-1]
Sorry for insisting, Hans, but many languages (excepting en and uk) seem
nor to recogize this option:
\startluacode
function document.addfunnyhyphen(tfmdata)
local underscore =
es]
\starttext
\startTEXpage[offset=1em, width=4em]
\hsize\zeropoint\tt
\hyphenatedword{legibility-legible}
\stopTEXpage
\stoptext
Results are the same with "\mainlanguage[es]" or "\mainlanguage[nl]".
If "\mainlanguage" is placed after "\setuplanguage"
On 12/8/2022 12:33 PM, Pablo Rodriguez via ntg-context wrote:
Dear list,
I have the following sample:
\startluacode
function document.addfunnyhyphen(tfmdata)
local underscore = utf.byte("_")
local char = tfmdata.characters[underscore]
if not char then return end
Dear list,
I have the following sample:
\startluacode
function document.addfunnyhyphen(tfmdata)
local underscore = utf.byte("_")
local char = tfmdata.characters[underscore]
if not char then return end
tfmdata.characters[0xFE000] = {
width= 0,
> -Ursprüngliche Nachricht-
> Von: ntg-context Im Auftrag von Pablo
> Rodriguez via ntg-context
> Gesendet: Mittwoch, 19. Oktober 2022 20:02
> An: Leah Neukirchen via ntg-context
> Cc: Pablo Rodriguez
> Betreff: Re: [NTG-context] Suboptimal German hyphenation
>
On 10/24/22 17:09, Hans Hagen via ntg-context wrote:
>> [...]
>> Hans, is there any news regarding Pablos wish?
> no, because I'm in a different tex mode ...
Steffen,
meanwhile, a way of crappy cheating...
\setuphyphenation[method=traditional]
\doloopoverlist{en,nl,de,es,it,fr,da,fi}
{\r
On 10/24/2022 3:08 PM, Steffen Wolfrum wrote:
Anfang der weitergeleiteten Nachricht:
*Von: *Pablo Rodriguez via ntg-context <mailto:ntg-context@ntg.nl>>
*Betreff: **Aw: [NTG-context] Hyphenation in multi-language projects*
*Datum: *14. September 2022 um 19:40:53 MESZ
*An: *Denis
> Anfang der weitergeleiteten Nachricht:
>
> Von: Pablo Rodriguez via ntg-context <mailto:ntg-context@ntg.nl>>
> Betreff: Aw: [NTG-context] Hyphenation in multi-language projects
> Datum: 14. September 2022 um 19:40:53 MESZ
> An: Denis Maier via ntg-context
On 10/19/22 16:47, Leah Neukirchen via ntg-context wrote:
>> [...]
>> Many prefixes have two letters, so changing the default may be
>> reasonable. But there are more experienced German typographers on
>> this list who can chime in.
>
> After some research, I found the recommendation in
> Forssman
Leah Neukirchen via ntg-context writes:
> Max Chernoff via ntg-context writes:
>
>> Hi Leah,
>>
>>> I was typesetting some German text on a narrow page when I discovered
>>> the justification wasn't as good as expected. I think I tracked this
>
very long line followed by an ugly linebreak, not
\quotation{supercalifragilisticexpialidocious}
\stoptext
The macro-quoted text is not protruded. I fixed this locally with a
macro
\def\q#1{\protrusionboundary1\quotation{#1}}
Should this be default?
But the missing hyphenation I have to add myself
inebreak, very
>> supercalifragilisticexpialidocious.
>> This is a very long line followed by an ugly linebreak, not
>> \quotation{supercalifragilisticexpialidocious}
>> \stoptext
>> The macro-quoted text is not protruded. I fixed this locally with a
>> macro
>>
}
\stoptext
The macro-quoted text is not protruded. I fixed this locally with a macro
\def\q#1{\protrusionboundary1\quotation{#1}}
Should this be default?
But the missing hyphenation I have to add myself with \-. Ideas?
Try
\setupdelimitedtext[quotation][method=font]
Hraban
locally with a macro
\def\q#1{\protrusionboundary1\quotation{#1}}
Should this be default?
But the missing hyphenation I have to add myself with \-. Ideas?
--
Leah Neukirchenhttps://leahneukirchen.org/
___
If your
On Thu, Sep 29, 2022 at 06:49:23AM +0200, Henning Hraban Ramm via ntg-context
wrote:
> Thank you, Leah, Max and Wolfgang! I changed that immediately in all of my
> ongoing projects, but I don’t think we should change the default after all
> these years.
Are you sure that the default in ConTeXt
Am 29.09.22 um 08:27 schrieb Arthur Rosendahl:
On Thu, Sep 29, 2022 at 06:49:23AM +0200, Henning Hraban Ramm via ntg-context
wrote:
Thank you, Leah, Max and Wolfgang! I changed that immediately in all of my
ongoing projects, but I don’t think we should change the default after all
these years.
Am 29.09.22 um 06:10 schrieb Wolfgang Schuster via ntg-context:
Max Chernoff via ntg-context schrieb am 29.09.2022 um 02:17:
Babel/ngerman sets left/righthyphenmin to 2/2, but ConTeXt sets those to
3/3 for German. (The English default is 2/3). I don't speak German so I
have no idea which is corr
Max Chernoff via ntg-context schrieb am 29.09.2022 um 02:17:
Hi Leah,
I was typesetting some German text on a narrow page when I discovered
the justification wasn't as good as expected. I think I tracked this
down to differences in hyphenation points, namely, ConTeXt has fewer:
\star
Max Chernoff via ntg-context writes:
> Hi Leah,
>
>> I was typesetting some German text on a narrow page when I discovered
>> the justification wasn't as good as expected. I think I tracked this
>> down to differences in hyphenation points, namely, ConTeXt
1 - 100 of 1001 matches
Mail list logo
