> >How about (just to throw out an idea) this syntax? > >=head1 NAME Etaoinshrdlu > >or > >=head1 Etaoinshrdlu NAME > >Or maybe > >=head1 Etaoinshrdlu (NAME) > > Do you mean "Etaoinshrdlu" here to stand for the name of the module, or the > word for "Name" in whatever language?
The latter. > >What if someone wants to index multilingual pods, in all the languages? > > I'm not sure what kind of document (and syntax for document start, and kind > of indexing) you have in mind here. Can you make up an example? =head1 DESCRIPTION ... =head1 Qwertyuiop (DESCRIPTION) ... And then someone wanting create an index where both DESCRIPTION and Qwertyuiop are recognized as "descriptions". All this makes sense of course only for applications that have defined some semantics for some particular sections. > >(2) I haven't actually seen Autrijus =encoding proposal :-) ... but how > >about the possibility of indicating the languages, too? =language > >ISO639codehere. > > Just for the sake of metadata, you mean? What uses do you have in mind for > this? Mixing several languages in the same document but marking the appropriate sections with their languages so that a "subdocument" containing only a subset of the languages can be extracted. > (BTW, of course you mean RFC-3066 code. We wouldn't want to leave > out things like yi-latn, which aren't valid via an ISO-639 grammar, > but rely on the grammar-extensions that 3066 defines.) Makes sense. -- Jarkko Hietaniemi <[EMAIL PROTECTED]> http://www.iki.fi/jhi/ "There is this special biologist word we use for 'stable'. It is 'dead'." -- Jack Cohen
