hi, Am Sonntag, 11. Oktober 2015, 12:48:10 schrieb Thomas Friedrichsmeier: > the .pot files would not be affected (not in a meaningful way, that is), > unless fixes concern elements that are directly related to i18n, e.g. > typos in "label" or "i18n_context".
ok, good. my only concern is that we can't know what might need to be changed as long as we didn't examine the plugins. > Yes, since Alfredo can't start, immediately, we have some time to > experiment. However, I'd suggest, we _first_ import everything into > rkward-community/external-plugins, and split up into separate chunks / > pluginmaps as specified by Alfredo (thanks!). yes, agreed. > Once that is sorted out, I think it will also make sense to contact the > KDE Spanish team. Perhaps they can help us, get started, too. If so, > we'll have to discuss a good workflow. Perhaps it really does not > matter, whether we do the translating before or after going to > rkwarddev. i can prepare an rkwarddev script with only a couple of dialogs so we have something to look at to decide. > @Alfredo, what exactly is the state of things that we should > import? rkTeaching_es is the one, rkTeaching is currently outdated. > There are also some copies of "official" RKWard plugins, e.g. plot_options. > Do these contain modifications other than translation to Spanish? I.e. would > we keep these in rkTeaching, would we try to merge enhancements into RKWard, > or would they be obsolete as soon as the corresponding "official" plugins > have a Spanish translation? good point, i also thought some files in the embed directory looked familiar ;-) viele grüße :: m.eik -- dipl. psych. meik michalke institut f"ur experimentelle psychologie abt. f"ur diagnostik und differentielle psychologie heinrich-heine-universit"at d-40204 d"usseldorf
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ rkward-devel mailing list [email protected] https://mail.kde.org/mailman/listinfo/rkward-devel
