Translatability issues for Inkscape 1.2 (collection and Q&A)
I'll be going through strings that might require changes in Inkscape 1.2 to be translatable / understandable by translators. This means that I'll be having lots of questions... I'd ask them in the chat, but people may not be available, so I need a place to collect them as I go. I'm fixing those I can myself in
https://gitlab.com/Moini/inkscape/-/tree/inkscape_1.2_string_fixes and https://gitlab.com/Moini/extensions/-/tree/extension_strings_1.2 (no MR yet, because .. noise).
Steps to reproduce:
- open Inkscape po file for any language
- wonder what many strings mean...
When you have page numbers in Hebrew or Arabic, like 'page 1 of 5', would you write that 1/5 or 5/1 ? @shlomif @alezzacreative
For positional arguments in g_strdup_printf, how would that need to be used? They're both of type %d, but ... if they need to be positional for RTL languages, they'd need to be separately named. @doctormo @mc- FIXED BY inkscape!4115 (merged)
Same issue: ../share/ui/toolbar-page.ui:92
Why are /share/ui/dialog-trace.glade:852 , 807 , 702 and 747 a) texts (as they're clearly numbers) and b) translatable? @mkovFIXED
How can translator context be provided for strings in extension .py files? (/share/extensions/docinfo.py:33) @joneuhauserFIXED
Do any of the 'add_devmode_line' and 'add_devmode_groupheader' contents in ../src/ui/dialog/inkscape-preferences.cpp:2783 etc. actually need to be translatable? Looks to me like they're purely meant for development and we do not need to bother trying to explain to a translator what they mean. @pbs3141 @marcjeanmougin
more to follow later.
Inkscape master, will be updated as I go, so no use to tie to a specific version.