~mil/sxmo-tickets#247: 
localization support

Not all sxmo users want to use an english interface! Im unsure how we would solve this issue though. Should we use a profile file for various translations? Or maybe we can do translations in compile time?

Status
REPORTED
Submitter
~anjan
Assigned to
No-one
Submitted
1 year, 2 months ago
Updated
4 months ago
Labels
feature

~proycon 1 year, 2 months ago

On 21-04-24 05:41, ~anjan wrote:

Not all sxmo users want to use an english interface! Im unsure how we would solve this issue though. Should we use a profile file for various translations? Or maybe we can do translations in compile time?

I thought about this too the other day. In principle I support localization, but it does add a layer of complexity that I'd like to keep as minimal as possible. We have mostly shell scripts (that should remain easily human readable) and a small number of C programs. We'll need to investigate what the simplest way is , whilst adhering also to sensible standards probably like working based on locale settings and using *.po files possibly. I don't know what a decent solution for POSIX shell scripts is yet.

--

Maarten van Gompel (proycon) https://proycon.anaproy.nl

~proycon 1 year, 1 month ago

It looks like GNU gettext may be the most standard option applicable for shellscripts as well: https://www.gnu.org/software/gettext/manual/gettext.html#sh

~proycon closed duplicate ticket #298 a year ago

~lisael 4 months ago

I agree it's important. I'd like to work on a patch with a gettext PoC on an arbitrary menu to give a feeling of what it's like working with localized strings and dates in sxmo shell scripts.

If (or when..) we start with i18n/l10n, the hardest part is to document the localization process and to attract contributions.

~proycon 4 months ago

On 22-02-09 12:05, ~lisael wrote:

I agree it's important. I'd like to work on a patch with a gettext PoC on an arbitrary menu to give a feeling of what it's like working with localized strings and dates in sxmo shell scripts.

If (or when..) we start with i18n/l10n, the hardest part is to document the localization process and to attract contributions.

You're most welcome to give it a try yes!

~proycon referenced this from #473 4 months ago

Register here or Log in to comment, or comment via email.