From: Maurício <briqueabraque@yahoo.com>
To: ntg-context@ntg.nl
Subject: Re: How could a typesetting system be today?
Date: Fri, 13 Jun 2008 15:32:25 -0300 [thread overview]
Message-ID: <g2uefr$l1b$1@ger.gmane.org> (raw)
In-Reply-To: <09BF9DCC-1089-44E7-BD79-C06C61FEDBE2@fiee.net>
>> The reason for a standard tag language is that the main engine
>> should be able to do some operations on data, like breaking it
>> in pieces like words, paragraphs or staffs on music scores,
>> sometimes without fully understanding what exactly those are.
>>
>> Possible outcomes: with a proper script language (Lua?), things
>> like tables, multi-column text, and even a lot of crazy ideas
>> could be really easy to write. Plug-ins results would be
>> predictable, since they know nothing about the world except
>> what the main engine has informed them.
>
>
> As far as I can judge, music typesetting has completely
> different rules than text typesetting.
Sure.
>
> Ok, you would "just" use another plugin. But then the plugins
> need a way to interact: captions in graphics (like in MetaPost
> today), lyrics in music etc.
That's the idea. I do believe it's possible.
>
> I myself wouldn't probably able to handle a MetaPost based
> system (or something similar) - even if I "speak" a bit of
> PostScript, I just don't think of graphics as formulae:
Myself, I never touch my computer mouse :)
I did read an answer from Donald Knuth on why he thinks Metafont
never became a popular tool for font creation. His answer: you
can't ask an artist to become enough of a mathematician in order
to be able to design his font based on 60 variables.
> However, you need different parsers for different types of
> content
A system like what I want should have a common language for
all. I'm not smart enough to say which one.
> (I don't speak Lisp. I don't speak TeX-the-language or Lua as
> well. But the latter seems easy.)
Yes, it is easy and powerfull. And it was created here in Brazil!
(Proud smile)
> There is your unified system. XML rulez - for better or for
> worse. It's really no fun to write XML by hand.
But, as you said, TeX and Lilypond have a similar syntax. I belive
they could share some kind of common language.
> Perhaps you should try to help enhancing OpenOffice's typesetting? #
> Or Scribus?
I really would like something we could program, and then change
design variables at will.
Thanks for your comments. I have no knowledge to go beyond
what I went in my first message.
Best,
Maurício
___________________________________________________________________________________
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
___________________________________________________________________________________
next prev parent reply other threads:[~2008-06-13 18:32 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-30 4:18 Maurício
2008-05-30 5:08 ` Aditya Mahajan
2008-05-30 7:10 ` luigi scarso
2008-05-30 7:12 ` Yue Wang
2008-05-30 9:53 ` Steffen Wolfrum
2008-05-30 10:00 ` Steffen Wolfrum
2008-05-30 12:24 ` Yue Wang
2008-05-30 12:31 ` Idris Samawi Hamid
2008-05-30 19:04 ` Henning Hraban Ramm
2008-05-31 2:20 ` luigi scarso
2008-05-31 10:18 ` Henning Hraban Ramm
2008-05-31 11:32 ` luigi scarso
2008-05-31 12:57 ` Yue Wang
2008-05-31 15:29 ` luigi scarso
2008-05-31 15:28 ` luigi scarso
2008-05-31 21:23 ` Hans Hagen
2008-06-01 16:58 ` luigi scarso
2008-06-03 0:02 ` the error of xetex Yanli Li
2008-06-03 6:04 ` Wolfgang Schuster
2008-06-03 7:58 ` Yanli Li
2008-06-03 8:08 ` Wolfgang Schuster
2008-06-03 11:58 ` Yanli Li
2008-06-03 12:34 ` Wolfgang Schuster
2008-06-03 12:59 ` Yanli Li
2008-06-03 12:48 ` Mojca Miklavec
2008-06-03 16:39 ` Peter Münster
2008-06-03 12:16 ` Yanli Li
2008-06-03 13:05 ` Wolfgang Schuster
2008-05-30 14:15 ` How could a typesetting system be today? Steffen Wolfrum
2008-05-30 14:45 ` Alan BRASLAU
2008-05-30 7:37 ` Taco Hoekwater
2008-05-30 11:23 ` Martin Schröder
2008-05-30 7:26 ` Taco Hoekwater
2008-05-30 8:40 ` Yue Wang
2008-05-30 11:07 ` Olivier Guéry
2008-06-12 0:12 ` Maurício
2008-06-12 0:35 ` Idris Samawi Hamid
2008-06-12 18:26 ` Maurício
2008-06-13 17:26 ` Henning Hraban Ramm
2008-06-13 18:32 ` Maurício [this message]
2008-06-13 19:45 ` Charles P. Schaum
2008-06-14 16:24 ` Olivier Guéry
2008-06-12 4:27 ` Charles P. Schaum
2008-06-12 17:39 ` How could a typesetting system be today? (slightly off-topic, flame and nostalgic) Maurício
2008-06-12 17:52 ` Hans Hagen
2008-06-12 18:34 ` Aditya Mahajan
2008-06-13 15:41 ` Maurício
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='g2uefr$l1b$1@ger.gmane.org' \
--to=briqueabraque@yahoo.com \
--cc=ntg-context@ntg.nl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).