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
This is still a big problem eating a lot of time fixing gettext errors for "wrong" translations due to excessive whitespace padding due to well-intentioned XML formatting of sentences in help texts.
The solution is probably a bigger chunk of work and we need to retain backwards compat with the current way... maybe we only have this problem with help texts anyway.
The text was updated successfully, but these errors were encountered:
While looking into opnsense/plugins#4494, it crossed my mind that we still have this padding issue.
Although we can likely replace line endings and spaces easily, we do need a plan to make the existing translations match. Just thinking out loud, what if we generate a map of "unpadded" and new strings and replace all message id's in the .po files here, would we be able to push them back to the translation project easily? (so keep padding in translated content, remove it from all sources)
This is still a big problem eating a lot of time fixing gettext errors for "wrong" translations due to excessive whitespace padding due to well-intentioned XML formatting of sentences in help texts.
The solution is probably a bigger chunk of work and we need to retain backwards compat with the current way... maybe we only have this problem with help texts anyway.
The text was updated successfully, but these errors were encountered: