Re: [NTG-context] Wiki and source code browser

2004-10-01 Thread Christopher Creutzig
Patrick Gundlach wrote:
BTW: I have installed yet another service at contextgarden.net, the
source browser.
 Nice.  But I think the search should ignore the fmt files, they won't 
be displayed anyway.  I'd also welcome an option not to search in *.tws 
nor *-scite.properties, I have not found a use for them yet.

regards,
Christopher Creutzig
___
ntg-context mailing list
[EMAIL PROTECTED]
http://www.ntg.nl/mailman/listinfo/ntg-context


[NTG-context] Re: Wiki and source code browser

2004-10-01 Thread Patrick Gundlach
Hello Christopher,

 BTW: I have installed yet another service at contextgarden.net, the
 source browser.

   Nice.  But I think the search should ignore the fmt files, they
   won't be displayed anyway.  I'd also welcome an option not to search
   in *.tws nor *-scite.properties, I have not found a use for them
   yet.

Good point. I exclude now *fmt, *mem, *properties, *tws. Thanks  for
the feedback,

Patrick
-- 
ConTeXt wiki: http://contextgarden.net
texshow-web:  http://texshow.contextgarden.net
List archive: http://archive.contextgarden.net
garden news:  http://news.contextgarden.net
___
ntg-context mailing list
[EMAIL PROTECTED]
http://www.ntg.nl/mailman/listinfo/ntg-context


Re: [NTG-context] Context against XSL

2004-10-01 Thread Hans Hagen
Taco Hoekwater wrote:
Hans Hagen [EMAIL PROTECTED] wrote:

I'm on and off implementing an fo engine (foxet) and run into fuzziness 
with regards to the specs (a bad omen is that that there i could not 
find a good manual and the ones i have are made up rather poorly, which 
indicated that we're not so much dealing with high end typesetting, but 
with regular batchprocessing of not too complex documents).
 
The longer one has to read in the XSL-FO specification, the more one 
resents having to do so. If you are lookiing for a road towards creating 
pdf documents, then ConTeXt is like an actual freeway with perhaps a few 
potholes and missing roadsigns, where XSL-FO is a set of directions on how 
to create a jungle road, written down by a civil engineer with terrible
handwriting mirroring a quite chaotic mind who nonetheless insists on 
doing everything the right way(tm). 
you're right! unfortunately those engineers can ride on the back of the 
horse with xml painted all over it, which makes it good by principle for 
those who pay them; an interesting aspect of this is that while xml 
opens many roads, the tendensy is towards taking one road; there is 
probably some thinking behind this that we suddenly can solve all 
problems for ever and do with one road.

btw, as with much xml related things: much of what is around as 
'standard' is actually just a reversed engineered application interface, 
or worse: serving as an interface to different applications which makes 
it fuzzy; take xsl: there are a lot of dupplicate attributes just to 
serve css; this is strange because the whole idea behind xslt (which is 
mostly ok) is that one can transform, so there is no need for those 
duplicates. The engineer serves to many masters.

apart from the specs, fo lacks a real proper box model: (like css, there 
is no real way to do for instance vertical alignment comparable with 
tex's fill's); it somehow started from the wrong angle;  and then .. how 
about math, chemistry, etc -) a long road ahead

Various people have been busy trying to build that road according to the 
specifications, and some of the toll (payfare) roads are in fact reasonably 
close. I'm speaking with a certain fondness in my voice really, because I 
am also busy implementing a (commercial) fo engine using ConTeXt.
-)
comparisons between the not-taco engines show big differences (also in 
price) and as soon as extensions start coming into the picture, the 
'acclaimed advantage of fo' disappears. Some peeople pay five digit 
numbers for engines where formulas has to be included as graphic.

I sometimes wonder if it makes sense to cook up an alternative model on 
top of context -)

Hans
-
  Hans Hagen | PRAGMA ADE
  Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
 tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com
 | www.pragma-pod.nl
-
___
ntg-context mailing list
[EMAIL PROTECTED]
http://www.ntg.nl/mailman/listinfo/ntg-context


Re: [NTG-context] Fonts in ConTeXt

2004-10-01 Thread Willi Egger
Context support out of the box the freely available fonts delivered with 
TEX-live. Beyond this, it supports a couple of commercial fonts like 
lucida bright. For other commercial fonts you will have to setup 
typescripts and map files.

Kind regards Willi
Werner Struckmann wrote:
We have installed quite a lot of fonts
(mathtimepro, lucidabr, cm-super, ...).
Currently we are using these fonts with
LaTeX. All fonts are working correctly, i. e.
we have the following files for each font
  afm/tfm/vf/pfb
as well as map file for
  xdvi, dvips, dvipdfm and pdftex,
Here is my question: How can we use all these
fonts with ConTeXt? Is there an easy way to do
so?
Yours,
Werner
___
ntg-context mailing list
[EMAIL PROTECTED]
http://www.ntg.nl/mailman/listinfo/ntg-context


AW: AW: [NTG-context] PPCHTeX Bug?

2004-10-01 Thread Thomas Meyer
Thanks to all who answered me! Special thanks to Tobias.
I will use ochem or something like that under LaTeX because I need
seven-membered rings.
Or is it possible to use ochem under ConTeXt?

Greetings

Thomas

Is it possible to create seven-membered ring-systems with ppchtex? I 
never found something in the manual about it.
  

Probably not. Hans, how about implementing those?

No answer from Hans!

___
ntg-context mailing list
[EMAIL PROTECTED]
http://www.ntg.nl/mailman/listinfo/ntg-context


[NTG-context] Re: Context against XSL

2004-10-01 Thread Nikolai Weibull
* Hans Hagen [EMAIL PROTECTED] [Oct 01, 2004 12:40]:
 comparisons between the not-taco engines show big differences (also in
 price) and as soon as extensions start coming into the picture, the
 'acclaimed advantage of fo' disappears. Some peeople pay five digit
 numbers for engines where formulas has to be included as graphic.

Heh, serious?  That's incredible.  I'm really beginning to doubt the
authoring in XML-bandwagon's legitimacy.
nikolai

--
::: name: Nikolai Weibull:: aliases: pcp / lone-star / aka :::
::: born: Chicago, IL USA:: loc atm: Gothenburg, Sweden:::
::: page: www.pcppopper.org  :: fun atm: gf,lps,ruby,lisp,war3 :::
main(){printf(linux[\021%six\012\0],(linux)[have]+fun-97);}
___
ntg-context mailing list
[EMAIL PROTECTED]
http://www.ntg.nl/mailman/listinfo/ntg-context


Re: [NTG-context] Re: Context against XSL

2004-10-01 Thread Matt Gushee
On Fri, Oct 01, 2004 at 12:53:22PM +0200, Nikolai Weibull wrote:
 * Hans Hagen [EMAIL PROTECTED] [Oct 01, 2004 12:40]:
  comparisons between the not-taco engines show big differences (also in
  price) and as soon as extensions start coming into the picture, the
  'acclaimed advantage of fo' disappears. Some peeople pay five digit
  numbers for engines where formulas has to be included as graphic.
 
 Heh, serious?  That's incredible.  I'm really beginning to doubt the
 authoring in XML-bandwagon's legitimacy.
   nikolai

You and most of the XML community (I once claimed to be part of that,
but have lately tried to distance myself, partly for the reasons being
discussed here). The original idea was that XML would be a new and
better way to author *Web documents*. Somewhere along the line it
morphed into a general-purpose, universal data exchange format, in which
capacity it serves reasonably well (though it likely should have been
designed differently, had people foreseen how it would actually be
used). 

Meanwhile, a ragged band of diehards continued trying to develop
and promote XML specifically as a web technology and/or a document
technology, but I think very few people have much hope in that area any
more. There was an article on O'Reilly Network's XML.com in July
entitled XML on the Web has Failed; that may not settle the question,
but such a statement would have been unthinkable 2 or 3 years ago.

But to get back to the question of XSL: a couple of years ago I was
looking for a way to generate print-ready documents from XML. I tried
the then-latest version of FOP, which was and maybe still is the most
popular open-source XSL-FO processor. I was amazed, after several years
of its development by the Apache project, how many features were
unimplemented, including some that I considered obvious and important
for complex documents (I think, for example, there was no way to do
footnotes). In hindsight, this probably shouldn't have been surprising.
Print documents are complex, and few people are interested in them,
relative to the Web. There probably aren't enough users or interested
programmers to support more than a couple of high-quality products in
this problem space.

Anyway, when I found that FOP wouldn't meet my needs, I started
searching for something else--and found ConTeXt.  Architecturally, it
may not have XSL's Neoclassical tidiness, but it has one huge advantage:
it works.

-- 
Matt Gushee When a nation follows the Way,
Haven Rock PressHorses bear manure through
Englewood, Colorado, USAits fields;   
[EMAIL PROTECTED] When a nation ignores the Way,
Horses bear soldiers through
its streets.

--Lao Tzu (Peter Merel, trans.)
___
ntg-context mailing list
[EMAIL PROTECTED]
http://www.ntg.nl/mailman/listinfo/ntg-context