A new element really? what about the "type" attribute on <div>?
We shovelled the snow yesterday here in Toronto, Canada :) We tend to be
in long haul mode for winter and are careful about the quick and the dirty
in case there is environmental damage or difficulty managing in the long
run. Well, enough conceit.
<div type="cipher">... </div>
and the "corresp" attribute allows for the connection to a de-ciphering
translation -- oh yeah Canada not only has winter, it's officially
bilingual too, eh!
> Quick-and-dirty reply, I'm supposed to be shoveling :-)
> > ... ciphers. The element <expan> has a definition that appears to
> > be fine for the purpose, but is there any other element more
> > specifically designed for such cases?
> Not that I'm aware of. And while <expan> seems OK, it isn't really
> exactly the right thing. (A enciphered text isn't really an
> abbreviation of a clear text.) But from your example I see that you
> and I are using the term "cipher" differently. I would call what you
> seem to have a "code" (substituting words or phrases for words or
> phrases), and the rot13 algorithm a (simple) "cipher" (substituting
> characters 1-for-1).
> For (what I call) ciphers, I think <expan abbr=> (or <abbr expan=>)
> is the closest we have in vanilla TEI, but that one would do much
> better to invent a new element and attribute pair <enciphered
> cleartext=> (and perhaps <cleartext enciphered=> to be complete) with
> TEIform=expan (and perhaps "abbr"); might prefer <ciph clr=> if you're
> into brevity.
> For (what I call) codes, I think <orig reg=> (or <reg orig=>) is the
> closest we have in vanilla TEI, but that one would do much better to
> invent a new element and attribute pair <encoded decoded=> (and
> perhaps <decoded encoded=> to be complete) with TEIform=orig (and
> perhaps "reg"); might prefer <enc dec=> if you're into brevity.
> > The expansions of the ciphers are usually written above the
> > ciphers by the secretary of the recipient, but in some cases the
> > job is left to the present editor, in which cases one should add
> > the attribute resp="ed".
> As long as this practice is made clear somewhere in the TEI header
> (so that someone reading the file years from now can discern what
> text was written by the author of the letter and what was written by
> the recipient's secretary), this makes good sense to me. You may want
> to make the distinction explicitly, though, with resp="rcpt" or some
<activity>Actively visiting <?insert URN?></activity>
<motto><w corresp="grok">gork</w> structure, savour <w
corresp="peace">content</w>, <s ana="play-with-piece">enjoy