Fix committed in the trunk, rev. 13968.
Workaround applied to the 0.91.x branch, rev. 13734.
Note that the fix required a change in the original strings, and thus backporting it is a bit complicated (we would have to update all the translations, which is something we usually don't do for bugfix releases). As a workaround, I have marked the entry that caused the crash "fuzzy" (the message is thus partially translated, but Inkscape doesn't crash anymore):
JFYI, gettext requires that % fields follow the original order (here %s must be placed after %i). If not, it causes runtime issues.
In the trunk, I have modified the code so that we now use %1$i and %2$s and no longer need to follow the original order.
Fix committed in the trunk, rev. 13968.
Workaround applied to the 0.91.x branch, rev. 13734.
Note that the fix required a change in the original strings, and thus backporting it is a bit complicated (we would have to update all the translations, which is something we usually don't do for bugfix releases). As a workaround, I have marked the entry that caused the crash "fuzzy" (the message is thus partially translated, but Inkscape doesn't crash anymore):
#: ../src/ selection- describer. cpp:215
#, c-format, fuzzy
msgid "<b>%i</b> objects selected of type %s"
msgid_plural "<b>%i</b> objects selected of types %s"
msgstr[0] "已選擇類型 %s 的 <b>%i</b> 個物件"
msgstr[1] "已選擇類型 %s 的 <b>%i</b> 個物件"
JFYI, gettext requires that % fields follow the original order (here %s must be placed after %i). If not, it causes runtime issues.
In the trunk, I have modified the code so that we now use %1$i and %2$s and no longer need to follow the original order.