You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It seems that in the .pot-file every line break from the source lean file is encoded with '\n'.
Is this a bug or a feature?
I'm asking because this tends to confuse DeepL, at least when queried with Poedit Pro. For example:
revert h kann nützlich sein um eine Annahme als Implikationsprämisse zu schreiben bevor man\n contrapose verwendet.
becomes
revert h can be useful to write an assumption as an implication premise before using\n
using contrapose.
Note that using appears twice in the translation.
My impression from a cursory look at the gettext documentation is that lots of '\n's in the pot file is the expected behaviour. If that is true, then it is something to keep in mind when writing and formatting text in lean files that is meant for translation.
The text was updated successfully, but these errors were encountered:
If this is intended behaviour, it would be helpful to change all line breaks in natural language in the lean files so that they occur at the end of sentences. Or at least, to only break lines at the end of sentences in any new story text that we add.
It seems that in the .pot-file every line break from the source lean file is encoded with '\n'.
Is this a bug or a feature?
I'm asking because this tends to confuse DeepL, at least when queried with Poedit Pro. For example:
becomes
Note that
using
appears twice in the translation.My impression from a cursory look at the gettext documentation is that lots of '\n's in the pot file is the expected behaviour. If that is true, then it is something to keep in mind when writing and formatting text in lean files that is meant for translation.
The text was updated successfully, but these errors were encountered: