[NTG-context] problem between textrule and setupindenting ?
Hello,
In the following code, the second ruleis indented.
How to remove this indentation ?
%code%
\setuppapersize[A5]
\setupindenting[small,yes]
\setuptextrules[inbetween=\noindentation]
\starttext
\starttextrule{introduction}
Once upon a time \unknown
\stoptextrule
\stoptext
%code%
Many thanks,
Bertrand
___
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://www.pragma-ade.nl / http://tex.aanhet.net
archive : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___
Re: [NTG-context] Standalone
Hi, I'm sending the reply with a tiny bit of delay ... but I would be grateful for some testing of modifications I have done. - It took me a while to actually understand the problem. cygwin support has an interesting history: - at first, no support - then tried to setup the support by native cygwin binaries - the original On Sat, Mar 1, 2014 at 1:42 PM, wrote: On my system I already have Cygwin. I want to install the standalone Context. Which involves basically: mkdir -o /opt/context cd /opt/context wget http://minimals.contextgarden.net/setup/first-setup.sh chmod 744 first-setup.sh ./first-setup.sh #this works up to this point only partially. - /opt/context/tex is not installed. This is a bad error. It causes - first-setup.sh to fail. And what is loaded will cause conflicts with cygwin which already exists, I believe. I can't see why rsync is use to load anothe versio of rsync in a diff location. #1. Why does 1st setup duplicate Cygwin dlls? Because 99% of Windows users don't have rsync installed. And because the version of rsync we are using links against cygwin's dlls. But if you ask why it fetched that under cygwin, the answer is most probably because everyone attempting to install minimals under cygwin gave up or vanished before we were able to fix the issues. I've hurd that having multiple cygwin*.dlls can cause problems. Besideds They already exist and so does luatex.exe for that matter. 'first-setup.sh' should know that it does a test for CYGWIN, but doesn't seem to do anything with it. #2. Also redundant and confusing is first-setup.sh forces the fetching of rsync by an already existing rsync. Is rsync already exists, why fetch another one and put it in a different location. In past we had special cygwin-specific binaries, but those building them gave up. So we switched to fetching the regular windows binaries and forgot about the fact that cygwin users wouldn't want to install rsync cygwin's dlls. I have texlive for unix on a cygwin platform, on top of an XP system. I want to make installing the standalone easy for cyginw and linux. On linux it should be easy already, but if you have some specific suggestion(s), let me know. # # Firstly, exactly what packages are needed for context? # I assume it's one or more of the mtx prefixed programs below. Please advise. - mtx-update.lua - mtxrun.exe - mtxrun.dll - mtxrun.lua - lua52.dll - luatex.dll Is this needed in addition to luatex.exe? Yes, luatex.exe is only 1.5K and depends on it. - luatex.exe Note: cygwin has luatex.exe same functionality? Probably yes (unless you have a different version of luatex yourself). - kpathsea620.dll Note: TeXLive has kpath related code I didn't understand. I understand that there are not a lot of people experimenting with the latest ConTeXt and even less for the Cygin platform. There are a lot of people using the latest ConTeXt (for a certain meaning of a lot: it's definitely less than the number of latex or MS Word users, but still a reasonable number). But the cross section of those and cygwin users might well be asymptotically approaching zero (or one, now that you are attempting it). But, I would like to make it easier and clearer for Cygwin users who do want to experiement with the latest versions. I tried to fix a few problems. Can you please try again. I don't know if installing for a native linux version is easier or more straightforward or not. At least there should not be any problems with fetching rsync and shared libraries on Linux. Feel free to try. Mojca ___ 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://www.pragma-ade.nl / http://tex.aanhet.net archive : http://foundry.supelec.fr/projects/contextrev/ wiki : http://contextgarden.net ___
[NTG-context] Empty heads after leading whitespace
A more explicit minimal example of the problem:
\setupheadertexts[section]
\setuphead[section][%
placehead=empty,
before=,
after=]
\setuphead[subsection][%
placehead=yes,
before={\blank[line]},
after={\blank[line]}]
\starttext
\showframe
\section{My section}
\subsection{My subsection (whitespace before: problem)}
\input knuth
\subsection{My subsection (whitespace before: fine)}
\input knuth
\page
\subsection{My subsection (NO whitespace before: fine)}
\input knuth
\subsection{My subsection (whitespace before: fine)}
\input knuth
\stoptext
___
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://www.pragma-ade.nl / http://tex.aanhet.net
archive : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___
Re: [NTG-context] Empty heads after leading whitespace
Am 03.05.2014 um 16:32 schrieb Maggyero maggy...@gmail.com:
A more explicit minimal example of the problem:
\setupheadertexts[section]
\setuphead[section][%
placehead=empty,
before=,
after=]
\setuphead[subsection][%
placehead=yes,
before={\blank[line]},
after={\blank[line]}]
\starttext
\showframe
\section{My section}
\subsection{My subsection (whitespace before: problem)}
\input knuth
\subsection{My subsection (whitespace before: fine)}
\input knuth
\page
\subsection{My subsection (NO whitespace before: fine)}
\input knuth
\subsection{My subsection (whitespace before: fine)}
\input knuth
\stoptext
When you don’t need a section entry in the TOC you can use “placehead=hidden”,
the title of the section head can be accessed with the \namedstructurevariable
command.
\setupheadertexts[\namedstructurevariable{section}{title}]
\setuphead
[section]
[placehead=hidden]
\setuphead
[subsection]
[placehead=yes,
before={\blank[line]},
after={\blank[line]}]
\showframe
\starttext
\dorecurse{2}
{\page
\section{Section #1}
\dorecurse{2}
{\subsection{Subsection #1.##1}
\input knuth\par}}
\stoptext
Wolfgang
___
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://www.pragma-ade.nl / http://tex.aanhet.net
archive : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___
Re: [NTG-context] Hebrew vowel placement in ConTeXt. (Rik Kabel)
Thank you very much for the reply. I switched to ConTeXt standalone and now it is working. Best, Michael This works: \usemodule[simplefonts] \definefontfeature[hebrew][default][script=hebr,ccmp=yes] \setmainfont[Ezra SIL SR][features=hebrew] \setupdirections[bidi=on] \starttext בְרֵאשִ֖ית בָרָ֣א אֱלֹהִ֑ים אֵ֥ת הַשָמַ֖יִם וְאֵ֥ת הָאָֽרֶץ \stoptext BTW what is the \definefontfamily syntax that would work with \setupbodyfont in the new post-simplefonts era? Best, Michael PS Just FYI here is what I had been working with: What platform are you using, what version of Ezra SIL SR (likely 2.51, but worth asking)? I am using linux (ubuntu 14.04) fonts-sil-ezra package Package fonts-sil-ezra: i 2.51-8 trusty 500 (I presume this means version 2.51.) I am using the current ppa:reviczky/context-daily version of context: ConTeXt ver: 2014.03.25 16:58 MKIV beta fmt: 2014.5.1 int: english/english Here is the error message that I was receiving (when I include script=hebr): + /usr/share/texmf/tex/context/third/simplefonts/t-simplefonts.lua)error: /usr/share/texmf/tex/context/base/font-otn.lua:805: attempt to call upvalue 'getprop' (a nil value) May I bump? The following code used to work, but now it gives an error: \usemodule[simplefonts] \definefontfeature[hebrew][default][mode=node,script=hebr,language=dflt,mark=yes,ccmp=yes] \setmainfont[Ezra SIL SR][features=hebrew] \setupdirections[bidi=on] \starttext ?? ?? ? ?? ?? \stoptext The following variant (without script=hebr) compiles but the vowels are misplaced (not centered below the letters), which ccmp=yes (see http://www.microsoft.com/typography/otspec/features_ae.htm#ccmp) is supposed to request: \usemodule[simplefonts] \definefontfeature[hebrew][default][mode=node,language=dflt,mark=yes,ccmp=yes] \setmainfont[Ezra SIL SR][features=hebrew] \setupdirections[bidi=on] \starttext ?? ?? ? ?? ?? \stoptext The problem in definefontfeature seems to be that the feature ccmp=yes is not taking effect, and the feature script=hebr generates an error. Thank you very much for your advice. Michael Michael, Sorry to say, no problem here with your example, and trimming the second line even further to \definefontfeature[hebrew][default][script=hebr,ccmp=yes] still produces results with no errors and proper nikkud alignment (run on a system running Windows 8.1 x64 and ConTeXt standalone 2014-04-28 standard and jit). Similarly, no problem with traditional font definition without simplefonts. ___ 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://www.pragma-ade.nl / http://tex.aanhet.net archive : http://foundry.supelec.fr/projects/contextrev/ wiki : http://contextgarden.net ___
[NTG-context] Empty heads after leading whitespace
Thanks Wolfgang. I could even have sections in the TOC with
'\setuptexttexts[{\placerawheaddata[section]}]'.
However, how can I start a new page at each new section? The 'page=yes'
pair does no longer work with your solution 'placehead=hidden' (since the
head is not placed I guess). I also tried 'before=\page' or 'after=\page'
without more success. Here is a minimal example showing the absence of page
breaks though I specified 'page=yes' (the section numbers are also
mismatched but if one puts manual page breaks they match again, so it's not
really a problem for me):
\setupheadertexts[\namedstructurevariable{section}{title}][]
\setuphead
[section]
[placehead=hidden,
page=yes] % -- This key does NOT work.
\setuphead
[subsection]
[placehead=yes,
before={\blank[line]},
after={\blank[line]}]
\setuptexttexts[{\placerawheaddata[section]}]
\showframe
\starttext
\completecontent
\dorecurse{2}
{\section{My section}
\dorecurse{2}
{\subsection{My subsection}
\input knuth}}
\stoptext
___
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://www.pragma-ade.nl / http://tex.aanhet.net
archive : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___
Re: [NTG-context] Hebrew vowel placement in ConTeXt. (Rik Kabel)
On 2014-05-03 17:16, Michael Ash wrote:
Thank you very much for the reply.
I switched to ConTeXt standalone and now it is working.
Best,
Michael
This works:
\usemodule[simplefonts]
\definefontfeature[hebrew][default][script=hebr,ccmp=yes]
\setmainfont[Ezra SIL SR][features=hebrew]
\setupdirections[bidi=on]
\starttext
?? ?? ? ?? ??
\stoptext
BTW what is the \definefontfamily syntax that would work with
\setupbodyfont in the new post-simplefonts era?
Best,
Michael
As to the by-the-way, see message 56606
http://www.mail-archive.com/ntg-context%40ntg.nl/msg56606.html in the
list archive. This is not the post-simplefonts solution, but the
pre-simplefonts solution. It does allow much better control over all of
the fonts that make up the typeface (using ConTeXt terminology).
The example shows what to do to set a document that is primarily Hebrew
(or other RtL script). If you want to mix directions, bidi may be a
better choice than the setupalign of the example. If you use bidi, I
suggest \setupdirections[bidi=on,method=two]. I find that without method
two, there is a problem with punctuation. In particular, the comma in
some text {\heb **}, some more text
gets set before, not after, the hebrew text.
If you set only some Hebrew/Aramaic/Arabic, and especially if you do not
need font variants (bold, italic, ...) you might prefer to define a
single font. I have used:
\definefontfeature [aramaic]
[default]
[ccmp=yes,
script=hebr]
\definefont[aramaic]%% KeterYG from
http://culmus.sourceforge.net/taamim/
[KeterYG-Medium.ttf*aramaic sa 1]
\setupdirections [bidi=on=,method=two]
\starttext
English {\aramaic ???} English again.
\stoptext
I do note as well that there is a problem in the example in the linked
message. It looks to me like the order of components is beth/shva/dagesh
(for the first letter (and beth/qamatz/dagesh for the first of the
second word), which ConTeXt sets incorrectly. When the order is changed
to beth/dagesh/qamatz-or-shva, they are set correctly. If you use vim,
the command ga will show the decomposition of the character components.
Here are the two versions of that letter, first in the order that sets
correctly:
???
and then in the order that does not:
???
--
rik
___
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://www.pragma-ade.nl / http://tex.aanhet.net
archive : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___
