Gnus development mailing list
 help / color / mirror / Atom feed
From: sigurd@12move.de (Karl Pflästerer)
Subject: Re: Gnus-FAQ: xml to texi with Scheme prog
Date: Mon, 21 Mar 2005 23:04:10 +0100	[thread overview]
Message-ID: <usm2od5sb.fsf@hamster.pflaesterer.de> (raw)
In-Reply-To: <v9wts2853m.fsf@marauder.physik.uni-ulm.de>

On 20 Mrz 2005, reinersteib+gmane@imap.cc wrote:

>
> On Tue, Mar 15 2005, Karl Pflästerer wrote:
> [ Scheme program to transform `gnus-faq.xml' to `gnus-faq.texi' ]
>
> I have installed the files `xml2texi.scm' and `xml2texi.sh' in texi/
> in the v5-10 branch.  I did some modifications on `xml2texi.scm' and
> `gnus-faq.xml' to improve the printed output.
>
> Some questions and remarks (not all related to xml2texi):
>
> - `+section-comments-alist+' should be put into `gnus-faq.xml'.

As I wrote in pm I think the best place for that information would be
attributes to the section titles.  If that would be changed I could
change also the Scheme program. 

> -  The "Changes" section should not be present in the texi version.

I'll look for that.


> -  Is there a possibility to add @cindex entries in `gnus-faq.xml'?

XML knows some sort of index commands; so if they were present in the
XML source they could be included in the generated texi file.  Maybe
this could be done together with the solution for the
+section-comments-alist+'.

> - <userinput>...</userinput> is translated to @samp{...}.  It would be
>   nice to have @kbd{T n}, @code{tar xvzf ...}, @file{~/.gnus.el}, etc.

I used the same format I found in the texi file.  The problem I see
here: how should the translating program know when to use e.g. @kbd and
when @code since both forms are included with the same tag: `userinput'

Maybe we find together a solution.

> - Currently texi/gnus-faq.texi has the following arch tag:
>
> ,----
>| @ignore
>|    arch-tag: 64dc5692-edb4-4848-a965-7aa0181acbb8
>| @end ignore
> `----
>
> How to deal with this?  Should we add something like...
>
>   (insert "@ignore\n   "
>           "arch-tag: "
> 	  "64dc5692-edb4-4848-a965-7aa0181acbb8"
>           "\n@end ignore")
>
> ... in `main' in `xml2texi.scm'?  I guess this would make sure that it
> is not confused with the arch tag of the file `xml2texi.scm'.  Miles?
> (I will not install the re-created `gnus-faq.texi' before this is
> clarified.)
>
> Bye, Reiner.

   KP



  parent reply	other threads:[~2005-03-21 22:04 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-09 19:41 Karl Pflästerer
2005-03-15 18:16 ` Reiner Steib
2005-03-15 19:22   ` Karl Pflästerer
2005-03-20 19:55     ` Reiner Steib
2005-03-20 21:55       ` Miles Bader
2005-03-21 18:37         ` Reiner Steib
2005-03-21 22:32           ` Karl Pflästerer
2005-03-21 22:47           ` Miles Bader
2005-03-22  9:45             ` Reiner Steib
2005-03-23  0:44               ` Miles Bader
2005-03-21 22:11         ` Karl Pflästerer
2005-03-21 22:04       ` Karl Pflästerer [this message]
2005-03-22 16:46       ` Reiner Steib
2005-03-23  8:30       ` Miles Bader
2005-03-23  8:56         ` Reiner Steib
2005-03-23  9:48           ` Miles Bader
2005-03-23 14:53             ` Reiner Steib

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=usm2od5sb.fsf@hamster.pflaesterer.de \
    --to=sigurd@12move.de \
    --cc=khp@pflaesterer.de \
    /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).