Hi all,
if I compile the following example with the actual beta, the circle is set in
foreground … even if the background is not set.
\startuseMPgraphic{test}
fill fullcircle scaled 5cm withcolor red;
\stopuseMPgraphic
\defineoverlay[test]{\useMPgraphic{test}}
% \setupbackgrounds[page][backg
On Thu, Mar 4, 2010 at 7:10 AM, luigi scarso wrote:
> On Thu, Mar 4, 2010 at 3:35 AM, James Fisher
> wrote:
>
> > - In my humble opinion, TeXies need to get out of the habit of
> > 'self-documenting' TeX using TeX itself. TeX is not some replacement for
> > all markup, it's for producing beauti
Am 04.03.10 15:17, schrieb Andreas Harder:
Hi all,
if I compile the following example with the actual beta, the circle is set in
foreground … even if the background is not set.
\startuseMPgraphic{test}
fill fullcircle scaled 5cm withcolor red;
\stopuseMPgraphic
\defineoverlay[test]{\useMPg
Hi Aditya,
On Thu, Mar 4, 2010 at 4:06 AM, Aditya Mahajan wrote:
> On Thu, 4 Mar 2010, James Fisher wrote:
>
> Right, to show I'm not just empty words, I've just spent ~90 minutes
>> preparing the beginnings of some decent documentation. Presenting
>> http://github.com/eegg/ConTeXt-doc : basic
*tumbleweed*
On Wed, Mar 3, 2010 at 11:09 PM, Vyatcheslav Yatskovsky <
yatskov...@gmail.com> wrote:
> Hi Wolfgang,
>
> To be serious, what \setbreakpoints[] do? I want to wikify this command.
>
> Vyatcheslav
>
> ___
Am 04.03.2010 um 15:31 schrieb Wolfgang Schuster:
> Am 04.03.10 15:17, schrieb Andreas Harder:
>> Hi all,
>>
>> if I compile the following example with the actual beta, the circle is set
>> in foreground … even if the background is not set.
>>
>> \startuseMPgraphic{test}
>> fill fullcircle s
Hello,
These suggestions are a bit a reply to the thoughts of James Fisher.
It would be nice, to have once in the future at least 2 up to date context
documentations:
- a context user manual
For me, it's the merge of all scattered articles and manuals. Each chapter
treats a particular subject, s
On Tue, Mar 2, 2010 at 12:00, Hans Hagen wrote:
> On 26-2-2010 14:09, Mojca Miklavec wrote:
>
>> The behaviour seems to be the same in both MKII and MKIV (MKII only
>> doesn't respect the accented characters; but I understand the pain of
>> recoding).
>
> technically mkii should be able to to the r
Hi Peter,
Thanks for your thoughts. I have wondered previously (in other projects)
about the legitimacy of a distinction between manuals and command
references. With a lot of effort, it can work -- but to make it work,
duplication is inevitable. Manuals simply have to make references to
comman
On Thu, 4 Mar 2010, James Fisher wrote:
On Thu, Mar 4, 2010 at 4:06 AM, Aditya Mahajan wrote:
On Thu, 4 Mar 2010, James Fisher wrote:
(2) converted it all to reStructuredText using html2rest.py (
http://bitbucket.org/djerdo/musette/src/tip/musette/html/html2rest.py)
The values in texweb
On Thu, Mar 4, 2010 at 6:11 PM, Aditya Mahajan wrote:
> I personally prefer a massive PDF to a massive HTML with lots of images.
> With pdf you can also *search* the output. A perfect solution will be to
> generate both outputs from a single source, but that means a custom made
> solution.
Doable
On Thu, 4 Mar 2010, luigi scarso wrote:
On Thu, Mar 4, 2010 at 6:11 PM, Aditya Mahajan wrote:
I personally prefer a massive PDF to a massive HTML with lots of images.
With pdf you can also *search* the output. A perfect solution will be to
generate both outputs from a single source, but that m
On Thu, Mar 4, 2010 at 5:11 PM, Aditya Mahajan wrote:
> On Thu, 4 Mar 2010, James Fisher wrote:
>
> On Thu, Mar 4, 2010 at 4:06 AM, Aditya Mahajan wrote:
>>
>> On Thu, 4 Mar 2010, James Fisher wrote:
>>>
>>> (2) converted it all to reStructuredText using html2rest.py (
>>>
http://bitbuck
Hello Taco,
the following example (I need to admit that I'm not sure how to
properly cite inproceedings) returns a different result in mkii and
mkiv. My citation (the fields I use) is probably a bit wrong, but the
results should be the same in my opinion. (Only mkii shows the year,
in mkiv there's
Hi,
(Forgetting our documentation philosophy session for a minute,)
I'm experiencing issues in MKIV with smart quotes. Specifically, opening
quotes. Compare the output of `texexec dash-test' and `context quote-test'
on the following:
\starttext
`Yes, but --- '
`--- this is an interruption! G
I confirm the above -- with the exception that mkiv does show the year, just
after the authors.
On Thu, Mar 4, 2010 at 5:55 PM, Mojca Miklavec <
mojca.miklavec.li...@gmail.com> wrote:
> Hello Taco,
>
> the following example (I need to admit that I'm not sure how to
> properly cite inproceedings)
On Thu, Mar 4, 2010 at 18:58, James Fisher wrote:
>
> ``Yes, but --- ''
>
> In both cases, MKIV treats the opening grave character (is that the name?
> backtick?) literally rather than as an opening smart quote.
That's on purpose (there are some threads on the mailing list that
explain it). You ma
On Tue, Jan 19, 2010 at 08:31:22PM +0100, Mojca Miklavec wrote:
> - The deciding moment when some of these ugly tricks have been thrown
> away was when we realized that if you do add those tricks, there is no
> way to print the grave accent. (Grave accent will be automatically
> converted to the sa
Apologies, that must have slipped through my shoddy search.
Upon consideration I prefer the \quote and \quotation method. Trusty old
semantic markup. :)
On Thu, Mar 4, 2010 at 6:07 PM, Mojca Miklavec <
mojca.miklavec.li...@gmail.com> wrote:
> On Thu, Mar 4, 2010 at 18:58, James Fisher wrote:
>
On Wed, Jan 20, 2010 at 10:10:07AM +0100, Hans Hagen wrote:
> (actually one of my reasons for never using `` '' is that it looks
> quite ugly in the source as the second pair is not tilted and i hate
> ugly looking sources)
Since I'm using Inconsolata while reading this email, I had hard time
unde
On Wed, Jan 20, 2010 at 03:42:11PM +0100, Mojca Miklavec wrote:
> On Wed, Jan 20, 2010 at 10:58, Alan BRASLAU wrote:
> >
> > I'm not sure that I understand the
> > problem with ` (GRAVE ACCENT) that cannot be solved with a macro or by a
> > setting that disactivates the production of ‘ (LEFT SINGLE
On Thu, Mar 4, 2010 at 3:25 PM, James Fisher wrote:
> lol; I thought this might come up. I have a couple of replies to that:
>
> (1) First and most important: I'm not suggesting that we use TeX to document
> things at all. I'm suggesting that ConTeXt documentation should be
> accessible to newco
On Thu, Mar 4, 2010 at 6:30 PM, Aditya Mahajan wrote:
> On Thu, 4 Mar 2010, luigi scarso wrote:
>
>> On Thu, Mar 4, 2010 at 6:11 PM, Aditya Mahajan wrote:
>>>
>>> I personally prefer a massive PDF to a massive HTML with lots of images.
>>> With pdf you can also *search* the output. A perfect solu
" We are pleased to announce that Adobe has joined our corporate
sponsorship program."
http://www.lua.org/sponsors.html
--
luigi
___
If your question is of interest to others as well, please add an entry to the
Wiki!
Hi Luigi,
On Thu, Mar 4, 2010 at 6:42 PM, luigi scarso wrote:
> On Thu, Mar 4, 2010 at 3:25 PM, James Fisher
> wrote:
> > lol; I thought this might come up. I have a couple of replies to that:
> >
> > (1) First and most important: I'm not suggesting that we use TeX to
> document
> > things at
On Thu, 4 Mar 2010, James Fisher wrote:
I'm not saying that a dcvs is useless for documentation or manuals.
But without contributors a dcvs can be practically useless,
and the only contributors for manuals actually are Taco for luatex and
Hans for Context mkiv.
Why are they the only contribut
On Thu, Mar 4, 2010 at 20:08, luigi scarso wrote:
> " We are pleased to announce that Adobe has joined our corporate
> sponsorship program."
> http://www.lua.org/sponsors.html
Oh, I already see Hans replacing his "javascript in pdf documents"
strategy with "fun with lua scripts in pdf documents" n
On Thu, Mar 4, 2010 at 8:44 PM, James Fisher wrote:
>ConTeXt was not created to produce documentation for ConTeXt.
This is not the point.
The point is that code documentation of ConTeXt can be made with ConTeXt .
see for example http://foundry.supelec.fr/gf/project/modules/scmsvn
We don't need S
On Thu, Mar 4, 2010 at 9:30 PM, Mojca Miklavec
wrote:
> On Thu, Mar 4, 2010 at 20:08, luigi scarso wrote:
>> " We are pleased to announce that Adobe has joined our corporate
>> sponsorship program."
>> http://www.lua.org/sponsors.html
>
> Oh, I already see Hans replacing his "javascript in pdf doc
The important thing is: is there _ever_ going to be a manual? I
want to try Context, but I've been putting it off for years because
it's not really practical without documentation. There must be many
others in the same situation.
_
On Thu, Mar 4, 2010 at 10:31 PM, Michael Saunders wrote:
> The important thing is: is there _ever_ going to be a manual? I
> want to try Context, but I've been putting it off for years because
> it's not really practical without documentation. There must be many
> others in the same situation.
On Thu, 4 Mar 2010, Michael Saunders wrote:
The important thing is: is there _ever_ going to be a manual? I
You mean like the beginner's manual
http://www.pragma-ade.com/general/manuals/ms-cb-en.pdf
and the user manual
http://www.pragma-ade.com/general/manuals/cont-eni.pdf
want to try
A bit of a diversion here, but two questions about the plethora of PDF docs:
* Where are the TeX sources of all these manuals kept?
* What are the licenses on all these various things? In particular the
Pragma documents. Would I be *allowed*, if I so wanted, to embark on a
collated version of al
" We are pleased to announce that Adobe has joined our corporate
> sponsorship program."
> http://www.lua.org/sponsors.html
Oh, I already see Hans replacing his "javascript in pdf documents"
strategy with "fun with lua scripts in pdf documents" now:)
Wow. I first decided that Adobe
%%
%%# egrep trackers\.reg *|perl -ne
'if(s/.*trackers\.register\("([^"]+)"/$1/){print
"\\enabletrackers[$1]\n"}' -|sort|uniq
%%
\enabletrackers[afm.features]
\enabletrackers[afm.indexing]
\enabletrackers[afm.loading]
\enabletrackers[asciimath.mapping]
\enabletrackers[backend.detail]
\enabletracker
There was a thread about columns and whitespace ~ 2 weeks ago, but I wasn't
a subscriber then. I've just come across it independently myself. I'm not
sure what conclusion was come to. From a few tests, I'd characterize the
problem code in \startcolumns as: "if whitespace has been set to more tha
On Thu, 4 Mar 2010, James Fisher wrote:
A bit of a diversion here, but two questions about the plethora of PDF docs:
* Where are the TeX sources of all these manuals kept?
svn://ctx.pragma-ade.nl/manuals (seems to be down at the moment)
browsable at
http://context.aanhet.net/svn/
This info
Good news on both counts, then. (Is there a reason that the source and
license of the documents aren't included in the docs themselves?)
On Thu, Mar 4, 2010 at 11:05 PM, Aditya Mahajan wrote:
> On Thu, 4 Mar 2010, James Fisher wrote:
>
> A bit of a diversion here, but two questions about the p
On Thu, 4 Mar 2010, James Fisher wrote:
Good news on both counts, then. (Is there a reason that the source and
license of the documents aren't included in the docs themselves?)
All the docs refer to the readme file which states the license
http://wiki.contextgarden.net/Read_Me
Aditya
___
(Can I leave all of this for a bit? I'll reply tomorrow, I think, but
first...)
I'd like to go back to the very first post about problems with flush right.
The \setbreakpoints command works to an extent, but I'm still experiencing
issues where, when a hyphenated string has been broken, the first
On Thu, 4 Mar 2010, James Fisher wrote:
I'd like to go back to the very first post about problems with flush right.
The \setbreakpoints command works to an extent, but I'm still experiencing
issues where, when a hyphenated string has been broken, the first half of it
still sticks out. I unfortu
Perfecto.
On Thu, Mar 4, 2010 at 11:36 PM, Aditya Mahajan wrote:
> On Thu, 4 Mar 2010, James Fisher wrote:
>
> I'd like to go back to the very first post about problems with flush
>> right.
>> The \setbreakpoints command works to an extent, but I'm still experiencing
>> issues where, when a hyp
> You mean like the beginner's manual
>
> http://www.pragma-ade.com/general/manuals/ms-cb-en.pdf
>
> and the user manual
>
> http://www.pragma-ade.com/general/manuals/cont-eni.pdf
>
...
>
> amongst 46 others by Pragma
No, not like those. I mean like a real manual. I read the book
about Hasselt-
"...the book about Hasselt". That actually made me laugh out loud. What a
loser I am.
Ok, goodnight now. :)
On Fri, Mar 5, 2010 at 2:10 AM, Michael Saunders wrote:
> > You mean like the beginner's manual
> >
> > http://www.pragma-ade.com/general/manuals/ms-cb-en.pdf
> >
> > and the user manual
Just to clarify, I pretty much agree with everything you say.
On Fri, Mar 5, 2010 at 2:22 AM, James Fisher wrote:
> "...the book about Hasselt". That actually made me laugh out loud. What a
> loser I am.
>
> Ok, goodnight now. :)
>
>
> On Fri, Mar 5, 2010 at 2:10 AM, Michael Saunders wrote:
>
>
Am 04.03.10 23:56, schrieb James Fisher:
There was a thread about columns and whitespace ~ 2 weeks ago, but I
wasn't a subscriber then. I've just come across it independently
myself. I'm not sure what conclusion was come to. From a few tests,
I'd characterize the problem code in \startcolumn
Am 05.03.10 03:10, schrieb Michael Saunders:
I've looked at most of the fifty or so documents over which
this virtual manual is supposed to be spread. They are about
as informative. Most of these documents seem to be 5--12
years old.
*The LaTeX manual* is 16 years old.
http://www.pearsonh
On Fri, Mar 05, 2010 at 05:34:39AM +0100, Wolfgang Schuster wrote:
> Am 05.03.10 03:10, schrieb Michael Saunders:
>
> I've looked at most of the fifty or so documents over which
> this virtual manual is supposed to be spread. They are about
> as informative. Most of these documents s
On Fri, Mar 5, 2010 at 03:10, Michael Saunders wrote:
>
> You can't be serious about "mk.pdf" being a manual. Even it
> admits, "This document is not so much a users manual as a
> history of the development." Little after that point is intelligible.
>
Yes, I agree with you on this point !
_
49 matches
Mail list logo
