Translation

[shut falcon]

Mostly for the docs, but possibly for other things.

Linking this message: #contributors message

re #contributors message @pallid oriole As said above, there are no plans to change how the API docs are written. And the change of the prose docs from MD to Typst is relatively minor.

[pallid oriole]

define "the prose docs"

[shut falcon]

The files that live in docs/ in the repo

Basically the tutorial, guides and the Styling, Scripting & Syntax pages

But not the docs for all the functions, elements, etc.

[pallid oriole]

and why they are called "prose docs"?

never heard that before

[pallid oriole]

so about that. will we have a translation for the API docs? because if there are no plans in changing how these docs are written, this kinda implies that either the method of translating/making translation is different from non-api docs, or there will be no translations for the api docs.

[shut falcon]

I am calling them that because they are longer form, like prose.

[pallid oriole]

mmm, ok

[shut falcon]

see my linked message, specifically

The typical solution for translations is not to literally rewrite the documentation in every language, trying to keep the structure in sync. Rather, one localization is the primary one (English in our case) and the other translations are kept in a separate sentence-by-sentence translation database (e.g. https://weblate.org/). This is also robust against movements.

So all of the docs would be translated in the same way

[pallid oriole]

if some sentences are linked with words, then this can be difficult to translate, I think.

[shut falcon]

I am not an expert on this, so some more research might be necessary, but I think this is the industry-standard solution.

Maybe the granularity can be adapted on a case-by-case basis.

[pallid oriole]

me neither (btw)

[warm flicker]

I see a few PRs were made recently to translate what I assume is the three new keywords of upcoming accessibility. Is this to be manually translated? If so, I only found how the email/telephone are used in the tooltip, but not the footnote. Still, I'm not even sure why the telephone is translated as Telephone and not as Phone number, is there a way to check this, because I assume it's the same thing in most languages and it would be unfortunate if we ended up mixing them up?

I'm also wondering where the change from https://github.com/typst/typst/commit/717ba1a8eddff9841a8e2af6bd7d634705b22146 is reflected, because I noticed that for example page was uppercase before, but in 0.13.1, I see it in lowercase when created with ref(form: "page") so I guess I'm looking at the wrong spot.

[shut falcon]

The page thing was changed in the commit right before

[shut falcon]

Regarding "Telephone" vs "Phone number", we just discussed this internally. We've opted for "Telephone" and "Email" because this neutrally describes the kind of link (tel:, email) and seems sufficiently clear.