-
-
Notifications
You must be signed in to change notification settings - Fork 4.5k
gettext: refresh page #16555
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
gettext: refresh page #16555
Conversation
Updating gettext to include disambiguation options
Updating to correct TLDR005
Updating to reorder help to the last entry and to note the parsing for space-separated format
Co-authored-by: Managor <[email protected]>
Co-authored-by: Managor <[email protected]>
Adding more clear explanation of what this is doing
Co-authored-by: Managor <[email protected]>
Including clarity on file structure
For anyone reading this thread in the future, this command has a bit of complexity in terms of where it's looking for the localisation content, and people often get hung up on the file structure. If you have a localised file, you must ensure it lives in the following directory structure:
This file is made using the msgfmt tool to convert from a .po to an .mo. Note that it's not good enough to just have it in the director - it needs to be in a subdirectory of LC_MESSAGES for gettext to be able to find it. GNU C does this because there's other variables at play, like LC_TIME for date/time formatting and LC_MONETARY for currency. LC_MESSAGES is specifically for software message strings. If you're running into localisation issues with gettext, make sure you're in the right directory! A common error is to locate the file like this:
To correct this, just use the move command:
E.g.:
|
Clarifying the domain functionality
Removing --context as this is dependent on an update in the core tool, and clarifying that --domain is a requirement. Reworking summary.
Co-authored-by: Managor <[email protected]>
Co-authored-by: Managor <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Once you apply these, please voice your opinion on what information is missing from the page. I want you to push back when you think my opinion is wrong.
Co-authored-by: Managor <[email protected]>
Co-authored-by: Managor <[email protected]>
The only thing I think that's missing here that wouldn't be more confusing to include (thinking --context here) would be:
I'll include in the .md |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This feels like it's complete now. Let me know if there's any information that you feel is missing.
Adding in trailing newline suppression and version check.
Co-authored-by: Managor <[email protected]>
Co-authored-by: Managor <[email protected]>
Ok, I think this is complete now! |
Clarifying the use of the -n flag.
Spelling
@KristopherLeads send a new PR when you have the time to expand this page. |
Updating gettext to include disambiguation options
common
,linux
,osx
,windows
,sunos
,android
, etc.