In this case, there is another problem: not knowing what word will be following means that I don't know what verb to use for the translation of "to be" to Spanish, as we have two different verbs with different meaning (it is one of the difficulties English speakers have when learning Spanish):
msgstr "El repositorio será %s."
or
msgstr "El repositorio estará %s."
I need to see an example of the complete sentence. My guess is it would be enabled/disabled, but I do not know. In fact, we would also need to see the related set of words that would fill the "%s" connected somehow, so that we could translate the group of sentences/words in a consistent manner. But this is something the gettext format does not support, as far as I know.
Therefore, possibly the best solution is not to have incomplete sentences, but neither "%s to be filled" sentences. We would need 2, 4, or 20 different and distinct msgids, one for each combination that the programmer is going to use. :-( That's exactly the sentences that made me to start the discussion about i18n rules for developers. Cause it is impossible to translate
2010/4/16 Carlos E. R. <carlos.e.r@opensuse.org>: those lines in russian, since the form of the word standing for %s depends on a gender of forthcoming noun: repository is male, autorefresh is of middle gender, option is female (or male or middle depending on context)? that gives three different forms for enabled\disabled word in russian. We definitely need to formalize some of the rules so we can point developers on it. -- Regards, Minton. -- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-translation+help@opensuse.org