[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

What autogenerated documentation to translate

From: Jean Abou Samra
Subject: What autogenerated documentation to translate
Date: Mon, 10 Jan 2022 01:47:33 +0100
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.3.1


Suppose I submitted a change allowing to translate
autogenerated documentation via PO files (likely not
this week because I already have syntax highlighting
on my plate, but this discussion can already happen now).
What should we translate?

One reason for asking is that the list of Scheme
functions (
is quite large (693 docstrings, as many as context
properties and grob properties together) and all very
technical, so I don't know if is a good idea to translate

More precisely, for which of the following should
translation support be added?

- Markup and markup list function docstrings

- Music function docstrings

- Type predicates

- All the stuff in the first three parts of the
  Internals Reference: Music definitions, Translation,
  Backend (including property docstrings,
  music expression & context & engraver & grob interface
  docstrings, etc.)

- The list of Scheme functions.

Thoughts on the matter would be welcome, especially
from translators.

A semi-related question for Jean-Charles in particular: directs
me to, but
the mailing list link is a 404. How does this work?


reply via email to

[Prev in Thread] Current Thread [Next in Thread]