[NTG-context] Re: A new problem with space in third itemize
Dear Mikael,
Many Thanks, works perfect.
Many Regards
Uschi
Von: Mikael Sundqvist
Gesendet: Donnerstag, 29. Februar 2024 16:45:03
An: mailing list for ConTeXt users
Betreff: [NTG-context] Re: A new problem with space in third itemize
Hi Uschi,
Your coding style is interesting. I do not understand the purpose of
the \it for example. I did put something together that you can try,
but I don't know if this is what you are looking for.
\starttext
\startitemize[n]
\startitem
\m{\forall n \in \naturalnumbers\mtp{:} n^2 > n \implies n > 1},
\stopitem
\startitem
\m{\forall n \in \naturalnumbers\mtp{:} 3\divides n \implies 4 \divides n},
\stopitem
\startitem
\m{\forall n \in \naturalnumbers\mtp{:} n^3 \mtext{ ungerade }
\implies n \mtext{ ungerade}}.
\stopitem
\stopitemize
\stoptext
To quote Pablo, I hope it helps.
/Mikael
On Thu, Feb 29, 2024 at 4:10 PM Ursula Hermann
wrote:
>
> Dear List,
>
>
> This is my little example: the problem is, that everything was fine, in
> itemize 1 and 2. In the third itemize i have a problem, because after n^3
> and after \Rightarrow there should be a spaace , if I want to write :
> \Rightarrow n ungerade, but it says nungerade, what I dont want,.
>
>
> \startitemize[n]
> {\it \item \m{\forall n ∈ \naturalnumbers:n^2 >n\Rightarrow>1,\par}\nospace
> \par \item \m{\forall n ∈ \naturalnumbers:3\mid n\Rightarrow 4 \mid n,\par}
> \nospace
> \par \item \m{\forall n ∈ \naturalnumbers:n^3 ungerade \Rightarrow n
> ungerade \par}
>
> Uschi
>
> ___
> If your question is of interest to others as well, please add an entry to the
> Wiki!
>
> maillist : ntg-context@ntg.nl /
> https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl
> webpage : https://www.pragma-ade.nl / https://context.aanhet.net (mirror)
> archive : https://github.com/contextgarden/context
> wiki : https://wiki.contextgarden.net
> ___
___
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist : ntg-context@ntg.nl /
https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl
webpage : https://www.pragma-ade.nl / https://context.aanhet.net (mirror)
archive : https://github.com/contextgarden/context
wiki : https://wiki.contextgarden.net
___
___
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist : ntg-context@ntg.nl /
https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl
webpage : https://www.pragma-ade.nl / https://context.aanhet.net (mirror)
archive : https://github.com/contextgarden/context
wiki : https://wiki.contextgarden.net
___
[NTG-context] Re: Japanese
On Wed, 28 Feb 2024 at 20:53, Emanuel Han via ntg-context < ntg-context@ntg.nl> wrote: > Thank you all for your suggestions and contributions to the wiki. > > I don't intend to nag, but when looking at what ConTeXt is producing, I > need to state that the result is still far away from a properly typeset > Japanese text. > > So the nihongo script which comes with ConTeXt handles *line breaks / > line wrapping*. But the line break rules defined in it need a rework, > because they don't follow the standards. The standards are documented here: > https://www.w3.org/TR/jlreq/#possibilities_for_linebreaking_between_characters > , and all affected characters are listed here: > https://www.w3.org/TR/jlreq/tables/table_en3.pdf > > We have different rules, depending what kind of character is surpassing > the text width (or is in its last position). > > Rule 1: > > Before closing brackets, closing quotation marks, iteration marks, the > Prolonged sound mark and small Kana, line breaking is prohibited. > > ’”）〕］｝〉》」』】ヽヾゝゞ々ーぁぃぅぇぉァィゥェォっゃゅょッャュョ etc. > > The actual programmed behaviour by the nihongo script is that, if in the > position which exceeds the line width, these characters jump to the next > line and take the previous character with them. If they're in the last > position of the line, they stay where they are. This behaviour is correct. > > Rule 2: > > After opening Brackets and opening quotation marks, line breaking is > prohibited (but not before). > > ‘“（〔［｛〈《「『【 > > The actual programmed behaviour by the nihongo script is that these > characters jump to the next line and take the previous character with them. > This behaviour is wrong. They should jump to the next line without taking > the previous character with them, just like any regular character. The > difference to a regular character is that they jump already when still > within the line length, and they're in the last position of the line. The > correct behaviour can be seen in LibreOffice Writer in action. > > Rule 3: > > Comma (tōten), full width comma, full stop > > 、，。 > > The actual programmed behaviour by the nihongo script is that, if in the > position which exceeds the line width, these characters jump to the next > line and take the previous character with them. This behaviour is wrong. > They have to be put back to the end of the previous line, but beyond the > specified line length. (JIS Z 8125) (Search for "Line adjustment by hanging > punctuation" under https://www.w3.org/TR/jlreq/ ) > If they're in the last position of the line, they stay where they are. The > correct behaviour can be seen in LibreOffice Writer in action. > > Rules 4, 5, ...: > > Combinations of inseparable characters... (see > https://www.w3.org/TR/jlreq/#possibilities_for_linebreaking_between_character > ) and eventually more, which I didn't test. > > It might be useful to define three scripts nihongo_loose, nihongo_strict > and nihongo_very_strict which each implement one of the 3 cases described > here: https://www.w3.org/TR/jlreq/#addendum_a > > According the *line gap* (Otared uses \setupwhitespace[big], which is > exceeding common line gaps), I'd like to quote from > https://www.w3.org/TR/jlreq/ : > > *It is common that the line gap for the kihon-hanmen is set to a value > between half-em spacing and the one em spacing of the character frame used > for the kihon-hanmen. Half-em spacing can be chosen in cases where the line > length is short, but one em spacing or close to it is more appropriate when > the line length is longer than 35 characters.* > > I like the standard line gap which is provided by ConTeXt, which is > equivalent to \setupwhitespace*[0pt]*. Even when using ruby, it works > well. I found the best voffset for ruby to be -1.7ex. > > The *line adjustment* provided by ConTeXt by default is not meeting the > needs for Japanese (and Chinese) text, which follow a grid pattern. > Especially the last line of a paragraph is squeezed, which is "hurting the > eye". > > When characters need to jump to the next line due to previously discussed > line breaking rules, ConTeXt seems to apply "Line adjustment by > inter-character spacing expansion", which is a valid method according to > https://www.w3.org/TR/jlreq/#line_adjustment , although "Line adjustment > by inter-character spacing reduction" is preferred. > > The last point which ConTeXt is missing, when talking about Japanese > typesetting, is vertical writing. > > I know, this is a lot of work. Hopefully we can achieve with joint efforts > to make ConTeXt Japanese ready. > > If I happen to have made false statements, please accept my apology. I > tried to be of help as far as I could. I grew up in Japan and know more or > less how typeset text should look like. > > Emanuel > > It would be nice if you can put your notes above into https://wiki.contextgarden.net/Chinese_Japanese_and_Korean or in general improve/maintain that page (e.g. the links about the fonts are broken at the moment) Perhaps with
[NTG-context] Re: FreeBSD 13.2
Hi Alan, Alan Braslau via ntg-context writes: > On Sun, 25 Feb 2024 14:23:10 +0100 > Henning Hraban Ramm wrote: > >> Am 25.02.24 um 13:12 schrieb Hans Hagen: >> > We could add a flag to the installer that doesn't update the >> > binaries but intead (advices) to build the bins but it assumes >> > Cmake and gcc to be installed (we could cheat and use an existing >> > cmake made make file). >> >> Yes please! A platform-independent download would be great. > > However, we should not assume gcc: it could be clang. FWIW clang is now the default on FreeBSD. Cheers, Roger ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl webpage : https://www.pragma-ade.nl / https://context.aanhet.net (mirror) archive : https://github.com/contextgarden/context wiki : https://wiki.contextgarden.net ___
[NTG-context] Re: FreeBSD 13.2
Hello Hans, Hans Hagen writes: >> Please do not go to this trouble on my account. I have decided to >> give >> up on context. > well, i put the older in in the latest anyway Many thanks, I will give it a try in the next day or so and respond to the list. Best wishes, Roger ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl webpage : https://www.pragma-ade.nl / https://context.aanhet.net (mirror) archive : https://github.com/contextgarden/context wiki : https://wiki.contextgarden.net ___
[NTG-context] Re: A new problem with space in third itemize
Hi Uschi,
Your coding style is interesting. I do not understand the purpose of
the \it for example. I did put something together that you can try,
but I don't know if this is what you are looking for.
\starttext
\startitemize[n]
\startitem
\m{\forall n \in \naturalnumbers\mtp{:} n^2 > n \implies n > 1},
\stopitem
\startitem
\m{\forall n \in \naturalnumbers\mtp{:} 3\divides n \implies 4 \divides n},
\stopitem
\startitem
\m{\forall n \in \naturalnumbers\mtp{:} n^3 \mtext{ ungerade }
\implies n \mtext{ ungerade}}.
\stopitem
\stopitemize
\stoptext
To quote Pablo, I hope it helps.
/Mikael
On Thu, Feb 29, 2024 at 4:10 PM Ursula Hermann
wrote:
>
> Dear List,
>
>
> This is my little example: the problem is, that everything was fine, in
> itemize 1 and 2. In the third itemize i have a problem, because after n^3
> and after \Rightarrow there should be a spaace , if I want to write :
> \Rightarrow n ungerade, but it says nungerade, what I dont want,.
>
>
> \startitemize[n]
> {\it \item \m{\forall n ∈ \naturalnumbers:n^2 >n\Rightarrow>1,\par}\nospace
> \par \item \m{\forall n ∈ \naturalnumbers:3\mid n\Rightarrow 4 \mid n,\par}
> \nospace
> \par \item \m{\forall n ∈ \naturalnumbers:n^3 ungerade \Rightarrow n
> ungerade \par}
>
> Uschi
>
> ___
> If your question is of interest to others as well, please add an entry to the
> Wiki!
>
> maillist : ntg-context@ntg.nl /
> https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl
> webpage : https://www.pragma-ade.nl / https://context.aanhet.net (mirror)
> archive : https://github.com/contextgarden/context
> wiki : https://wiki.contextgarden.net
> ___
___
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist : ntg-context@ntg.nl /
https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl
webpage : https://www.pragma-ade.nl / https://context.aanhet.net (mirror)
archive : https://github.com/contextgarden/context
wiki : https://wiki.contextgarden.net
___
[NTG-context] A new problem with space in third itemize
Dear List,
This is my little example: the problem is, that everything was fine, in itemize
1 and 2. In the third itemize i have a problem, because after n^3 and after
\Rightarrow there should be a spaace , if I want to write : \Rightarrow n
ungerade, but it says nungerade, what I dont want,.
\startitemize[n]
{\it \item \m{\forall n ∈ \naturalnumbers:n^2 >n\Rightarrow>1,\par}\nospace
\par \item \m{\forall n ∈ \naturalnumbers:3\mid n\Rightarrow 4 \mid n,\par}
\nospace
\par \item \m{\forall n ∈ \naturalnumbers:n^3 ungerade \Rightarrow n ungerade
\par}
Uschi
___
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist : ntg-context@ntg.nl /
https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl
webpage : https://www.pragma-ade.nl / https://context.aanhet.net (mirror)
archive : https://github.com/contextgarden/context
wiki : https://wiki.contextgarden.net
___
[NTG-context] Re: Japanese
Hi, In Korea, LaTeX is popular rather than ConTeXt since mathematicians initiated the use of TeX in Korea and they use LaTeX mainly. But right now, there are so many non-math people who developed many things for Korean & LaTeX. Many years ago, Hans and Taco visited the seminar held by KTUG. They discussed with the experts KTUG about to use Korean. From then, there are many progress to use Korean in ConTeXt. Now, I am using ConTeXt to produce textbooks and manuals in Korean with pleasure. Unfortunately, there is a little problem in spacing, for example, “) ,”. It is rare case, so I can correct it manually without problem. In general, ConTeXt typesets Korean nicely. Thanks Hans and ConTeXt team. For Koreans, I use \mainlanguage[kr] \setscript[hangul] The rule of line break are very similar to that of Japanese. I think that “hangul” script handles it and other things. I am just a user of ConTeXt, but if you need any information about Korean to enhance the usage of Korean in ConTeXt, please let me know. Thanks again to Hans, team, and people in this list. Best regards, Dalyoung > 2024. 2. 29. 오전 4:51, Emanuel Han via ntg-context 작성: > > Thank you all for your suggestions and contributions to the wiki. > > I don't intend to nag, but when looking at what ConTeXt is producing, I need > to state that the result is still far away from a properly typeset Japanese > text. > > So the nihongo script which comes with ConTeXt handles line breaks / line > wrapping. But the line break rules defined in it need a rework, because they > don't follow the standards. The standards are documented here: > https://www.w3.org/TR/jlreq/#possibilities_for_linebreaking_between_characters > , and all affected characters are listed here: > https://www.w3.org/TR/jlreq/tables/table_en3.pdf > > We have different rules, depending what kind of character is surpassing the > text width (or is in its last position). > > Rule 1: > > Before closing brackets, closing quotation marks, iteration marks, the > Prolonged sound mark and small Kana, line breaking is prohibited. > > ’”）〕］｝〉》」』】ヽヾゝゞ々ーぁぃぅぇぉァィゥェォっゃゅょッャュョ etc. > > The actual programmed behaviour by the nihongo script is that, if in the > position which exceeds the line width, these characters jump to the next > line and take the previous character with them. If they're in the last > position of the line, they stay where they are. This behaviour is correct. > > Rule 2: > > After opening Brackets and opening quotation marks, line breaking is > prohibited (but not before). > > ‘“（〔［｛〈《「『【 > > The actual programmed behaviour by the nihongo script is that these > characters jump to the next line and take the previous character with them. > This behaviour is wrong. They should jump to the next line without taking the > previous character with them, just like any regular character. The difference > to a regular character is that they jump already when still within the line > length, and they're in the last position of the line. The correct behaviour > can be seen in LibreOffice Writer in action. > > Rule 3: > > Comma (tōten), full width comma, full stop > > 、，。 > > The actual programmed behaviour by the nihongo script is that, if in the > position which exceeds the line width, these characters jump to the next line > and take the previous character with them. This behaviour is wrong. > They have to be put back to the end of the previous line, but beyond the > specified line length. (JIS Z 8125) (Search for "Line adjustment by hanging > punctuation" under https://www.w3.org/TR/jlreq/ ) > If they're in the last position of the line, they stay where they are. The > correct behaviour can be seen in LibreOffice Writer in action. > > Rules 4, 5, ...: > > Combinations of inseparable characters... (see > https://www.w3.org/TR/jlreq/#possibilities_for_linebreaking_between_character > ) and eventually more, which I didn't test. > > It might be useful to define three scripts nihongo_loose, nihongo_strict and > nihongo_very_strict which each implement one of the 3 cases described here: > https://www.w3.org/TR/jlreq/#addendum_a > > According the line gap (Otared uses \setupwhitespace[big], which is exceeding > common line gaps), I'd like to quote from https://www.w3.org/TR/jlreq/ : > > It is common that the line gap for the kihon-hanmen is set to a value between > half-em spacing and the one em spacing of the character frame used for the > kihon-hanmen. Half-em spacing can be chosen in cases where the line length is > short, but one em spacing or close to it is more appropriate when the line > length is longer than 35 characters. > > I like the standard line gap which is provided by ConTeXt, which is > equivalent to \setupwhitespace[0pt]. Even when using ruby, it works well. I > found the best voffset for ruby to be -1.7ex. > > The line adjustment provided by ConTeXt by default is not meeting the needs > for Japanese (and
[NTG-context] Re: Structuring a magazine or booklet
Thank you very much Pablo !
I have to play with this canvas.
Many thanks.
JP
Le 28/02/2024 à 19:10, Pablo Rodriguez via ntg-context a écrit :
On 2/28/24 15:27, Jean-Pierre Delange wrote:
Sorry for the noise : I did'nt see the ConTeXt imposition schemas here :
https://wiki.contextgarden.net/Imposition
I'll read and test it.
Hi Jean-Pierre,
in its simplest form, a booklet may be:
\setuppapersize[A4][A3, landscape]
\setuparranging[2UP]
\starttext
\dorecurse{28}{\section{Section}\input zapf}
\stoptext
I think this seems to be what you may be aiming at.
Just in case it might help,
Pablo
___
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist : ntg-context@ntg.nl /
https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl
webpage : https://www.pragma-ade.nl / https://context.aanhet.net (mirror)
archive : https://github.com/contextgarden/context
wiki : https://wiki.contextgarden.net
___
___
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist : ntg-context@ntg.nl /
https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl
webpage : https://www.pragma-ade.nl / https://context.aanhet.net (mirror)
archive : https://github.com/contextgarden/context
wiki : https://wiki.contextgarden.net
___
[NTG-context] Re: \in, \at, and labletext
Dear List,
So I changed my sentence a little bit, now it works perfect, as I wanted it.
\setupinteraction[state=start]
\starttext
\reference[Rule:1]{Rule (3.1)}
Formulate equivalents according to rule (\goto {3.1} [Rule:1]).
\stoptext
Uschi
Von: Ursula Hermann
Gesendet: Mittwoch, 28. Februar 2024 13:05:25
An: mailing list for ConTeXt users
Betreff: [NTG-context] \in, \at, and labletext
Dear List,
In the Documentation IntroCTX_eng_s.pdf at page 170 , I found the two examples
with \in and \at, and also the lable.
The Problem is, that in the following sentence only the number (3.1) is a
placed formula in an example, should have a link. Without the brackets. The
sentence says:
Task 1: Formulate equivalents according to rule (3.1):
Sorry, I have no example.
Uschi
___
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist : ntg-context@ntg.nl /
https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl
webpage : https://www.pragma-ade.nl / https://context.aanhet.net (mirror)
archive : https://github.com/contextgarden/context
wiki : https://wiki.contextgarden.net
___
