Re: [Docutils-develop] language set testing

[David G. <go...@py...>]

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

[Engelbert]
> 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 processing 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.

All I can suggest is to read the description in
http://docutils.sf.net/spec/rst/directives.html and decide on the best
word for your language.

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

If "raw" is a German word, then sure.  Otherwise, it will be available
via the fall-back language, English.

>>       'topic': 'topic',  # Inhalt, Thema or =D0berbegriff
>>
>> There can be many keys with the same value.  Two of them anyway;
>> "inhalt" is already used for "contents".  Are they homonyms?
>=20
> actually it is =B8berbegriff (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.
...
> so what is a topic: something summarizing (the title sums up the
> document as does a chapter title ...)

"Contents" is short for "table of contents".  "Topic" is a kind of
self-contained subsection, or an admonition (like the "note"
directive) with its own title.  It's not a summary.  I suspect that
"=B8berbegriff" may not be the correct translation (but what do I know).

> 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.

Don't understand.

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

Or become one ;)

> 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.

No, I think it should be an error if no directive translations are
present.

Idea (added to To Do list): the "test_language.py" module could test
all languages when run by "alltests.py", and it could accept a
language name argument if run as a script, like this::

    test_language.py de

If no argument, the default would be to test all language modules.

--=20
David Goodger  <go...@py...>  Open-source projects:
  - Python Docutils: http://docutils.sourceforge.net/
    (includes reStructuredText: http://docutils.sf.net/rst.html)
  - The Go Tools Project: http://gotools.sourceforge.net/