Fixes issue #691 #701
No reviewers
Labels
No Label
bug
build
dependencies
developers
documentation
duplicate
enhancement
formatting
invalid
legal
mobile
obsolete
packaging
performance
protocol
question
refactoring
regression
security
test
translation
usability
wontfix
No Milestone
No project
No Assignees
1 Participants
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: Bitmessage/PyBitmessage-2024-12-19#701
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "Issue-#691"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
This fixes the encoding issues around datetime formatting. It introduces a new module l10n that aims to make localization a little easier. If the language and/or encoding can not be determined it defaults to en_US and ISO8859-1. The use of ISO8859-1 prevents decoding errors, but may result in foreign or wrong characters being displayed when locale formatting options are used.
At the moment it offers formatTimestamp and getTranslationLanguage functions:
formatTimestamp returns the provided timestamp (or current time if ommitted or the wrong type) as unicode (default) or raw bytestring.
getTranslationLanguage simply returns the users language. It is the result of refactoring the QtTranslator initialization for the Qt GUI.
Resolves #691
Thank you bmng. This is quite a complex one!
bmng, A user has reported a problem with this pull request:
https://pay.reddit.com/r/bitmessage/comments/2cttc4/new_bitmessage_version_v043/cjjf28f