Re: [NTG-context] No menu bar option for Adobe Reader
I have just tested the latest beta (2019-04-29). The new option works as expected in both Acrobat Reader 11 and DC. Thanks again. Paul ___ 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://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : http://contextgarden.net ___
Re: [NTG-context] No menu bar option for Adobe Reader
@luigi: Version 11. I know, it isn't supported anymore since October 2017. ___ 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://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : http://contextgarden.net ___
Re: [NTG-context] No menu bar option for Adobe Reader
@Hans: Thanks a lot, I'm looking forward to testing it. @Alan: Like Hans said. It's a new option, and I have it activated in my local environment file. It's the only and clumsy way to control the interface setting since Adobe Reader cannot save the state of the menu bar permanently (which is complete nonsense). I use Acrord because I'm used to it and because I think it still has the best subpixel rendering, at least in the Linux world (with Wine). Mozilla's PDF.js comes close though. Paul ___ 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://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : http://contextgarden.net ___
[NTG-context] No menu bar option for Adobe Reader
Hi,
I use the "Hide menu bar" option extensively in Adobe Acrobat Reader to get a
cleaner interface. To this end, I usually hack lpdf-mis.lua after a ConTeXt
upgrade to create a \setupinteractionscreen[option=nomenubar] switch.
I wonder if it would be possible to add this little feature to the source code.
Perhaps it can be useful to others as well.
Greetings!
Paul
Attachment: patch + modified lpdf-mis.lua (from ConTeXt MkVI 2019.04.25)if not modules then modules = { } end modules ['lpdf-mis'] = {
version = 1.001,
comment = "companion to lpdf-ini.mkiv",
author= "Hans Hagen, PRAGMA-ADE, Hasselt NL",
copyright = "PRAGMA ADE / ConTeXt Development Team",
license = "see context related readme files"
}
-- Although we moved most pdf handling to the lua end, we didn't change
-- the overall approach. For instance we share all resources i.e. we
-- don't make subsets for each xform or page. The current approach is
-- quite efficient. A big difference between MkII and MkIV is that we
-- now use forward references. In this respect the MkII code shows that
-- it evolved over a long period, when backends didn't provide forward
-- referencing and references had to be tracked in multiple passes. Of
-- course there are a couple of more changes.
local next, tostring, type = next, tostring, type
local format, gsub, formatters = string.format, string.gsub, string.formatters
local flattened = table.flattened
local backends, lpdf, nodes = backends, lpdf, nodes
local nodeinjections = backends.pdf.nodeinjections
local codeinjections = backends.pdf.codeinjections
local registrations= backends.pdf.registrations
local nuts = nodes.nuts
local copy_node= nuts.copy
local nodepool = nuts.pool
local pageliteral = nodepool.pageliteral
local register = nodepool.register
local pdfdictionary= lpdf.dictionary
local pdfarray = lpdf.array
local pdfconstant = lpdf.constant
local pdfreference = lpdf.reference
local pdfunicode = lpdf.unicode
local pdfverbose = lpdf.verbose
local pdfstring= lpdf.string
local pdfflushobject = lpdf.flushobject
local pdfflushstreamobject = lpdf.flushstreamobject
local pdfaction= lpdf.action
local pdfminorversion = lpdf.minorversion
local formattedtimestamp = lpdf.pdftimestamp
local adddocumentextgstate = lpdf.adddocumentextgstate
local addtocatalog = lpdf.addtocatalog
local addtoinfo= lpdf.addtoinfo
local addtopageattributes = lpdf.addtopageattributes
local addtonames = lpdf.addtonames
local pdfgetmetadata = lpdf.getmetadata
local texset = tex.set
local variables= interfaces.variables
local v_stop = variables.stop
local v_none = variables.none
local v_max= variables.max
local v_bookmark = variables.bookmark
local v_fit= variables.fit
local v_doublesided= variables.doublesided
local v_singlesided= variables.singlesided
local v_default= variables.default
local v_auto = variables.auto
local v_fixed = variables.fixed
local v_landscape = variables.landscape
local v_portrait = variables.portrait
local v_page = variables.page
local v_paper = variables.paper
local v_attachment = variables.attachment
local v_layer = variables.layer
local v_lefttoright= variables.lefttoright
local v_righttoleft= variables.righttoleft
local v_title = variables.title
local v_nomenubar = variables.nomenubar
local positive = register(pageliteral("/GSpositive gs"))
local negative = register(pageliteral("/GSnegative gs"))
local overprint= register(pageliteral("/GSoverprint gs"))
local knockout = register(pageliteral("/GSknockout gs"))
local omitextraboxes = false
directives.register("backend.omitextraboxes", function(v) omitextraboxes = v end)
local function initializenegative()
local a = pdfarray { 0, 1 }
local g = pdfconstant("ExtGState")
local d = pdfdictionary {
FunctionType = 4,
Range= a,
Domain = a,
}
local negative = pdfdictionary { Type = g, TR = pdfreference(pdfflushstreamobject("{ 1 exch sub }",d)) } -- can be shared
local positive = pdfdictionary { Type = g, TR = pdfconstant("Identity") }
adddocumentextgstate("GSnegative", pdfreference(pdfflushobject(negative)))
adddocumentextgstate("GSpositive", pdfreference(pdfflushobject(positive)))
initializenegative = nil
end
local function initializeoverprint()
local g = pdfconstant("ExtGState")
local knockout = pdfdictionary { Type = g, OP = false, OPM = 0 }
local overprint = pdfdictionary { Type = g, OP = true, OPM = 1 }
Re: [NTG-context] Imposition: 4 on 1, last 2 pages upside down
Thanks, but don't bother if I'm the only one using this formatting. I've lowercased the switch name in the wiki section. ___ 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://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : http://contextgarden.net ___
[NTG-context] Imposition: 4 on 1, last 2 pages upside down
Hi, I ended up creating a new imposition schema. I've added a little wiki section on the matter: https://wiki.contextgarden.net/Imposition Greetings! Paul ___ 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://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : http://contextgarden.net ___
[NTG-context] Imposition: 4 on 1, last 2 pages upside down
Hello, I'm trying to get four small A6 pages on one A4 page (portrait) like this: 4 1 3 2 The last two pages should be upside down. This is my starting point: \setuppapersize[A6][A4] \setuparranging[1*4] Aside from the different page sequence, this rotates the last two pages, which is not what I'm looking for. Can anyone help me with this? Sorry if this has been covered before. I'm not very familiar with imposition. Greetings! Paul ___ 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://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : http://contextgarden.net ___
[NTG-context] New logo proposal
Hello again, as many critics go towards "I don't see any coherence" or "to me it's just a random bunch of colored letters" or "it's hard to read the word CONTEXT", some afterthoughts in that regard (difficulty, randomness). Personally, I like visual material that catches my attention, but does not give all away at first glance. For example a good poster or book cover. It invites me to spend time on it. And I don't have the feeling that the designer thinks I'm stupid. ConTeXt is quite sophisticated, its logo can also be a little bit more complicated than your average sportswear brand. Any color choice is arbitrary to some extend. The colors I've used cover the entire hue range and are at equal distance apart (common in multicolored designs). This denotes to me not only the flexibility, and the fun of using it, but also the comprehensiveness of ConTeXt. Not only can you use ConTeXt in very different situations, you can use it in every situation (that requires typesetting). My 2c! Greetings, Paul ___ 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://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : http://contextgarden.net ___
[NTG-context] New logo proposal
Hello, thank you all again for your reactions. A lot of interesting comments here on logo design in general and a ConTeXt logo in particular. I'm honored that the new design has found its way into the Wiki, thanks Taco! @Lukas: I like the idea. Would be worth a try. @Floris vM: I'm glad that my nemesis on the matter felt himself challenged to make his own proposal. While I think it's too minimalistic (only insiders know what 'CTX' stands for), I like your idea of the subscript 'T'. Your concept with the crosses reminded me of the visual identity of Amsterdam. I do not see, however, how it reflects better "typesetting beautiful readable typography". And it lacks some colors ,-) Greetings! Paul ___ 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://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : http://contextgarden.net ___
[NTG-context] New logo proposal
Hello, thanks for your feedback. Again, I don't want to impose or dismiss anything. I wanted to share this because I believed somebody else in the ConTeXt community could be interested. @Taco: Actually, I stumbled upon the nice ConTeXt group logo recently and was wondering who made it. To answer your questions: I tried to avoid any logic or rainbow-type color sequence to create something more unique. The first square had to be in blue and the middle area in a warm color. (I played around a lot with the color combinations.) Regarding the outside circle: I tried different variations, with and without a surrounding circle or round background, with and without rounded squares, and was most pleased with this solution. It's true, "clean and simple" can easily lead to "too informal". @Clyde J: Valid point. I use the logotype with the subscript 'E' whenever I can in inline text. @Floris vM: Font, spacing, overall appealingness. No Helvetica/Nimbus Sans, which has less meaning to me for ConTeXt than a DIN-ish/technical one. Colors are fun. If you don't see it this way, it's perfectly fine. @Alan B: I've uploaded MetaPost files of the main version. Yes, the horizontal version is not very exciting nor very TeX-aware. I made this one primarily because I wanted something small for a little GUI script. Now I think it's just superfluous. Greetings! Paul ___ 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://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : http://contextgarden.net ___
[NTG-context] New logo proposal
Dear ConTeXt users and developers, I want to submit a new ConTeXt logo to you (link to GitLab project): https://gitlab.com/schickele/new-context-logo I made this logo in February 2018. At the time, I was planning to do some video tutorials on ConTeXt (still work in progress), and I wanted a nice looking visual clue for the thumbnails. Recently, I made a few minor tweaks and thought it would be the right time to put it out there. The logo comes in two different layouts (hexagonal and horizontal), and each layout comes in two color variations (multicolored and blue). The hexagonal layout is borrowed from the unofficial ConTeXt logo that has been around for some time. I like the idea of a clean geometrical form, and the hexagon reminds me of chemistry formulas -- one of the many application fields of ConTeXt. The seven colors have mainly an esthetic purpose. They also denote the flexibility of ConTeXt. I've added a monochromatic blue version because shiny, saturated colors are not suitable for every case, and blue is strongly associated with ConTeXt to me. Blue is also a reminder of Mark IV and LuaTeX. The letters are set in Din17 EF, which I've licensed. I like its simple shapes combined with a round and soft touch. It avoids consciously the very connoted Computer Modern and can be seen as a modernized and also Europeanized interpretation of the TeX tradition. This logo is just a humble proposal. Perhaps it is of some use to someone. It could also make someone else want to create and share his or her logo -- that would be great. I'm using ConTeXt since 2006/07 for almost everything that contains text: letters, presentations, invitations, résumés, certificates, manuals, reports, flyers, university papers, book typesetting, exercise sheets, song sheets, and I'm still amazed by how powerful, flexible and reliable it is. Thanks to the whole community -- and particularly to the Dutch wizard -- for making this possible! Greetings from Leimen, Germany Paul Schalck ___ 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://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : http://contextgarden.net ___
Re: [NTG-context] Palatino Linotype under MKIV
Thank you very much, Taco, especially for the detailed explanations you
gave! It works like a charm. I've made a new Wiki page (my first one),
mainly based on your answer:
http://wiki.contextgarden.net/Palatino_Linotype_under_MKIV
- Original Message -
From: Taco Hoekwater t...@elvenkind.com
To: mailing list for ConTeXt users ntg-context@ntg.nl
Cc: Paul Schalck schick...@web.de
Sent: Wednesday, June 30, 2010 9:33 AM
Subject: Re: [NTG-context] Palatino Linotype under MKIV
Hi,
On 06/29/2010 11:15 AM, Paul Schalck wrote:
Hi,
I'm trying to use the full glyph range of the Palatino Linotype font
shipped with XP (version 1.40; significantly different from the Windows
7 one) under MKIV. Everything works fine (oldstyle figures, sups for
instance), except that the small cap i character has a dot whereas it
shouldn't.
I borrowed one of the fonts from my wife's XP install (pala.ttf).
The short answer: the font is borked, complain to Microsoft.
The long answer: lookups are name-based, and if there are two glyphs
with the same name, you can't know which one is used in any particular
piece of software.
As far as I can see, it has to do with the messy name list of the
glyphs. Both the normal small cap i and the small cap dotted i are named
i.sc
The one with a dot is meant for Turkish.
Moreover, the small cap glyphs have no unicode numbers in this font, so
I cannot pick them manually with \char or even with \charX.
Any ideas how I can get the right dottless i?
Context always maps all unencoded glyphs into a private area starting
at 0xF. For this font, the first i.sc (the one without dot) is at
0xF00AF and has glyph index 0x456, and the second is at 0xF00EB
with glyph index 0x492.
To find these numbers, run a file like this:
\usemodule[fnt-10]
\starttext
\ShowCompleteFont{file:pala.ttf}{20pt}{1}
\stoptext
This means that to get the dotless version, you could enter \charF00AF
Really long answer: to fix the problem nicely, we have to rename one of
the two glyphs.
This could be done in an external editor, but as this is a system font,
that may not be wise or even possible. Luckily, context allows to do
this using a patching system that is active during initial font loading
time (when the cache is generated).
In the following, we will be patching the generated cache file before
it is saved (by putting some lua code at the beginning of your test
file). Remember that you have to delete the generated cache
files after each iteration. In my case, they were /opt/tex/texmf-
cache/luatex-cache/context/c24894930eb65eadf7b71f1e305ff518/fonts/otf/pala.tm*.
If you forget to do this step in between runs,
nothing will change in the output!
The existing font patches are in font-pat.lua, and from that file it is
possible to deduce that something like this is the correct program
structure, theoretically:
\startluacode
function palapatch (data,filename)
-- to be filled in
end
fonts.otf.enhancers.patches[^pala] = palapatch
\stopluacode
The two arguments to the patch function are the data table from the
luafontloader and the font file name, respectively. The function
should patch the data table to our liking and does not have to return
anything.
In order to have a good look at the data, the first thing to do is to
dump the data to a file. Put this code at the top of your test file,
delete the data cache files, and run:
\startluacode
function palapatch (data,filename)
io.savedata(filename .. '.lua', table.serialize(data))
end
fonts.otf.enhancers.patches[^pala] = palapatch
\stopluacode
\definefontfeature [...]
Afterwards, open pala.ttf.lua (or pala.TTF.lua. not sure how this works
out on an actual XP install) in an editor for browsing.
Looking at the lua code in pala.ttf.lua, you will see that there
is a pretty large sub-array called 'glyphs', which happens to be
indexed by glyph id. There are two entries in that sub-array called
'i.sc' and we will want to change the second of those to 'i.scturkish'
(the one at 0x492, the number we discovered above).
Change the lua code to the code below, save your test file, delete the
data cache again, and rerun.
\startluacode
function palapatch (data,filename)
data.glyphs[0x492].name = a.scturkish
end
fonts.otf.enhancers.patches[^pala] = palapatch
\stopluacode
That's one problem fixed. If you look at the test's pdf, it will now
have dotless i's in the smallcaps. But now we have broken the
turkish smallcaps code (it will now also use the first i.sc, which is
wrong) so it is nice to fix that as well. Some searching back and forth
through the pala.ttf.lua code reveals that there are two lookups that
use i.sc: ss_latn_l_13_s (for normal latin) and ss_latn_l_14_s (for
turkish). These lookups are part of the glyph definition of 'i' which
lives at 0x92 (I found that number in the earlier font dump, but you
could also count the entries in pala.ttf.lua, if you are bored or like
counting stuff).
Named lookups are small
[NTG-context] Palatino Linotype under MKIV
Hi,
I'm trying to use the full glyph range of the Palatino Linotype font shipped
with XP (version 1.40; significantly different from the Windows 7 one) under
MKIV. Everything works fine (oldstyle figures, sups for instance), except
that the small cap i character has a dot whereas it shouldn't.
Here's a test file. The result, produced on WinXP / ConTeXt beta 2010-06-23,
is attached.
\definefontfeature[palatinolt-default][script=latn,kern=yes,liga=yes,trep=yes,tlig=yes,protrusion=quality]
\definefontfeature[palatinolt-smcp][script=latn,kern=yes,liga=yes,trep=yes,tlig=yes,protrusion=quality,smcp=yes,onum=yes]
\definefontfeature[palatinolt-sups][mode=node,script=latn,kern=yes,liga=yes,trep=yes,tlig=yes,protrusion=quality,sups=yes]
\starttypescript[serif][palatinolt][name]
\usetypescript[serif][fallback]
\definefontsynonym[Serif][file:pala.ttf][features=palatinolt-default]
\definefontsynonym[SerifBold][file:palab.ttf][features=palatinolt-default]
\definefontsynonym[SerifItalic][file:palai.ttf][features=palatinolt-default]
\definefontsynonym[SerifBoldItalic][file:palabi.ttf][features=palatinolt-default]
\definefontsynonym[SerifCaps][file:pala.ttf][features=palatinolt-smcp]
\stoptypescript
\definetypeface[palatinolt][rm][serif][palatinolt][default]
\setupbodyfont[palatinolt]
\enableprotruding\setuppagenumbering[location=]
\starttext
{\sc \input knuth }
\stoptext
As far as I can see, it has to do with the messy name list of the glyphs.
Both the normal small cap i and the small cap dotted i are named i.sc, but
the wrong one is picked when the smcp feature is activated. Moreover, the
small cap glyphs have no unicode numbers in this font, so I cannot pick them
manually with \char or even with \charX.
Any ideas how I can get the right dottless i?
palatinolt_mkiv_test.pdf
Description: Adobe PDF document
___
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] textbackground and protrusion
Hi! Currently (Context beta 2010-06-20 / Luatex 0.60.1), textbackground and protrusion don't work together. Here's a little test file: --- \showframe \definefontfeature[test][mode=node,script=latn,kern=yes,trep=yes,tlig=yes,protrusion=quality] \definetextbackground[MyTextbackground][frame=off] \enableprotruding \starttext \definedfont[lmroman12-regular*test] An arbitrary and \startMyTextbackground incomplete \stopMyTextbackground\ sentence. \stoptext --- Is there a workaround for this? Thanks in advance. ___ 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] textbackground and protrusion (update)
It seems that the typographical quotation marks got lost in my test file. It has thus become pretty much useless. Just enter some other character instead to make protrusion visible. ___ 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] \setupcapitals[sc=yes] and \setupfootnotes[n=2] problems with luatex
Hi,
The following minimal examples work fine with pdftex, but give unexpected
results with newer betas and luatex (tested under ConTeXt - 2008.11.10 21:40 --
luaTeX-0.30.2):
% engine=luatex
\setupcapitals [sc=yes]
\abbreviation [OTAN] {otan} {Organisation du Traité de l'Atlantique Nord}
\starttext
\OTAN
\stoptext
% engine=luatex
\setupfootnotes [n=2]
\starttext
Test.\footnote{Here's a footnote.} Test.\footnote{And another one.}
\stoptext
The second issue has been reported recently. Maybe some Dutch wizard is working
on it... And, btw, thanks for your amazing type system!
___
Jetzt neu! Schützen Sie Ihren PC mit McAfee und WEB.DE. 30 Tage
kostenlos testen. http://www.pc-sicherheit.web.de/startseite/?mc=00
___
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 : https://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___
[NTG-context] \cite customisation
Hello! Using the bib module for Context for the first time, I wonder if there is a way to change the \cite definition in order to get something like this: \cite[a_schm:73] -- A. Schmitt, Entrückung (author name with initial, short title -- the real title is much longer) as it is common in the humanities, at least in Germany. I didn't find anything in that direction in former posts, I hope I haven't missed anything, and hacking the t-bib.tex file is nothing I can manage by myself. Have a nice week! P ___ SMS schreiben mit WEB.DE FreeMail - einfach, schnell und kostenguenstig. Jetzt gleich testen! http://f.web.de/?mc=021192 ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] \cite customisation
I found the solution, it#8217;s very easy: I have to modify manually the s={}
entry of my .bbl file and with setuppublications[refcommand=short], it works
fine!
Sorry for the noise
P
___
SMS schreiben mit WEB.DE FreeMail - einfach, schnell und
kostenguenstig. Jetzt gleich testen! http://f.web.de/?mc=021192
___
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] Can I use OpenType fonts with ConTe Xt on Windows right now
An easy way to test OpenType fonts with Context/Xetex from scratch under Windows (XP): 1. Get Texlive 2007 2. Install the Context collection with the Texlive Manager (Xetex is included) 3. Create a little test file: \enableregime[utf] \definetypeface[myface][ss][Xsans][Arial]%or any else font in your /windows/fonts folder; run fc-list namelist.txt to get them all \setupbodyfont[myface, 12pt] \starttext Hello World! \stoptext 4. Run texexec --xtx test.tex Sources: http://wiki.contextgarden.net/Fonts_in_XeTeX http://www.fsci.fuk.kindai.ac.jp/kakuto/win32-ptex/web2c75-e.html ___ SMS schreiben mit WEB.DE FreeMail - einfach, schnell und kostenguenstig. Jetzt gleich testen! http://f.web.de/?mc=021192 ___ ntg-context mailing list [EMAIL PROTECTED] http://www.ntg.nl/mailman/listinfo/ntg-context
[NTG-context] Long heading alignment
Hello! First, I want to thank you all. It's my first post here, but I've read many of your emails before, and I've already found a lot of solutions for my problems in there. I'm using Context intensely since several months (before, I was Latex) and at the moment, I'm setting my first big document (400 pages, very boring) with it. My issue: I have a little problem with headings I can't solve by my own. It's rather simple: I would like to align headings that span across multiple lines on the left margin, like this: a) This is (not really) a very, very, very lng title and not that way: a) This is (not really) a very, very, very lng title The use of (\setuphead[section][command=\MySectionCommand] disables the standard alignment mechanism. I wonder if there is a simpler way to achieve this. Any ideas? Thank you very much! Scheeni Grieß (it's Alsatian German) Paul ___ SMS schreiben mit WEB.DE FreeMail - einfach, schnell und kostenguenstig. Jetzt gleich testen! http://f.web.de/?mc=021192 ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
