Jump to content

About [[Mifos:Pd-errors.mandatoryconfig/en]]

How does one expect this can be translated?

Siebrand11:17, 27 March 2013

It should stay as it is. Numbers in curly bracket are just variables, that we put special strings (depend on situation). User will not see {0} {1} {2}, just a dedicated text.

Nszprega (talk)15:16, 15 July 2013

Yes, we know what variables are in strings. What we are addressing here is that patchwork messages are a bad practice, and make for poorly localisable products. See for example the MediaWiki documentation on this subject.

I welcomed you in another thread, and apologies, as I do not know who you are or what your background is. If you are a developer, please understand that saying "this needs to stay as it is" is probably not a productive answer, as you're not doing two things:

  1. Explain what 0, 1 and 2 can be here
  2. Try to understand why using 0, 1 and 2 here may be problematic when trying to translate the Mifos product into other languages.

I'd be happy to elaborate on #2, if you're willing to answer the first question. Thanks.

Siebrand22:28, 15 July 2013

Excuse me, I did not understood your question well.

Hope this answer will be more clear: {0} is min/max/defaultString under where we put: "Min" "Max" "Default" {1} is label, where we put text: "Interest" {2} is prdrate, where we put: "rate"

Is this what you have expected?

Nszprega (talk)11:18, 17 July 2013

Yes. That's the answer I was looking for.

If you look at how that "sentence" (or in this case really string) is constructed in the UI, could you agree that this may lead to big problems with localisation?

The options we have here are:

  • Please specify the Min Interest rate.
  • Please specify the Max Interest rate.
  • Please specify the Default Interest rate.

Would it be possible to simply have 3 strings, without any variables in them? That would completely fix the i18n issues in this case.

Siebrand13:34, 30 July 2013

It would indeed be possible, so I created a ticket for this issue.

You can track the progress under this url: https://mifosforge.jira.com/browse/MIFOS-6102.

LechRozanski (talk)09:44, 19 August 2013
 

The ticket has been finished and the functionality will be available in the next (2.6.3) Mifos release.

LechRozanski (talk)08:09, 23 September 2013

Thanks.

Siebrand16:15, 26 September 2013