Fix for translation bug #372

I know it's a little complicated. But in many countries in east Europa we need separate LBL_ADD_ACCOUNT, LBL_ADD_INVOICE, LBL_ADD_SO, .... Because static merge LBL_ADD and LBL_SINLGLE_MODULE_NAME create a mistake.

Or maybe use only one LBL_ADD_RECORD or LBL_ADD_RELATED_RECORD for each related module creation. I think this need a review from community, if possible.

Interesting point. Sure, please raise it on the mailing list and let's see if we can get input for languages where the initial proposal doesn't work right.

Thanks @lord_alan, Please check the commit 6053b56c

@satish.dvnk I really don't understand what you are doing? I created this merge request. Why do you not simply use it rather than creating a new commit which is identical? Then these things will all be linked back to the issue... As it is you have to manually tag me, to tell me you have done something.

Please try and use the tools at your disposal more effectively.

And also, please note the comments from @its4you above. This fix is probably not the right thing to do for certain languages:

Because static merge LBL_ADD and LBL_SINLGLE_MODULE_NAME create a mistake.

@lord_alan, While I was working with some other issue, I came to know about this issue and at the same time I committed the change set. Later, I got to know your merge request so I changed the subject(title) of my merge request and I think it's not parallel work.

This can probably be closed I guess? Maybe @its4you has some specific cases where singular and plural translations do not work correctly for certain languages but this merge request was "sort of" copied and then merged by @satish.dvnk 11 months ago.

thanks @lord_alan - good to close the stalled ones. so it can re-opened with more details or file with respect latest trunk.

Status changed to closed