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

L10N - string we should or should not have #18

Closed
Jibec opened this issue Oct 3, 2016 · 3 comments
Closed

L10N - string we should or should not have #18

Jibec opened this issue Oct 3, 2016 · 3 comments

Comments

@Jibec
Copy link

Jibec commented Oct 3, 2016

Hi,

We probably do not need to translate:

We probably need to translate

thanks a lot for your help

@Jibec Jibec changed the title L10N - string we should not have L10N - string we should or should not have Oct 3, 2016
@MartinBriza
Copy link
Collaborator

Hello, thanks for the report!
Just one question, should we translate the "KB", "MB", etc. too? Or do I need to keep just the word order in mind?

@Jibec
Copy link
Author

Jibec commented Oct 4, 2016

Yes, we should translate it too !
Le 3 oct. 2016 12:50, "Martin Bříza" notifications@github.com a écrit :

Hello, thanks for the report!
Just one question, should we translate the "KB", "MB", etc. too? Or do I
need to keep just the word order in mind?


You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
#18 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAc_AyS2eyESqJhdOAEmFymaMUyT4yZoks5qwN3tgaJpZM4KMQAI
.

@MartinBriza
Copy link
Collaborator

Ok, thanks, I'm just working on it.
The string from the desktop file will be a bit of a problem because xgettext just keeps on extracting it for some reason. I'll probably just grep it out to be safe...

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

No branches or pull requests

2 participants