On Fri, 20 Feb 2009, Alan Bowen wrote:
Aditya—
luatools --expand-var TEXMF gets
{/Applications/ConTeXtMinimals/tex/texmf-project,/Applications/ConTeXtMinimals/tex/texmf-fonts,/Applications/ConTeXtMinimals/tex/texmf-local,/Applications/ConTeXtMinimals/tex/texmf-osx-intel,/Applications/ConTeXtMi
I'm interested to know whether nested sections are supported in the new
structure code (strc-*)?
Using the following to test, I don't get a section and subsection, but
rather two sections. The log file notes a "missing \stopsection".
\starttext
\startsection{Section}
\input tufte
\startsection{
Aditya—
luatools --expand-var TEXMF gets
{/Applications/ConTeXtMinimals/tex/texmf-project,/Applications/
ConTeXtMinimals/tex/texmf-fonts,/Applications/ConTeXtMinimals/tex/
texmf-local,/Applications/ConTeXtMinimals/tex/texmf-osx-intel,/
Applications/ConTeXtMinimals/tex/texmf-context,/Applicati
On Fri, 20 Feb 2009, Alan Bowen wrote:
I have been revising my notes for newbie Mac installation of the ConTeXt
Minimals and was about to put them online when I discovered that, when I try
to process a file using MKIV, it does not find my personal texmf folder
(~Library/texmf). There is no pro
On Fri, Feb 20, 2009 at 11:07:08PM +0100, Hans Hagen wrote:
> Khaled Hosny wrote:
>
>> I think we can make default features per script (HarfBuzz seems to do
>> that).
>>
>>> if it was trivial i'd already done it -)
>>
>> I know :) just my two cents.
>
> how about making a wiki page where we collect
On Fri, 20 Feb 2009 11:39:23 -0700, Khaled Hosny
wrote:
Microsoft's OpenType features list page
(http://www.microsoft.com/typography/otspec/features_ae.htm) gives a "UI
suggestion" for each feature noting if it should be on by default,
Hmm, I think this page is more relevant for what you ha
I have been revising my notes for newbie Mac installation of the
ConTeXt Minimals and was about to put them online when I discovered
that, when I try to process a file using MKIV, it does not find my
personal texmf folder (~Library/texmf). There is no problem when I
process the same file us
On Fri, 20 Feb 2009 15:10:52 -0700, Hans Hagen wrote:
Idris Samawi Hamid ادريس سماوي حامد wrote:
Khaled: Have you considered making an inventory of available Arabic
fonts? Or does one already exist? We could put together a table of
what's available, checking for available OT features, etc.
Idris Samawi Hamid ادريس سماوي حامد wrote:
Khaled: Have you considered making an inventory of available Arabic
fonts? Or does one already exist? We could put together a table of
what's available, checking for available OT features, etc.
also, it would be nice to have some quality otf arabic f
Khaled Hosny wrote:
On Fri, Feb 20, 2009 at 07:58:11PM +0100, Hans Hagen wrote:
Khaled Hosny wrote:
I think some font features should be on by default, so that
\definefontfeature[script=arabic] should be enough to get an Arabic font
btw, this is why we already have arabic as featureset define
Khaled Hosny wrote:
I think we can make default features per script (HarfBuzz seems to do
that).
if it was trivial i'd already done it -)
I know :) just my two cents.
how about making a wiki page where we collect fontnames + assumed
default features (+ test if possible); the problem is t
On Fri, 20 Feb 2009 14:02:58 -0700, Khaled Hosny
wrote:
Microsoft's OpenType features list page
(http://www.microsoft.com/typography/otspec/features_ae.htm) gives a
"UI
suggestion" for each feature noting if it should be on by default, I
think those are what most OpenType enable by defaul
On Fri, Feb 20, 2009 at 12:31:49PM -0700, Idris Samawi Hamid ادريس سماوي حامد
wrote:
> On Fri, 20 Feb 2009 11:57:22 -0700, Hans Hagen wrote:
>
>> Khaled Hosny wrote:
>>
>>> Currently, when defining a font feature one has to enable all features
>>> by hand which is IMHO not very user friendly as i
On Fri, Feb 20, 2009 at 07:58:11PM +0100, Hans Hagen wrote:
> Khaled Hosny wrote:
>
>> I think some font features should be on by default, so that
>> \definefontfeature[script=arabic] should be enough to get an Arabic font
>
> btw, this is why we already have arabic as featureset defined
I wasn't
On Fri, Feb 20, 2009 at 07:57:22PM +0100, Hans Hagen wrote:
> Khaled Hosny wrote:
>
>> Currently, when defining a font feature one has to enable all features
>> by hand which is IMHO not very user friendly as it implies prior
>> knowledge about OpenType font features and the meaning of each one, no
On Fri, 20 Feb 2009 11:57:22 -0700, Hans Hagen wrote:
Khaled Hosny wrote:
Currently, when defining a font feature one has to enable all features
by hand which is IMHO not very user friendly as it implies prior
knowledge about OpenType font features and the meaning of each one, not
every Arabi
Khaled Hosny wrote:
I think some font features should be on by default, so that
\definefontfeature[script=arabic] should be enough to get an Arabic font
btw, this is why we already have arabic as featureset defined
-
Khaled Hosny wrote:
Currently, when defining a font feature one has to enable all features
by hand which is IMHO not very user friendly as it implies prior
knowledge about OpenType font features and the meaning of each one, not
every Arabic user, for example, knows what does 'init', 'medi, etc.
Currently, when defining a font feature one has to enable all features
by hand which is IMHO not very user friendly as it implies prior
knowledge about OpenType font features and the meaning of each one, not
every Arabic user, for example, knows what does 'init', 'medi, etc.
ligatures mean yet to k
On Fri, Feb 20, 2009 at 4:09 PM, Thomas A. Schmitz
wrote:
>
> On Feb 19, 2009, at 3:10 PM, luigi scarso wrote:
>
>> see
>> http://codespeak.net/lxml/tutorial.html#namespaces
>
> Luigi,
>
> thanks so much for your patient replies. I have now begun to play with
> python's lxml. It offers a lot, mayb
On Feb 19, 2009, at 3:10 PM, luigi scarso wrote:
see
http://codespeak.net/lxml/tutorial.html#namespaces
Luigi,
thanks so much for your patient replies. I have now begun to play with
python's lxml. It offers a lot, maybe too much for a beginner. One
advantage for my immediate needs that I
On Thu, Feb 19, 2009 at 10:36 PM, Hans Hagen wrote:
> Alan Stone wrote:
>
>> Hi,
>>
>> BF = body font
>> HF = head font
>>
>> A = arial
>> T = times new roman
>> V = verdana
>>
>> OT = 12 = 12pt
>> OF = 14 = 14pt
>>
>> See comments in fontswitch.tex
>>
>> In attachment...
>>
>> - fontswitch.tex:
Assuming the lack of responses means that there isn't a way to do that
using texexec, you could always use a script to do that.
#!/bin/sh
PAPER=test
texexec $PAPER".tex"
mv $PAPER".pdf" ./newdir
mv $PAPER.*./newdir2
mv ./newdir2/$PAPER".tex" .
Then just execute the script instead
Vyatcheslav Yatskovsky wrote:
Hi all,
I just downloaded and setup latest context beta on my new machine.I made
a simple script file for my teaching schedule in UTF-8 encoding and
with %engine=luatex prefix. But.. the default font is LMRoman12, and it
has no Cyrrilic letters.
I need simple do
Hi all,
please have a look to the following small table with its own footnotes:
\setupoutput[pdftex]
\starttext
\startlocalfootnotes[n=0,conversion=characters]
\placetable[here][]{}
\placelegend
{
\tfx
\setupTABLE [frame=off]
\bTABLE
\bTR\bTD 1990 \eTD\bTD 1991 \eTD\eTR
\bTR\bTD 2.\footnote[f
Hi Albrecht,
have you tried my proposal from 13.2.08?
(http://archive.contextgarden.net/message/20090213.144419.432c095e.en.html)
Maybe there is a better solution (?) but with my context installation and
mkII it just works fine this way.
Greetings
Thomas
\setupoutput[pdftex]
\starttext
\st
Le 19 fév 2009 à 07:21, Aditya Mahajan a écrit:
Hi,
> I have fixed the makefile, t-setup.tex, ma-cb-styles and ma-cb-setups.tex
> so that the english documentation compiles.
>
> You can try the current svn version.
Works perfectly.
Thanks!
--
Sébastien
http://edilibre.net
__
Maurício wrote:
Hi,
This is probably a really basic question
already asked many times, but I wasn't able
to find an answer.
How to type an unicode character using its
number? Searching for messages, I found
things like:
\char"2019
that one is pretty safe in mkiv
make sure to end witha spac
Thanks Hans.
This works, except...
\usetypescriptfile[tps_timesnewroman]
\usetypescript[timesnewroman]
\usetypescriptfile[tps_verdana]
\usetypescript[verdana]
\def\myBodyFontSize{14pt}
\def\myHeadFontSize{14pt}
\setupbodyfont[verdana,\myBodyFontSize]
\setuphead[chapter][style={\switchtobodyfon
there is no such sharing built in (for context mkiv i will probably
provide a merge registers features)
\def\VegetableAndOrange#1%
{\Vegetable{#1}\Orange{#1}#1}
Thanks for your quick answer and we're looking forward to the merge
register features
groet,
Femke
You may try \uchar{"20}{"19}.
On Thu, Feb 19, 2009 at 09:48:50PM -0300, Maur憝cio wrote:
> Hi,
>
> This is probably a really basic question
> already asked many times, but I wasn't able
> to find an answer.
>
> How to type an unicode character using its
> number? Searching for messages, I found
>
31 matches
Mail list logo
