From: Henning Hraban Ramm <angerweit@gmx.net>
Subject: Re: Context manuals
Date: Wed, 23 Oct 2002 21:15:06 +0200 [thread overview]
Message-ID: <200210232115.06809.angerweit@gmx.net> (raw)
In-Reply-To: <5.1.0.14.1.20021023012020.0281cea0@remote-1>
Am Mittwoch, 23. Oktober 2002 01:23 schrieb Hans Hagen:
[AUTHOR]
> >Perhaps <faq author="user"> is better.
> >I'd use your verbose tags only in a user database.
> but you want to typeset the names correctly, and also be able to sort them
> in several ways ...
But I get much redundancy and perhaps inconsistency if I give whole author
information in every question.
Therefore I would only give some short name ("login") and collect the whole
information (forename, surname, email, homepage, quote...) in a separate
authors/users database.
[KEYWORDS]
> > > <entry key="xyz">exeizet</entry>
> >The bundling is ok, but why should the entry use an option?
> unless you also want to sort 'm, typeset them, etc
> xml is about reusing information !
Please explain, what the 'key="xyz"' is for?
I would define keywords for searching (web version) and indexing (PDF version)
-- what does a keyword need an other description?
e.g.
<keywords>
<entry>math</entry>
<entry>formula</entry>
</keywords>
or perhaps
<keywords>
<entry lang="en">math</entry>
<entry lang="en">formula</entry>
<entry lang="de">Mathematik</entry>
<entry lang="de">Formel</entry>
</keywords>
(I'd like to make the FAQ multilingual, but I guess it's too much work...)
> of course they can link, just define your element/attribute as such; it's
> up to you to define that something links:
> <whatever file="..." location="..."/>
would be
<author file="authors.xml">hans</author>
<editor file="authors.xml">hraban</editor>
correct?
Grüßlis vom Hraban!
--
http://www.ramm.ch/context/
---
next prev parent reply other threads:[~2002-10-23 19:15 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-18 2:32 [NTG-context] " John Culleton
2002-10-18 18:48 ` Henning Hraban Ramm
2002-10-18 20:44 ` Jens-Uwe Morawski
2002-10-20 16:56 ` Hans Hagen
2002-10-20 17:48 ` Henning Hraban Ramm
2002-10-20 18:42 ` Hans Hagen
2002-10-21 12:00 ` Jens-Uwe Morawski
2002-10-21 18:15 ` [NTG-context] FAQ structure (was: Context manuals) Henning Hraban Ramm
2002-10-21 21:22 ` [NTG-context] FAQ structure Jens-Uwe Morawski
2002-10-22 8:59 ` [NTG-context] Context manuals Hans Hagen
2002-10-22 19:34 ` Henning Hraban Ramm
2002-10-22 23:23 ` Hans Hagen
2002-10-23 19:15 ` Henning Hraban Ramm [this message]
2002-10-23 22:00 ` Hans Hagen
-- strict thread matches above, loose matches on Subject: below --
2002-02-21 19:32 John Culleton
2002-02-20 9:22 ` Patrick Gundlach
2002-02-20 9:28 ` Frans Goddijn
2002-02-20 18:57 ` W. Egger
2002-02-20 23:23 ` Bruce Horrocks
2002-02-21 13:59 ` Frans Goddijn
2002-02-22 14:02 ` Bruce Horrocks
2002-02-22 16:01 ` John Culleton
2002-02-27 19:26 ` Hans Hagen
2002-02-22 20:09 ` John Culleton
2002-02-21 9:11 ` Taco Hoekwater
2002-02-22 17:39 ` John Culleton
2002-02-20 17:52 ` Frans Goddijn
2002-02-25 13:58 ` Hans Hagen
2002-02-25 16:16 ` Frans Goddijn
1999-11-22 8:08 Berend de Boer
1999-11-22 6:47 Zeljko Vrba
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=200210232115.06809.angerweit@gmx.net \
--to=angerweit@gmx.net \
/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).