[REBOL] Re: building a dynamic path to elements in block
From: null_dev:ya:hoo at: 2-Nov-2000 16:16
>Yes, paths can be "interesting"! They are aggressively evaluated
>and don't have quite as much freedom in compsition as one might
> print structure-block/1/:count
>However, my curiousity is killing me... You wrote
>I can't figure out how your block relates to XML. It isn't the output
>from parse-xml, it doesn't correspond to XML by replacing the block
>brackets with tag brackets, and it isn't literal REBOL either...
Thanks for the tip.
The error in the blocks are probably from my hasty cutting and pasting - yes
they should be strings.
As to what I'm doing, It's a case of making a simple task really complicated
(but interesting :-} ) I've been learning Ancient Greek and I came across the
Perseus collection of texts (if you set it up correctly you can get the texts
in Greek with the pitch accents) Because their server can be a little shaky I
started making some local copies. Each text is about 150+ pages of html so I
was concatenating them, however this led to them being a little to much for
my browser so I thought of breaking them up .... blah blah blah... I noticed
from errors and other clues in the html that they were probably based on
TEI.2 (Text encoding Initiative) xml or sgml, and since I'm particularly
interested in multi-lingual etext and xml I thought I'd learn REBOL by
writing some scripts to reverse engineer the texts into something like the
original xml/sgml, And from there I could generate any number of layouts for
....... I apologise if this was far too much information.
For later reference I was wondering whether there was any clever way to
handle the two to three character strings that UTF-8 uses to encoded non-asci
unicode. For the moment I can avoid the issue - partly because my BeOS shell
displays the characters correctly, and partly because I don't really want to
do any damage to the ancient greek. But I could envisage transcoding problems
down the track.