> Question. How is this handled in different locales? Will the types be in the > English placement, or in the localized one?
It will be the localized one. > By removing the "source file" suffix you avoided most of the trouble this > could cause (e.g. in Spanish nearly all languages are called "Archivo de > fuente `<type>`" or "Archivo `<type>`", and they'd all be filed under A) Even if the prefix/suffix stayed there, it would be grouped by `<type>`. > but there are still a few localized names (e.g. "Cascading Stylesheet" = > "Hoja de estilo en cascada"). Probably the most reasonable approach is to not > translate the names, and to use "short names" (e.g. "CSS" rather than > "Cascading Stylesheet") in all locales. Yes, I was thinking about this too. The following language names are translatable now: - Shell (possibly keep untranslated) - Makefile (possibly keep untranslated) - Cascading Stylesheet (could become CSS) - Config (could become Ini/conf) - Gettext translation (???) So it means these could appear under different letters depending on the used locale. And as you said, at least for CSS, it would be better to use "CSS" (not sure how common it's to translate Shell or Makefile). -- Reply to this email directly or view it on GitHub: https://github.com/geany/geany/pull/3977#issuecomment-2481384893 You are receiving this because you are subscribed to this thread. Message ID: <geany/geany/pull/3977/[email protected]>
