I’m evaluating ERPNext , and the first thing I’ve checked was the invoice printing and how far we can customize it to to comply with our local tax regulations, then I found an issue , which I assumed was caused by lack of entry in the master file “ar.csv”
There are two columns wrongly translated , and the master file has no reference to those columns.
(See image )
‘Sr’ column title ( Serial Number) - which was translated to Arabic equivalent to ‘Saudi Riyal’ instead of ‘Serial number’
‘Amount’ column title (line amount) - which is translated to Arabic equivalent to ‘Quantity’ instead of ‘Amount’
I’m using the VM version and manually corrected few translations for the testing purposes.
I’ve inspected the ar.csv file , I failed to find any reference.
Please advise if I missed anything.
thanks for your post. In the meantime, have you looked at the “Custom translation” feature? This will allow you to override translations to your liking without the need to change a file. Improvements to the language files are always appreciated, there is a portal for that: https://translate.erpnext.com/
@aasaady as @lasalesi said you can contribute to the translation via the portal. Any local changes made to the csv will be wiped out when an update arrives.
There is an issue on the translation login. Its niether sending confirmation email for new sign up nor accepting existing service provider login credentials.
BUT, I’m not able to take action due to the following:
The verify buttons does not work, am I supposed to click them in order to correct a translation?
I failed to find the wrong translation that caused the printing issue. i.e. mainly the one I’ve fixed earlier by adding the below line to the master translation
The verify button is to verify the translated string.
Be careful, if one is verified then you can only change the translated field if you have more than 100 karma.
I found there are further missing texts (beyond the mentioned case above) and the same applies to them, i.e. we should copy other lines from frappe framework translation file to ERPnext master translation file.
The idea of using a “master translation file” contradicts with the current status quo, I strongly recommend only sticking to one file (the apps master) instead of two sources ( Framework translation + App Translation).
