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

CRLF-based verbatim string literals are not translated. #41

Open
air-hand opened this issue Mar 25, 2022 · 0 comments · May be fixed by #42
Open

CRLF-based verbatim string literals are not translated. #41

air-hand opened this issue Mar 25, 2022 · 0 comments · May be fixed by #42

Comments

@air-hand
Copy link

Hello.

I use NGettext with gettext on Windows.

In my project, all source codes are CRLF-based.

but, the verbatim literals like below are not translated.

// in CRLF-based source code.

var translated = _("foo bar baz");

var not_traslated = _(@"
foo
bar
baz
");

The gettext tools understand only LF (without CR) I think, so built *.po and *.mo files include only LF even though with CRLF-based source codes.
and, I found this has happened because NGettext doesn't ignore CRLF and LF differences.

I know I can change all of my code to LF-based, but it may be forgotten in the future because CRLF is the default on Windows.

so, I want NGettext to ignore the differences between CRLF and LF.

Thanks.

@air-hand air-hand linked a pull request Apr 29, 2022 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