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
{{ message }}
This repository has been archived by the owner on Mar 15, 2023. It is now read-only.
I have a few translation keys that have trailing whitespace on purpose. However, after editing my existing translation files with i18n, all the trailing whitespace is gone. Even worse, I can't add it again, since adding trailing whitespace won't toggle the save button (so I can't save the project), and even if I make some other changes and save afterwards, the whitespace is stripped again.
i18n-edit has really made my life a lot simpler managing my local translation files for my project. Thanks a lot for this great work, this is very valuable! Translating by hand using just a text editor would have been very tedious, since I'd have to manually check which translation keys are already present in the other file and which aren't. Thanks a lot for that! It would be nice, if this whitespace issue could get fixed, though :)
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I have a few translation keys that have trailing whitespace on purpose. However, after editing my existing translation files with i18n, all the trailing whitespace is gone. Even worse, I can't add it again, since adding trailing whitespace won't toggle the save button (so I can't save the project), and even if I make some other changes and save afterwards, the whitespace is stripped again.
i18n-edit has really made my life a lot simpler managing my local translation files for my project. Thanks a lot for this great work, this is very valuable! Translating by hand using just a text editor would have been very tedious, since I'd have to manually check which translation keys are already present in the other file and which aren't. Thanks a lot for that! It would be nice, if this whitespace issue could get fixed, though :)
The text was updated successfully, but these errors were encountered: