Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

find a solution for excessive padding in XML formatted messages #68

Open
fichtner opened this issue Dec 15, 2023 · 1 comment
Open

find a solution for excessive padding in XML formatted messages #68

fichtner opened this issue Dec 15, 2023 · 1 comment
Assignees

Comments

@fichtner
Copy link
Member

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.

@AdSchellevis
Copy link
Member

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)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

No branches or pull requests

2 participants