That is how such english words are spelled in German, they end with `t` (which I didnt know back then when I translated).
And wrap it in an abbr which explains the meaning.
Also added rule to prompt.
I thought it is okay, meanwhile, in German when there is no space inbetween, (which is why i did not fix these changes before) but this is actually not the case. In English both spellings are okay.
Has one change in the English document. If we leave those backticks, the LLM should by definition not translate it, but we want this here.
... made while re-reading the diff until inclusive docs/de/docs/deployment/cloud.md
One change is an addition of a sentence in an English dokument.
Two word additions to the German prompt
* (Hopefully) improve rule when not to convert to typographic quotation marks, re-add some examples
* Refine rule how to translate abbr elements
* Include and remove some words
Starting with this commit and in the remaining two folders, I translate the documents in the order they appear in the documentation. Should have done that from the beginning, as it helps the LLM learning things (I guess).
This commit started as an attempt to handle translation of abbr elements, which I was not able to get to work in a clean way. Shortly before I resigned I had the idea to try `openai:gpt-5` as agent in the translate.py, instead of `openai:gpt-4o` and BAM it worked. A lot of other things also worked much better. Modifications had to be made though because GPT-5 interpreted some rules stricter, so some reformulation and some more examples were needed. Will translate with that agent in the remaining translations to test if these prompts work well.
The LLM wrote `Pfadparameter`, which is not bad, but let's use or not use a dash unison for all FastAPI specific path operation parameters. As the translation so far used one, I now defined it to be so.
There are some instances of using `<code>...</code>` instead of backticks in the English document, which I fixed on the way, as it will not require a retranslation of other languages.
Removes one level of Use–mention distinction [1] by writing the examples in separate paragraphs, instead of wrapping them in backticks. This because the LLM still seems to ignore the rules sometimes, here it ignored the rule to translate the content of title attribute of abbr elements.
[1]: https://en.wikipedia.org/wiki/Use%E2%80%93mention_distinction
Before it seemingly randomly applied them, indicating that it has not understood them the way they were formulated.
Change two related things in two translations.
Remove the part to not translate link targets, as this may interfere with the more precise rulings in the general prompt.
Nils Lindemann