Question translation problems

Hi all,

I'm trying to translate this excellent module into Japanese. because some words do not have the meaning only by it, I am embarrassed of the translation of this.
Moreover, if only the word is translated because the order of the word changes into some grammars, it becomes strange Japanese.

If you can change these words, please do it.

DEFINE('_PROFILEBOX_PLEASE', 'Please');
DEFINE('_PROFILEBOX_OR', 'or');

Please %s or %s

DEFINE('_KUNENA_ADDMOD', 'Add Moderator to');

Add Moderator to %s

In addition, a necessary word of such a change might exist because I am still translating.

Thanks,

I am glad somebody else brought this up as well.

Many software projects, including Kunena (just think of the many times mentioned horrible "ago" message age implementation), sadly do not pay enough attention to i18n of their code, mostly going for what is easiest to code up by the developers without any or very little thought about their international user base.

I would once again urge Kunena to switch to gettext based i18n - this at least gives code context in po files which makes it easier for translators to submit patches to the code, not to mention other benefits, such as plural forms, easier maintainability between versions, etc.

I hioe i18n will be areality on the future, but right now is not one of our priorities, we are comited to the interest of the community, so the most desired things in uservoice, are first to be served, so make campaign for it

johnnydement wrote:

I hioe i18n will be areality on the future, but right now is not one of our priorities, we are comited to the interest of the community, so the most desired things in uservoice, are first to be served, so make campaign for it

Oh, you know know I already did

kunena.uservoice.com/pages/11439-kunena/...-based-i18n-and-l10n

yes, but it needs some more visibility most people doesn't know what that are, or don't care a bit as don't need...

johnnydement wrote:

most people doesn't know what that are, or don't care a bit as don't need...

That's why it doesn't make too much sense to be on uservoice. It's not a nice-to-have feature. i18n is a basic functionality of any modern piece of software.

Anyway, here's a nifty idea to think about for the future, don't know how possible it is:

If you're thinking about going to stupid INI files for 1.6 and Joomla's own JText translation methods, you could somehow alias JText::_() to just _() so if and when you do switch to gettext you have to change very few lines of code.