Hi, for my section titles I’m looking for the alignment parameters that give me:
- left aligned
- no hyphenation (or only where I set breakpoints manually)
- no overfull hboxes
At the moment I have
align={flushleft,extremestretch,nothyphenated}
(would use also hz and hanging, if they don’t
On 1/17/20 12:05 PM, MANUEL GONZALEZ SUAREZ wrote:
> Hi:
> When I compile a document with the following preamble:
> [...]
> \usemodule[simplefonts]
Hi Manuel,
as Hraban and Thomas mentioned, the module has been deprecated.
The commands \definefallbackfamily, \definefontfamily and \setupbodyfont
On Fri, Jan 17, 2020 at 03:44:58PM +0100, Henning Hraban Ramm wrote:
> Thank you for the clarification!
You’re welcome :-)
> That means, I can mix e.g. {de,agr,ru} but not {de,en}, right?
Exactly. In the latter case, even with both languages marked up, the
mix of two completely different
> Am 2020-01-17 um 15:36 schrieb Arthur Reutenauer
> :
>
> On Fri, Jan 17, 2020 at 01:51:42PM +0100, Henning Hraban Ramm wrote:
>> Just \mainlanguage[es] and \language[agr] (= \agr) where you need it should
>> be enough.
>
> As Thomas said, that shouldn’t be necessary.
>
>> You can’t expect
On Fri, Jan 17, 2020 at 01:51:42PM +0100, Henning Hraban Ramm wrote:
> Just \mainlanguage[es] and \language[agr] (= \agr) where you need it should
> be enough.
As Thomas said, that shouldn’t be necessary.
> You can’t expect ConTeXt to auto-detect your language, even if that maybe
> would
ht pattern without that
setup.
No, since the patterns for Spanish and Greek are utf8, they can
co-exist, there's no need to mark the Greek passages.
The module simplefonts is obsolete since 2013.
Yes, that's right.
I get both Spanish and Greek hyphenation in a test file:
\mainl
> Am 2020-01-17 um 13:04 schrieb MANUEL GONZALEZ SUAREZ
> :
>
> Thanks very much, but if the module simplefonts is obsolete, What should I
> indicate in the preamble to write with both languages?
Your font setup should be good without trying to load that module (that doesn’t
do anything
> Am 2020-01-17 um 12:05 schrieb MANUEL GONZALEZ SUAREZ
> :
>
> Hi:
> When I compile a document with the following preamble:
>
> \mainlanguage[es]
> %\setuphyphenation[method=traditional]
> \usemodule[simplefonts]
> \setuplanguage[es][patterns={es,agr}]
> \definefallbackfamily [mainface]
=auto]
\definefontfamily [mainface] [serif] [TeX Gyre Schola]
\setupbodyfont[mainface,11pt]
\starttext
...
\stoptext
with Context LuaTeX, hyphenation patterns work for Greek, but not for Spanish.
I do the compilation with Mac. Any ideas to solve it?
Thanks
Manuel González
On 9/3/19 11:17 PM, Julian G wrote:
> Hello everyone,
> I apologize if this has been brought up already (or if my mistake is
> painfully obvious), but I'm having a slight issue with overfull
> hboxes. I think it is connected to hyphenation and/or using different
> fonts.
Hi Juli
On 9/3/2019 11:17 PM, Julian G wrote:
Hello everyone,
I apologize if this has been brought up already (or if my mistake is painfully
obvious), but I'm having a slight issue with overfull hboxes. I think it is
connected to hyphenation and/or using different fonts.
Test file: at the end
Julian G schrieb am 03.09.2019 um 23:17:
Hello everyone,
I apologize if this has been brought up already (or if my mistake is painfully
obvious), but I'm having a slight issue with overfull hboxes. I think it is
connected to hyphenation and/or using different fonts.
Test file: at the end
Hello everyone,
I apologize if this has been brought up already (or if my mistake is painfully
obvious), but I'm having a slight issue with overfull hboxes. I think it is
connected to hyphenation and/or using different fonts.
Test file: at the end of this mail or at
https://gist.github.com
uin in
https://github.com/u-fischer/luaotfload/issues/60 a work-around it
to suppress hyphenation:
\font\keyboard=LibertinusKeyboard-Regular.otf:mode=node;+liga
\hyphenchar\keyboard=-1
\starttext
\keyboard
Tab
Entf
Enter
Capslock
Windows
\stoptext
--
Ulrike Fischer
https://www.troublesho
ements markup.
>
For the document language, Pandoc provides language variables:
https://pandoc.org/MANUAL.html#language-variables
I haven't tried it, so I don't know if it'll handle variations on quotes or
hyphenation, but that strikes me as more a presentation layer aspect than a
content aspec
uage = {english},
hyphenation = {english}, % ignored
pagetotal = {206}, % ignored
pages = {206},
}
\stopbuffer
\usebtxdataset[bib.buffer]
\usebtxdefinitions[apa]
\setupbtx[apa:cite:authoryear][left={[},right={]}]
\startsetups btx:apa:list:book
\btxdoif {author} {
Henning Hraban Ramm schrieb am 01.05.2019 um 16:14:
2. how to switch language for just three words for correct hyphenation?
\starttext
English ... \language[de]{Deutsch}
\stoptext
Shouldn’t that be
\starttext
English ... {\language[de]Deutsch}
\stoptext
?
Yes, the brace should be before
o enable a line break at a hyphen.
>
> \setbreakpoints[compound]
>
> \starttext
> electromagnetic-endioscopy
> \stoptext
>
> 2. Use || to insert a breakable hyphen.
>
> \starttext
> electromagnetic||endioscopy
> \stoptext
>
>> 2. how to switch language for j
On 4/29/19 10:57 AM, Hans Hagen wrote:
> On 4/27/2019 1:51 PM, Pablo Rodriguez wrote:
>> [...]
>> I get the underscore hyphenation with latest ConTeXt beta (LuaTeX-1.10),
>> but not with latest LMTX (LuaTeX-2.0).
>>
>> Am I missing something here?
>
>
phenation[method=traditional]
\sethyphenationfeatures[strict, whatever]
\setuppapersize[A10, lanscape]
\starttext
\startmakeup[standard]
\hsize\zeropoint
\tt definebodyfont
\stopmakeup
\stoptext
I get the underscore hyphenation with latest ConTeXt beta (LuaTeX
setuppapersize[A10, lanscape]
\starttext
\startmakeup[standard]
\hsize\zeropoint
\tt definebodyfont
\stopmakeup
\stoptext
I get the underscore hyphenation with latest ConTeXt beta (LuaTeX-1.10),
but not with latest LMTX (LuaTeX-2.0).
Am I missin
-endioscopy
\stoptext
2. Use || to insert a breakable hyphen.
\starttext
electromagnetic||endioscopy
\stoptext
2. how to switch language for just three words for correct hyphenation?
\starttext
English ... \language[de]{Deutsch}
\stoptext
Wolfgang
1. is there an analog to \hyp{} command from the 'hyphenat' package? Double
words with a dash happen all too often.
2. how to switch language for just three words for correct hyphenation?
3. if the citation in APS format falls out of the right margin, what needs
to be changed to adjust it?
4
On 4/3/19 4:14 PM, Arthur Reutenauer wrote:
> [...]
> βμ βν γμ θμ πμ τν φμ χμ
>
> are the only consonant pairs that require a different treatment. Would
> you please confirm?
Arthur,
the pairs are (to the best of my knowledge):
βμ βν γμ δλ θμ πμ τν φμ χμ
The patterns would be:
Pablo,
On Sun, Mar 31, 2019 at 10:55:18PM +0200, Pablo Rodriguez wrote:
> Since this isn’t about myself or my documents, I guess it is worth to
> provide the optional hyphenation set to all TeX users, not only the ones
> who use ConTeXt.
You’re making it impossible to
t about myself or my documents, I guess it is worth to
provide the optional hyphenation set to all TeX users, not only the ones
who use ConTeXt.
Many thanks again for your help,
Pablo
--
http://www.ousia.tk
___
If your qu
Pablo Rodriguez schrieb am 30.03.19 um 15:40:
On 3/26/19 9:42 AM, Arthur Reutenauer wrote:
On Mon, Mar 25, 2019 at 08:57:40PM +0100, Pablo Rodriguez wrote:
I read your original message when you sent it, but the issue with that
kind of hyphenation exceptions is that they are document-based
On 3/26/19 9:42 AM, Arthur Reutenauer wrote:
> On Mon, Mar 25, 2019 at 08:57:40PM +0100, Pablo Rodriguez wrote:
>> I read your original message when you sent it, but the issue with that
>> kind of hyphenation exceptions is that they are document-based
>
> No. Why wou
On Mon, Mar 25, 2019 at 08:57:40PM +0100, Pablo Rodriguez wrote:
> I read your original message when you sent it, but the issue with that
> kind of hyphenation exceptions is that they are document-based
No. Why would they be restricted to a single document?
> This is wh
using for Esperanto --
slightly non-standard -- a vertical tick mark for the inner-line and the
left but the hyphen for the right). The main benefit, though, is that
you can do the same thing for line-breaking hyphenation if you need to
change that, just drop the `compound` in the keys
is the
> email, with a few updates (the paragraph quoted at the top is by
> myself).
Dear Arthur,
many thanks for your reply.
I read your original message when you sent it, but the issue with that
kind of hyphenation exceptions is that they are document-based (I had
used them before, for Spanish
wrote the whole hyphenation routine in
Lua in 2014, and users can switch to it with
\setuphyphenation[method=traditional]
The idea behind the name is apparently that the Lua code mimics the
“traditional” way implemented in the TeX engine, and Hans envisages that
other methods
Dear list (especially Thomas and Arthur),
I opened a request for optional hyphenation patterns at GitHub
(https://github.com/hyphenation/tex-hyphen/issues/34).
I’m not advocating changing the default, but only providing hyphenation
patterns that allow hyphenating consonant pairs that cannot
On Thu, Feb 28, 2019 at 06:19:24PM +0100, Wolfgang Schuster wrote:
> Paul Hoffman schrieb am 27.02.19 um 23:05:
> >I'm trying to define a new language for use in a bilingual document, but
> >my hyphenation patterns are being ignored and I'm sure I must be doing
> >something
Paul Hoffman schrieb am 27.02.19 um 23:05:
I'm trying to define a new language for use in a bilingual document, but
my hyphenation patterns are being ignored and I'm sure I must be doing
something wrong.
For which Language do you need patterns?
Did you try to contact Arthur or Mojca to add
On Wed, Feb 27, 2019 at 05:05:05PM -0500, Paul Hoffman wrote:
> I'm trying to define a new language for use in a bilingual document, but
> my hyphenation patterns are being ignored and I'm sure I must be doing
> something wrong.
Never mind, I solved the problem. I'll describe what I
I'm trying to define a new language for use in a bilingual document, but
my hyphenation patterns are being ignored and I'm sure I must be doing
something wrong.
I've devised a minimal example that should hyphenate between vowels but
doesn't. Here's the hyphenation patterns file
s no word that begins with γμ.
>
> Am I missing something or should this be improved in the hyphenation
> patterns?
Since we’ve continued that discussion off list, I’d like to mention
our conclusion, which is that the patterns shouldn’t be changed, since
they follow a somewhat differen
Untested:
\setupreferenceformat[style=\nohyphens]
Wolfgang
Hans van der Meer schrieb am 26.10.18 um 13:38:
Using roman numbers in figures I encountered a case where XIII.9 was
hyphenated into XI-II.9. A bit unclear, in my opinion.
Easily repairable with something
like
a problem but maybe something waiting to
be fixed.
\nl \hyphenation{XIII}
-
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69
Using roman numbers in figures I encountered a case where XIII.9 was hyphenated
into XI-II.9. A bit unclear, in my opinion.
Easily repairable with something like
\def\myfigure[#1]{{\nohyphens\in{figure}[#1]}}
Just an observation, not really a problem but maybe something waiting to be
fixed.
List,
Given this example:
\enabletrackers [publications.authorhash]
\startbuffer [bib]
@book{dalambert1743,
title = {Traite de Dynamique},
author = {Jean Le Rond d’Alembert},
publisher = {David l’aîné},
Hi Axel,
how about creating a repository at GitLab with the contents you provide?
This would make contributions easier.
Just in case it helps,
Pablo
PS: ConTeXt can deal with XML directly, so I wonder whether it makes
sense to convert from pandoc to ConTeXt.
PS²: hyphenation is wrong in US
On 10/15/18 10:44 AM, Arthur Reutenauer wrote:
> [...]
> You can see that γμ is not there (nor, of course, γν, which was
> expected). If it was, the pattern 2γ1μ would force the break πράγ-μα,
> hence its absence leads me to believe that the breaks before γμ are
> intentional. I suggest you
Am 2018-10-15 um 10:44 schrieb Arthur Reutenauer
:
> On Sat, Oct 13, 2018 at 11:05:01AM +0200, Thomas A. Schmitz wrote:
>>failed. Arthur is the guru here, so maybe he has a suggestion?
>
> Ah, I was going for a title that inspired more awe, like “Emperor of
> Hyphenation”
On Sat, Oct 13, 2018 at 11:49:31AM +0200, Pablo Rodriguez wrote:
> I have just discovered that LuaLaTeX (from the TeX Live version that
> comes with Fedora 32) does exactly the same with ancient Greek
> (hyphenation is fine in modern polytonic Greek).
All the TeX engines and fo
Arthur is the guru here, so maybe he has a suggestion?
Ah, I was going for a title that inspired more awe, like “Emperor of
Hyphenation”, but guru will do for the time being :-)
The reason you can’t find any obvious culprit is because you need to
look at the patterns that are missing
On 10/13/18 11:49 AM, Pablo Rodriguez wrote:
> On 10/13/18 11:05 AM, Thomas A. Schmitz wrote:
>> On 13.10.2018 10:05, Pablo Rodriguez wrote:
>>> [...]
>>> Γν may be the beginning of word in Greek (such as γνῶσις), but even LSJ
>>> has no word that begins with γμ.
>>
>> You're right, this shouldn't
omes with Fedora 32) does exactly the same with ancient Greek
(hyphenation is fine in modern polytonic Greek).
Just in case it helps,
Pablo
--
http://www.ousia.tk
___
If your question is of interest to others as well, p
this be improved in the hyphenation
patterns?
You're right, this shouldn't happen. I tried in vain to find the culprit
in lang-agr.lua and to see more with
\enabletrackers[hyphenator.visualize,hyphenator.steps,languages.patterns]
but failed. Arthur is the guru here, so maybe he has a suggestion?
Thomas
aren’t hyphenated,
when they may begin a word.
Γν may be the beginning of word in Greek (such as γνῶσις), but even LSJ
has no word that begins with γμ.
Am I missing something or should this be improved in the hyphenation
patterns?
Many thanks for your help,
Pablo
--
http://www.ousia.tk
t a
function of the compounds, but of hyphenation in general.
\setupbackend [export=yes]
\setupdirections [bidi=on]
\starttext
abraca% adjust to cause hyphenation with your textwidth
abra|-|cadabra abra|-|cadabra abra|-|cadabra abra|-|cadabra
abra|-|cadabra abra
l documented options (but not all combinations) for
\setupdirections, and the only one under which there is no problem is
"off". With bidi active, there is a spurious space wherever a
linebreak is introduced. As the example demonstrates, this is not a
function of the compounds,
not all combinations) for \setupdirections, and
the only one under which there is no problem is "off". With bidi active,
there is a spurious space wherever a linebreak is introduced. As the
example demonstrates, this is not a function of the compounds, but of
hyphenation in general.
On 9/13/2018 4:48 PM, Henning Hraban Ramm wrote:
Am 2018-09-13 um 02:04 schrieb Rik Kabel :
On 9/12/2018 18:16, Joseph Canedo wrote:
Seconding the issue. No hyphenation in ragged right text with no change in
setup-- I use:
Thirded.
Just updated ConTeXt (fortunately *after* sending one
Am 2018-09-13 um 02:04 schrieb Rik Kabel :
> On 9/12/2018 18:16, Joseph Canedo wrote:
>
> Seconding the issue. No hyphenation in ragged right text with no change in
> setup-- I use:
Thirded.
Just updated ConTeXt (fortunately *after* sending one project to the printer)
and get no
On 9/12/2018 18:16, Joseph Canedo wrote:
Hello,
Typesetting some documents I notice several overfull boxes and having
a look to output document it looks that somehow no hyphenation at all
is performed (comparing to document produced with previous beta).
I use thiese settings linked
Hello,
Typesetting some documents I notice several overfull boxes and having a look to
output document it looks that somehow no hyphenation at all is performed
(comparing to document produced with previous beta).
I use thiese settings linked to hyphenation
\setupalign[hanging
an through the source code shows existence of
'./texmf-context/tex/context/patterns/mkiv/lang-et.lua' file. It looks like
much of the work, such as hyphenation, has been already done.
MWE 1:
\usemodule[languages-system]
\loadinstalledlanguages
\showinstalledlanguages
MWE 2:
\starttext
\l
ung" is wrong.)
>>
> Yes it is wrong. Correct hyphenation points are
>
> Rind-fleisch-e-ti-ket-tie-rung
Many thanks for your reply, Ulrike.
>> Are the hyphenation patterns wrong in the cases above, or am I missing
>> something?
>
> That's difficult to
but I think that "Rindfleisch-etikettierung"
> is right in German. (And I think that "Rindflei-schetikettierung" is wrong.)
>
Yes it is wrong. Correct hyphenation points are
Rind-fleisch-e-ti-ket-tie-rung
> Are the hyphenation patterns wrong in the cases above,
chetikettierung" is wrong.)
Are the hyphenation patterns wrong in the cases above, or am I missing
something?
Many thanks for your help,
Pablo
--
http://www.ousia.tk
___
If your question is of interest to others
x doesn't look ahead, only back
you probably need to look at the delta of pagegoal - pagetotal and evide
that by the line height .. probably good enough for text without whitespace
even then, hyphenation penalties can make a page one or more lines
shorter so you also need to disable some of that
&g
to look at the delta of pagegoal - pagetotal and evide
that by the line height .. probably good enough for text without whitespace
even then, hyphenation penalties can make a page one or more lines
shorter so you also need to disable some of that
> vspacing > page 4, prevdepth 2.
enough for text without whitespace
even then, hyphenation penalties can make a page one or more lines
shorter so you also need to disable some of that
vspacing > page 4, prevdepth 2.56577pt => 2.56577pt, prevgraf 0 => 4
vspacing > list glue:topskip hlist:line penalty
On 07/10/2018 07:44 PM, Hans Hagen wrote:
> On 7/10/2018 5:20 PM, Pablo Rodriguez wrote:
>> [...]
>> I wonder why English cannot have extra hyphenation patterns, while
>> ancient Greek allows them.
>
> there are no patterns 'en', just 'us' and 'uk'
Many thanks for you
why English cannot have extra hyphenation patterns, while
ancient Greek allows them.
Have I hit a bug or am I missing something?
Sorry for insisting, but I get weird results with column balancing
(registers).
there are no patterns 'en', just 'us' and 'uk'
\enabletrackers[language
Dear list,
sorry for bothering with this again:
\setuplanguage[agr][patterns={agr, en}]
\setuplanguage[en][patterns={en, agr}]
\starttext
\hyphenatedword{judgmental}
\agr\hyphenatedword{judgmental}
\stoptext
I wonder why English cannot have extra hyphenation patterns
languages have the same patterns loaded.
Using \de or \es, hyphenation works fine in both cases:
\setuplanguage[agr][patterns={agr, deo}]
\setuplanguage[deo][patterns={de, agr}]
\mainlanguage[de]
\starttext
\hyphenatedword{Klugheit}
\agr \hyphenatedword{Klugheit
Dear list,
I have the following sample:
% \setuplanguage[agr][patterns={agr, en}]
% \mainlanguage[agr]
\setuplanguage[en][patterns={en, agr}]
\mainlanguage[en]
\starttext
\hyphenatedword{judgmental}
\stoptext
I get hyphenation if I use English as main language
On 02/09/2018 12:03 AM, Hans Hagen wrote:
> On 2/8/2018 8:00 PM, Pablo Rodriguez wrote:
>
>> Have I hit an issue with the new hyphenator, or am I simply missing
>> somehting?
>
> it's a border case that i'll look into
Many thanks for your fast fix in latest beta, Hans.
Pablo
--
On 2/8/2018 8:00 PM, Pablo Rodriguez wrote:
Have I hit an issue with the new hyphenator, or am I simply missing
somehting?
it's a border case that i'll look into
Hans
-
Hans Hagen |
-hyphenated
text are formatted with the monospaced font. The other ones are
formatted with the Roman font.
- The point outside the command is formatted with the monospaced font,
instead of the Roman one.
- It might be possible that hyphenation could behave wrong in this case.
The simplest way to avo
for the rendering and hyphenation of the title. It is
apparently used for that in the bibliography, but it is needed as well
in the text. (And yes, /Formenwandlungen/ does have the same
hyphenation points in both German and English; this was just a
convenient example.)
It also shows
een the times I created
> them, I switched from \hyphenation to \startexceptions.
>
> In general, however, it seems that \startexceptions provides
> fine-grained control by language, whilst \hyphenation appears to be
> broad-stroke across all languages, and so it m
Thank you, Pablo, for the workaround.
As to your question, it originally came about because of the order in
which environment files were included in a document (one general to many
documents, one specific to a new document). Between the times I created
them, I switched from \hyphenation
On 10/22/2017 07:18 PM, Rik Kabel wrote:
> Or am I doing something wrong?
>
> With the following, Schwarzenegger is not hyphenated according to the
> instruction. I get:
Hi Rik,
is there any reason not to include Schwarzenegger in the exceptions?
In any case, either you use \hyphen
Or am I doing something wrong?
With the following, Schwarzenegger is not hyphenated according to the
instruction. I get:
\mainlanguage[en]
\hyphenation{Schwarz-en-egger}
\startexceptions[en]
epi-graphs
Mount-weazels
Mount-weazel
\stopexceptions
\starttext
][tag] does not have an associated language, even though the
bib entry specifies one and the publications manual indicates that this
is intended for the rendering and hyphenation of the title. It is
apparently used for that in the bibliography, but it is needed as well
in the text. (And yes
.
Oh, yes. Thanks for the analysis. I get the startligature-f also on
hyphenation, like in auf-fällig, so that the arc of the first f (that is
supposed to touch the second) reaches over the hyphen.
Greetlings, Hraban
---
http://www.fiee.net
http://wiki.contextgarden.net
G
use it (in production it often
> leads
> to more whitespace than one wants) ... the tex glue model is good
> enough
>
> (the requirement often comes from cases where snapping is the only
> way
> to get spacing right ... similar to the use of ragged right and no
> hy
) ... the tex glue model is good enough
(the requirement often comes from cases where snapping is the only way
to get spacing right ... similar to the use of ragged right and no
hyphenation because the used system can't handle it well ... in the
worst case the limitations of a system
Am 27.09.2017 um 14:09 schrieb Henning Hraban Ramm:
I know I can break ligatures with \/, like Auf\/lage, but is there a general
dictionary approach, like \hyphenation{} ?
https://ctan.org/tex-archive/macros/luatex/latex/selnolig
is a selnolig.lua which could be used for a solution
hange is that adding a
brace group in the middle of a word (like in of{}fice) does not
prevent ligature creation."
With pdftex it does avoid ligatures, but not reliably. There are
cases where the brace group disappear when pdftex tries out
hyphenation points.
in traditional tex hyphenation is
f a word (like in of{}fice) does not
prevent ligature creation."
With pdftex it does avoid ligatures, but not reliably. There are
cases where the brace group disappear when pdftex tries out
hyphenation points.
--
Ulrike Fischer
http://www.troublesh
\hyphenation{} ?
#
#
# Greetlings, Hraban
# ---
# http://www.fiee.net
# http://wiki.contextgarden.net
# GPG Key ID 1C9B22FD
#
#
___
# If your question is of interest to others as well, please add an entry to the
Wiki
On 27 September 2017 at 13:09, Henning Hraban Ramm <te...@fiee.net> wrote:
>
> I know I can break ligatures with \/, like Auf\/lage, but is there a general
> dictionary approach, like \hyphenation{} ?
That's a nice idea. If something like that existed, it could be used
to c
Hi all,
I know I can break ligatures with \/, like Auf\/lage, but is there a general
dictionary approach, like \hyphenation{} ?
Greetlings, Hraban
---
http://www.fiee.net
http://wiki.contextgarden.net
GPG Key ID 1C9B22FD
Dear Pablo, Rik, and Thomas
Thank you so much for your quick help! This gives me much more insight into
the matter. And you provide various solutions with their pros and cons. For
the moment I will stick to Thomas' suggestion \setupbreakpoints[compound]
because I don't want to change the source
On 09/11/2017 10:23 PM, Rik Kabel wrote:
See http://wiki.contextgarden.net/Compound_words.
But this page also contains the solution to the original problem:
\setbreakpoints [compound]
Thomas
___
If your question
On 2017-09-11 14:14, Pablo Rodriguez wrote:
On 09/11/2017 03:10 PM, Christoph Reller wrote:
Hi,
It seems that the hyphenation algorithm for long words with dashes when
typeset in a natural table has changed.
[...]> Could this be a bug or do I have to setup hyphenation differently in
natu
On 09/11/2017 03:10 PM, Christoph Reller wrote:
> Hi,
>
> It seems that the hyphenation algorithm for long words with dashes when
> typeset in a natural table has changed.
> [...]> Could this be a bug or do I have to setup hyphenation differently in
> natural tables? Any fee
Hi,
It seems that the hyphenation algorithm for long words with dashes when
typeset in a natural table has changed.
MWE:
\starttext
\bTABLE[width=5cm]
\bTR
\bTD super-cali-fragi-listic-expi-ali-docious \eTD
\bTD The longest word known to me that ever had an appearance in a musical.
\eTD
\eTR
Hala wrote:
# > Hi all,
# >
# > I came across the problem with typesetting long URLs containing special
# > characters transformed to hexadecimal form. Hyphenation of URLs is needed.
# >
# > Minimal examples (URL taken from our garden and adopted):
# >
# >
On 08/14/2017 06:27 PM, Tomas Hala wrote:
> Hi all,
>
> I came across the problem with typesetting long URLs containing special
> characters transformed to hexadecimal form. Hyphenation of URLs is needed.
>
> Minimal examples (URL taken from our garden and adopted):
>
&
Hi all,
I came across the problem with typesetting long URLs containing special
characters transformed to hexadecimal form. Hyphenation of URLs is needed.
Minimal examples (URL taken from our garden and adopted):
1.
\hyphenatedurl{http://bits.blogs.nytimes.com/2010/03/05/a-former-book
the line with "/,"
Would it be possible that both options were available: packed slashes
and hyphenation after (or before) the slash, both in urls?
Many thanks for your help,
Pablo
--
http://www.ousia.tk
_
kely better solutions for this.
>
> "better" depends on how often such a trick is needed
Many thanks for your help, Hans and Joseph.
I will play with your sample bellow to adapt it to the underscore
hyphenation to the code provided here.
Pablo
> \startluacode
>
>
ext
\startluacode
function sha(s)
local out = {}
for i = 1, s:len() do
out[#out + 1] = s:sub(i, i)
end
context(table.concat(out, '\\discretionary{_}{}{}'))
end
\stopluacode
\starttext
% \hsize\zeropoint
\hyphenation
%%8b2f3c087046c3
acters",
"after","document.addfunnyhyphen")
\stopluacode
\definehyphenationfeatures
[underscore]
[righthyphenchar="FE000]
\setuphyphenation
[method=traditional]
\sethyphenationfeatures
[underscore]
\starttext
301 - 400 of 1768 matches
Mail list logo
