On Thu, 05 Feb 2015 19:47:09 +0100 Albert Astals Cid <[email protected]> wrote: > El Dijous, 5 de febrer de 2015, a les 08:40:50, Thomas > Friedrichsmeier va escriure: > > Would it be enough, if I wrap all non-translatable terms in <i></i> > > (x, parameters, rk.header() are the ones missing)? > > > > Or do you need more than that / do you have a better idea? > > I don't understand, what do you guys mean with this strings being > untranslatable?
Hi, what I meant / thought was the problem, was that the string contains some terms that are function / variable names and should be kept as is in any translation. Not all of those were marked up, and at least for the term "parameters" (in this case the name of a function argument) that's clearly problematic. Anyway, the translator (Jaap) got back to me, and as far as I understand, the key issues he sees are something different: - these translation units are too large (at least one is much larger than the example, I cited, too). - they contain too much markup (as a reminder, these are HTML-formatted lists). Well, I can see those points. As you will have noted, these strings are rather atypical for us, and that's why I did not worry about this, so far. I can basically offer two possible solutions: 1. Split up the translation units "manually" (in the source, of course). 2. Automatically extract each bullet point in any list as a separate translation unit. 1) Would have the advantage(?) of allowing to keep short lists in one unit, while 2) would have the advantage of requiring less thought from the developer, and also stripping most markup. What do you think? Regards Thomas
signature.asc
Description: PGP signature
_______________________________________________ rkward-devel mailing list [email protected] https://mail.kde.org/mailman/listinfo/rkward-devel
