On 8 mei 2012, at 22:25, Wolfgang Schuster wrote:
Am 08.05.2012 um 19:32 schrieb Meer, H. van der:
I do not get lowercase greek letters on the itemize as should happen with
symbol setup g.
A minimal example, showing the demise of lowercase greek against succes for
uppercase.
It’s a font
Am 09.05.2012 um 10:41 schrieb finkler:
Hi there,
I have a question regarding the spacing and margins of a text document.
My layout is defined like this:
\setuppapersize[A4][A4]
\setuplayout[
topspace=1cm,header=1.5cm,
backspace=3cm,cutspace=3cm,
On 9-5-2012 09:31, Meer, H. van der wrote:
On 8 mei 2012, at 22:25, Wolfgang Schuster wrote:
Am 08.05.2012 um 19:32 schrieb Meer, H. van der:
I do not get lowercase greek letters on the itemize as should happen with
symbol setup g.
A minimal example, showing the demise of lowercase greek
On 9 mei 2012, at 11:15, Hans Hagen wrote:
On 9-5-2012 09:31, Meer, H. van der wrote:
On 8 mei 2012, at 22:25, Wolfgang Schuster wrote:
Am 08.05.2012 um 19:32 schrieb Meer, H. van der:
I do not get lowercase greek letters on the itemize as should happen with
symbol setup g.
A minimal
Hi Hans,
On 2012-05-09 07:31, Meer, H. van der wrote:
Indeed, the greek lowercase appears with \setupbodyfont[postscript].
But not with the brandnew \setupbodyfont[lucidaot], which is
quite a nuisance. Can it be remedied with a more generic mkiv
solution?
if it’s generic enough for your
On Wed, May 9, 2012 at 11:54 AM, Philipp Gesang wrote:
Hi Hans,
On 2012-05-09 07:31, Meer, H. van der wrote:
Indeed, the greek lowercase appears with \setupbodyfont[postscript].
But not with the brandnew \setupbodyfont[lucidaot], which is
quite a nuisance. Can it be remedied with a more
Am 09.05.2012 um 11:50 schrieb Meer, H. van der:
On 9 mei 2012, at 11:15, Hans Hagen wrote:
On 9-5-2012 09:31, Meer, H. van der wrote:
On 8 mei 2012, at 22:25, Wolfgang Schuster wrote:
Am 08.05.2012 um 19:32 schrieb Meer, H. van der:
I do not get lowercase greek letters on the
On 2012-05-09 12:25, Mojca Miklavec wrote:
On Wed, May 9, 2012 at 11:54 AM, Philipp Gesang wrote:
Hi Hans,
On 2012-05-09 07:31, Meer, H. van der wrote:
Indeed, the greek lowercase appears with \setupbodyfont[postscript].
But not with the brandnew \setupbodyfont[lucidaot], which is
quite
Am 09.05.2012 um 11:54 schrieb Philipp Gesang:
Hi Hans,
On 2012-05-09 07:31, Meer, H. van der wrote:
Indeed, the greek lowercase appears with \setupbodyfont[postscript].
But not with the brandnew \setupbodyfont[lucidaot], which is
quite a nuisance. Can it be remedied with a more generic
Hi Hans,
If I understand it correctly, with the \setupbodyfontenvironment one can define
various sizes and then apply them to various styles such as \it, \bf, etc. This
is indeed great!
But in your example the math fonts disappear: is this intended?
Best regards: OK
On 8 mai 2012, at 19:07,
On Wed, May 9, 2012 at 12:39 PM, Philipp Gesang wrote:
On 2012-05-09 12:25, Mojca Miklavec wrote:
If he wants to use Lucida, this would look bad, but the Lucida font
does have greek glyphs, however they are in the math range.
With unicode I thought this was an archaism.
I'm sorry, I'm
On 2012-05-09 13:50, Mojca Miklavec wrote:
On Wed, May 9, 2012 at 12:39 PM, Philipp Gesang wrote:
On 2012-05-09 12:25, Mojca Miklavec wrote:
If he wants to use Lucida, this would look bad, but the Lucida font
does have greek glyphs, however they are in the math range.
With unicode I
Loaded xml with: xmlinclude{problem}{include}{file}
Then called up parts of its contents through a setup:
\startxmlsetups xam:define:get
% The definition is the one with content.
\xmldoiftext{#1}{.}{
\foundtrue
\xmlflush{#1}
\xmlcontext{#1}{.}
}
\stopxmlsetups
The strange thing is that the
On 08/05/12 23:03, Hans Hagen wrote:
On 8-5-2012 16:25, Pablo Rodríguez wrote:
Hi there,
I'm afraid that footnote numbering in body text is wrong in latest beta
(the bug was also in the two previous betas).
Here you have a sample that shows the bug:
\setupnotation[footnote][number=no]
I have realized a slight typo was included in Fig3_5.txt.
The corrected one is attached to this mail.
Hans,
Japanese opening “ should be treated as opening 「, and
closing ” should be treated as closing 」, in the meaning of
spacing and line-breaking.
Thanks,
-- Yusuke.
2012/5/8 KUROKI Yusuke
By accident I found something that seems to work.
With \xmlregistereddocumentsetups{#1}{#1} put before the \xmlflush{#1} ConTeXt
processing resumes on the node.
What I do not understand however, is why \xmlcontext does not work in general.
Is it possible to have the \xmlregistereddocumentsetups
On Mon, 7 May 2012 22:25:37, Wolfgang Schuster
schuster.wolfg...@googlemail.com wrote:
Am 07.05.2012 um 15:03 schrieb Robert Blackstone:
On Mon, May 7, 2012 at 12:00 PM, Hans Hagen pra...@wxs.nl
wrote
On 6-5-2012 23:18, Robert Blackstone wrote:
Sometimes however the example is placed at
On 9-5-2012 13:34, Otared Kavian wrote:
Hi Hans,
If I understand it correctly, with the \setupbodyfontenvironment one can define
various sizes and then apply them to various styles such as \it, \bf, etc. This
is indeed great!
But in your example the math fonts disappear: is this intended?
Calling \xmlregisteredsetups I find an error: \xmlflushsetups is an undefined
controlsequence.
Seems nowhere defined. Occurs in lxml-ini.mkiv
What is wrong here
Hans van der Meer
___
If your question is of
Why does \xmlinclude does not throw an error when the file to be read is
missing? It causes a mssing file to go unnoticed.
In contrast \xmlprocessfile does throw an error, as expected.
Hans van der Meer
___
If
On 9-5-2012 14:53, Meer, H. van der wrote:
Loaded xml with: xmlinclude{problem}{include}{file}
Then called up parts of its contents through a setup:
\startxmlsetups xam:define:get
% The definition is the one with content.
\xmldoiftext{#1}{.}{
\foundtrue
\xmlflush{#1}
\xmlcontext{#1}{.}
On Wed, May 9, 2012 at 1:50 PM, Mojca Miklavec wrote:
On Wed, May 9, 2012 at 12:39 PM, Philipp Gesang wrote:
On 2012-05-09 12:25, Mojca Miklavec wrote:
If he wants to use Lucida, this would look bad, but the Lucida font
does have greek glyphs, however they are in the math range.
With
On Mon, May 7, 2012 at 15:03, Robert Blackstone wrote:
Thank you, Hans, for your quick reply. Unfortunately it does not help
me. The result is basically the same as when I write on
\at{page}[ref], except that, instead of on page 20, I get at page
20, (with the float sitting on page 20).
On Wed, May 09, 2012 at 05:14:39PM +0200, Mojca Miklavec wrote:
but the future seems Bright ;)
We should have named the fonts Lucida Brighter and Lucida Saner etc. ;)
Regards,
Khaled
___
If your question is of
Hey list,
ConTeXt 2012.05.08 13:45 reports that the units module is deprecated and
to use the px module in its place. Is it telling the truth or is this a
harmless warning?
--
Kip Warner -- Software Engineer
OpenPGP encrypted/signed mail preferred
http://www.thevertigo.com
signature.asc
Am 10.05.2012 um 00:39 schrieb Kip Warner:
Hey list,
ConTeXt 2012.05.08 13:45 reports that the units module is deprecated and
to use the px module in its place. Is it telling the truth or is this a
harmless warning?
True and true.
I guess you mean this message: “The units module is
On Wed, 2012-05-09 at 15:39 -0700, Kip Warner wrote:
Hey list,
ConTeXt 2012.05.08 13:45 reports that the units module is deprecated and
to use the px module in its place. Is it telling the truth or is this a
harmless warning?
Nevermind. I'm a fool. It was a Gtk runtime that was issuing an
Hello,
I'm just wonderding if there is a way to switch to an OpenType Math
font (referred to by name or filename, without any predefined
typescript) with some stylistic alternative in the middle of the
document, like in the LaTeX example:
running text ...
On Thu, May 10, 2012 at 2:25 AM, Mojca Miklavec wrote:
Hello,
I'm just wonderding if there is a way to switch to an OpenType Math
font (referred to by name or filename, without any predefined
typescript) with some stylistic alternative in the middle of the
document, like in the LaTeX
On Thu, 2012-05-10 at 00:50 +0200, Wolfgang Schuster wrote:
True and true.
I guess you mean this message: The units module is obsolete because
functionality is built into the core.
What the sentence tells you is that you dont need the units module because
the core has a similar function
30 matches
Mail list logo
