[Tuxpaint-i18n] Localized names of file paths?
An award-winning drawing program for children of all ages
Brought to you by:
wkendrick
From: Bill K. <nb...@so...> - 2024-04-27 18:30:48
|
I'm doing a little bit of work over in the `tuxpaint-docs` repo (the PHP + gettext source of the HTML docs that are then sync'd over to the main `tuxpaint` repo, to be part of a release) to modularize how filenames and paths are managed. That is, rather than every time I want to mention the file "/home/tuxpaint/.tuxpaintrc" (the user-level configuration file for Tux Paint, on Linux/Unix) -- which sometimes I might instead describe as "~/.tuxpaintrc" or "$HOME/.tuxpaintrc", I'll instead use a little bit of PHP that will grab a string that will be consistent across all of the documentation. (e.g., "<?= $PATHS["linux"]["config"]["user"] ?>"). To that end, it seems that some operating systems provide localized versions of their rather descriptive paths, e.g. on Windows there's "Program Files", and "Application Data". (And for example, it looks like the latter is actually named "Anwendungsdaten" (German), "Dati applicazioni" (Italian), "Datos de programa" (Spanish), & "Dane aplikacji", per a random Stackoverflow question I just landed on[*]. I haven't figured it out yet, but does macOS or other OSes do this (e.g., macOS has folders named "Library", "Application Support", "Users", etc. -- do they have different names under different locales?) Basically, I want to make sure we do some amount of reasonable localizing in the documentation, without going wild (and without being inaccurate; e.g., if it's _always_ "Application Support", even on a German Mac, there's no reason to _mis_-label it with a localized string, in our docs). Thanks in advance for whatever you can share, [*] https://stackoverflow.com/questions/4899985/windows-documents-and-settings-in-another-languages -- -bill! Sent from my computer |