Gnus development mailing list
 help / color / mirror / Atom feed
From: Miles Bader <snogglethorpe@gmail.com>
Cc: Miles Bader <miles@gnu.org>
Subject: Re: Gnus-FAQ: xml to texi with Scheme prog
Date: Mon, 21 Mar 2005 06:55:28 +0900	[thread overview]
Message-ID: <fc339e4a05032013554516e292@mail.gmail.com> (raw)
In-Reply-To: <v9wts2853m.fsf@marauder.physik.uni-ulm.de>

On Sun, 20 Mar 2005 20:55:25 +0100, Reiner Steib
<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.
...
> - 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 the generated file be in the archive at all?  Hmmm, I guess
scheme is an unusual enough language that you can't rely on developers
having it installed (is the implementation hairy enough that it can't
be done in elisp or awk or something?).

>  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?

Yes that would probably work.  The rules for finding arch-tag: in a
file are roughly: (1)  somewhere in the first or last 1K (2K?) of the
file, and (2) string "arch-tag:" on a line preceded by nothing but
puncuation or whitespace.  So splitting the "arch-tag:" in the insert
would be a good idea (e.g., use "arch-" "tag:" instead of
"arch-tag:").

Another method is to use an arch `explicit' tag for the generated file
(gnus-faq.texi), instead of an embedded arch-tag: line; then the
scheme source wouldn't have to insert anything special.  The only
downsides to this are that (1) explicit tags are slightly more clumsy
than tag lines (file moves &c need explicit detection), and (2)
_changing_ the tag basically means it's a new file (so the entire
contents of the file will present in the changeset describing the
changeover, not a diff); of course this last point is only a one-time
cost.

> (I will not install the re-created `gnus-faq.texi' before this is
> clarified.)

Thanks for caring... :-/

-Miles
-- 
Do not taunt Happy Fun Ball.



  reply	other threads:[~2005-03-20 21:55 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 [this message]
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
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=fc339e4a05032013554516e292@mail.gmail.com \
    --to=snogglethorpe@gmail.com \
    --cc=miles@gnu.org \
    /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).