Translating talk:Mifos

From translatewiki.net
Jump to navigation Jump to search
First page
First page
Last page
Last page

Context needed.

Siebrand11:45, 8 December 2013

This refer to the action of transferring a client from one branch office to another branch office. Once a transfer is initiated from one branch, the client and his/her accounts are put in a suspended state until the receiving branch office either 1) Rejects the Transfer of the Client 2) Accepts the Transfer of the Client or 3) Undo a Transfer.

Nayan could you please confirm the difference between Reject and Undo.

Edcable (talk)00:16, 4 January 2014
 

Context needed.

Siebrand11:45, 8 December 2013

This refer to the action of transferring a client from one branch office to another branch office. Once a transfer is initiated from one branch, the client and his/her accounts are put in a suspended state until the receiving branch office either 1) Rejects the Transfer of the Client 2) Accepts the Transfer of the Client or 3) Undo a Transfer. Nayan could you please confirm the difference between Reject and Undo.

Edcable (talk)00:15, 4 January 2014
 

Context needed.

Siebrand11:45, 8 December 2013

This refer to the action of transferring a client from one branch office to another branch office.

Once a transfer is initiated from one branch, the client and his/her accounts are put in a suspended state until the receiving branch office either 1) Rejects the Transfer of the Client 2) Accepts the Transfer of the Client or 3) Undo a Transfer.

Nayan could you please confirm the difference between Reject and Undo.

Edcable (talk)00:09, 4 January 2014
 

Context needed.

Siebrand11:46, 8 December 2013

These refer to what we've previously called Administrative Documents and/or User-Generated Documents. They are basically client-facing reports which can be generated on-screen and printed by the user.

However I agree that this name is confusing and it is a brand new term that the community won't be familiar with.

Nayan - thoughts?

Edcable (talk)00:04, 4 January 2014
 

Content needed.

Siebrand11:44, 8 December 2013

Transfer client refers to transferring a client from one group of borrowers to another or transferring a client from one branch office to another branch office. Added documentation.

Edcable (talk)00:02, 4 January 2014
 

Context needed. Should be "New savings account"?

Siebrand11:44, 8 December 2013

Yes Refers to New Savings Account but it's a button in task bar so we are aiming to save space. It should read however - "New Savings"

Edcable (talk)00:01, 4 January 2014
 

Need context. Feature to group multiple accounts, or a list of accounts to which multiple have access?

Siebrand10:24, 7 December 2013

I added some documentation to this message - it is an account (savings or loan) that is held jointly by members of a group.

Edcable (talk)23:53, 3 January 2014
 

Context needed.

Siebrand11:32, 8 December 2013

Context needed.

Siebrand11:38, 8 December 2013

Looks like a patchwork message.

Siebrand17:32, 4 November 2013

In that paragraph there is need to apply different HTML markup, that is the reason it is split into patches. Is there any better approach?

Nayan (talk)04:48, 6 November 2013
 

Empty messages:

Shirayuki (talk)14:31, 12 November 2013

spec is jargon. Use "specificication"

Siebrand17:34, 4 November 2013

Done, changed to "Functional specification" from "Functional spec"

Nayan (talk)10:24, 5 November 2013
 

Context needed.

Siebrand17:39, 4 November 2013

In MFI, clients and loans are always maintained by MFI staff ( usually referred as Loan Officer or Credit Officer or Field Officer)

During client creation or loan creation a staff is assigned to client/loan, if assigning staff is a optional then in staffs name drop-down a decorated text is shown as mentioned --Select staff--,

Nayan (talk)10:15, 5 November 2013
 

Need context.

Siebrand17:35, 4 November 2013

Should be "Username"

Siebrand17:27, 4 November 2013

it is proper "label.username" : "UserName"

Nayan (talk)04:43, 6 November 2013

I've never seen this spelling before in any application. Can you please explain why this particular spelling is being used?

Siebrand14:09, 6 November 2013

Sorry this was oversight, need correction.

Nayan (talk)11:56, 9 November 2013

done

Nayan (talk)18:47, 9 November 2013
 
 
 
 

Inconsistent use of proper noun. Is it "Mifos X" or MifosX"

Siebrand17:30, 4 November 2013

"Mifos X" is the correct noun. Update the same in all the places

Nayan (talk)08:03, 6 November 2013
 

This looks like a patchwork message. Use variables to ensure that translators can make grammatically correct sentences.

Siebrand17:31, 4 November 2013

In that paragraph there is need to apply different HTML markup, that is the reason it is split into patches. Is there any better approach?

Nayan (talk)04:48, 6 November 2013
 

What does COSM mean?

Siebrand17:33, 4 November 2013

COSM = Community for Open Source Microfinance

please see http://www.openmf.org/who-we-are/our-story/ for more info.

Keithwoodlock (talk)02:17, 5 November 2013
 

COSM (Community for Open Source Microfinance) is getting renamed as "Mifos Initiative", So I changed the label "label.community.name" : "Mifos Initiative" from "label.community.name" : "COSM"

Mifos is sharter version of MIcroFinanace Open Source

Nayan (talk)10:01, 5 November 2013
 

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
 
 
 
 
 

"Miscellenous" should be "Miscelleneous".

Shirayuki (talk)12:19, 2 August 2013

Actually, it should be "Miscellaneous".

McDutchie (talk)12:54, 3 August 2013
 
First page
First page
Last page
Last page