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

corrupted escape characters #66

Open
bryghtlabs-richard opened this issue Sep 13, 2024 · 0 comments · May be fixed by #68
Open

corrupted escape characters #66

bryghtlabs-richard opened this issue Sep 13, 2024 · 0 comments · May be fixed by #68

Comments

@bryghtlabs-richard
Copy link
Contributor

If I place _("Preparing\nUpdate") in my code, lv_i18n extract works, and I'll add the German translation:

en:
  Preparing\nUpdate: ~
de:
  Preparing\nUpdate: ~: Update\nvorbereiten

But it seems lv_i18n compile is over-escaping, and produces the following German table:

static lv_i18n_phrase_t de_singulars[] = {
    {"Preparing\\nUpdate", "Update\\nvorbereiten"},
    {NULL, NULL} // End mark
};

Which encodes to:

Preparing\nUpdate

Instead of the expected:

Preparing
Update

This breaks translations, as lv_i18n_get_text() is expecting an over-escaped version of the input, but passed the original input.

bryghtlabs-richard added a commit to bryghtlabs-richard/lv_i18n that referenced this issue Sep 16, 2024
@bryghtlabs-richard bryghtlabs-richard linked a pull request Sep 16, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant