Re: [Docutils-develop] language set testing

[<gr...@us...>]

On Wed, 6 Nov 2002, David Goodger wrote:

> gr...@us... wrote:
> > and maybe this should be more visible to translators not only
> > a unittest, and could give warnings (verbose mode).
>
> What do you mean?

anyone doing a translation should start all_test, but at least
test_language.

> BTW, de.py needs translations of the "raw", "include", and "replace"
> directives.  Could you please?

i put the in as comments, dont know a proper word yet, would be a sentence.
but saying "include" in a document is not document content, but a processin=
g
command, the document would say "here the contents of xxx would be inserted=
"
or "see xxxx for details" but not "include". for me these are two
different audiences.

should we support both 'raw' and 'unbearbeitet'.

>
> There's a comment::

i like to comment, so i donot have to fetch TFM to know what i
thought last time.

>
>       'topic': 'topic',  # Inhalt, Thema or =DCberbegriff
>
> There can be many keys with the same value.  Two of them anyway;
> "inhalt" is already used for "contents".  Are they homonyms?

actually it is =FCberbegriff (a summarizing (herding) concept ?)
but this does not mean that this is the exact usage in document
processing. e.g. contents is something different for a book writer
an e-business monkey or a grocery worker.

inside the writer many things come as a topic and the writer has to
decide when it is a title, that is why topic_class is there.
so what is a topic: something summarizing (the title sums up the
document as does a chapter title ...)

but for me topic is also usable in german conversation.

i have to see in i18n to get the =FC right.

>
> Another::
>
>       'bild': 'image',
>       'figure': 'figure', # also Bild ?
>
> You can't use "bild" twice, but surely there's an appropriate word in
> German?  Something like "titled-image" (translated) may suffice.  The
> English "image" just means "picture", whereas "figure" has a larger
> meaning, like "diagram/illustration/explanation".

changed to "abbildung"

>
> I know no German, so I have to trust you as a native speaker to do
> your best.  Just don't translate "contents" as "my hovercraft is full
> of eels".  (Monty Python reference)

i am more in programming so thinking half english, as i understand
these are domain specific translations, so xp says get a domain expert.

> >> In programming languages, most people seem to be happy with
> >> English-based syntax.  AppleScript had language dialects, but I
> >> don't think it caught on (code in Japanese looked *very* strange to
> >> my eyes, but I'm biased).  Directives are similar to programming
> >> language keywords/statements/commands, but not the same.  What do
> >> people think?
> >
> > reST is no programming language,
>
> I agree.
>
> > i thought the text should be a valid document (as far as possible)
> > otherwise we might need a text-writer.
>
> Don't know what you mean by "we might need a text-writer".

if rest would be a programming language, like latex, or postscript
we might need a docutils/writers/text.py module.

>
> > and the test of course must know if it is required or optional.
>
> I think a test should fail if any aspect of a language isn't there.

yes, so your intention is "directives translation is optional"
so it is not an error if none is present, but if they are there
we test them.

>
> >> Another question, from the to-do list: Should we use the language
> >> module for directive option names?  In other words, should
> >> directive option names be translated?
>
> How about this one?  Right now in English we would write::
>
>     .. contents:: :local:
>
> In German, "contents" is translated, but "local" is not::
>
>     .. inhalt:: :local:
>
> So should directive options be translated too?

i had no need for directives up to know do not ask me about
directives options :-)

--=20
 BINGO: Lassen Sie sich was einfallen!
 --- Engelbert Gruber -------+
 SSG Fintl,Gruber,Lassnig   /
 A6410 Telfs Untermarkt 9  /
 Tel. ++43-5262-64727 ----+