My Community

Work At Home Free Classifieds => Post Your Products & Services Here => Topic started by: magebaytn on September 22, 2016, 04:45:01 AM

Title: Editing Magento Translate.csv File
Post by: magebaytn on September 22, 2016, 04:45:01 AM

There's a technique to edit translation CSVs utilizing one file – translate.csv. So as to do that, you just have to set locale through Magento admin space, then create translate.csv in

app/design/frontend/<bundle>//locale/languagecode_COUNTRYCODE and put your translated strings inside this translate.csv file.
View extra : https://www.magebay.com/magento-multi-vendor-marketplace-extension (https://www.magebay.com/magento-multi-vendor-marketplace-extension) - https://www.magebay.com/magento-2-extensions (https://www.magebay.com/magento-2-extensions) - http://productsdesignercanvas.com/ (http://productsdesignercanvas.com/)
Listed below are some suggestions and tricks:

• All strings should start and end with double quotes and ought to be separated with comma (,), not a semicolon or some other sign

[list=1]
   

• “Default line”,“Translated line”

• It may be very handy to alternate the default theme strings with the help ofapp/design/frontend/<package>//locale/en_US/translate.csv file
  

For example:
[list=1]
   

• “My Cart”,“My Basket”
• “My Account”,“Your Account”

• All of the traces are case-sensitive and the first message have to be copied exactly as it appears within the default en_US version.

For instance, if in en_US locale the string seems to be like that
[list=1]
   

• “%s Item(s)”,“%s Merchandise(s)”

But in your translate.csv you'll strive
[list=1]
   

• “%s Items”,“%s Product(s)”

It simply wouldn’t work, so watch out with that.

• Some strings can include %1$s %s %d and so forth., and if you wish to have the right strings in your translations these entries ought to be also kept in the translated string

[list=1]
   

• “%s Merchandise(s)”,“%s Product(s)”

• Your textual content editor should have the ability to save an edited CSV file in UTF-8 encoding (), particularly when you translate using different alphabets. You probably have your translations in Excel, that you must convert your file to UTF-eight (discover more data on how to convert Excel to CSV with UTF-8 encoding StackOverflow).
• If you must have double quotes in your string they need to be escaped through the use of two double quotes

[list=1]
   

• “String”,” “” – this is how double quotation mark seems to be like”
• “Warning!”,“<sturdy model=””color:pink””>Attention!strong>”

• There are some strings that can be presented in just a few extensions concurrently. For example, in “Add To Cart” strings could be present in both Mage_Catalog.csv and Mage_Checkout.csv. What if you need to translate/change them in another way? Regular means can be to edit .phtml recordsdata manually, but with translate.csv you may solve this issue more elegantly – just put your extension identify as a prefix and it is possible for you to to translate them separately.

[list=1]
   

• “Mage_Catalog::Add to Cart”,“Add to Basket”
• “Mage_Checkout::Add to Cart”,“Add to my procuring cart”

• Last however not least – bear in mind to refresh all caches after any adjustments of your translate.csv file!