References: <l03102800b301c74fc00f@[130.239.20.144]>
            <199902281535.QAA14126@mozart.ujf-grenoble.fr>
            <199903021825.TAA13628@mozart.ujf-grenoble.fr>
            <l03102800b302fc0e2d09@[130.239.20.144]>
Mime-Version: 1.0 (generated by tm-edit 7.106)
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
Message-ID:  <199903041417.PAA17441@mozart.ujf-grenoble.fr>
Reply-To: Mailing list for the LaTeX3 project
              <LATEX-L@URZ.UNI-HEIDELBERG.DE>
In-Reply-To:  <l03102800b302fc0e2d09@[130.239.20.144]>
Date:         Thu, 4 Mar 1999 15:17:49 +0100
From: Thierry Bouche <Thierry.Bouche@UJF-GRENOBLE.FR>
Sender: Mailing list for the LaTeX3 project
              <LATEX-L@URZ.UNI-HEIDELBERG.DE>
To: Multiple recipients of list LATEX-L
              <LATEX-L@URZ.UNI-HEIDELBERG.DE>
Subject:      Re: Axis in nfss
Status: R

ť >but its use
ť >may be completely determined by proper markup (end of sentence, proper
ť >noun, even in german, you'd identify substantives, etc.)

ť I see what you mean, but you're unfortunately wrong.

Ahah !

ť It is not in general
ť possible to determine whether a word is a proper noun or not if it appears
ť in a monocase environment, since quite a lots of proper nouns have once
ť been nonproper nouns.

That's why I said _markup_: you don't hear caps when you speak a
natural language, so that is not needed. Now the uc/sc/lc  glyphs used
on print (should) follow rather simple rules that are dictated by
their nature, which could be specified by some markup, precisely as
you'd prefer \vector{v} to have v rendered in whatever specific style
you like for vectors. Something like natbib's \citeauthor could produce c&sc,
\Name c&lc, etc.

ť Not that I think the subject is of much relevance, though.

you said it!

\Fistname{thierry} \Name{Bouche}, \Town{grenoble}.