search

amanwas / magento-w2p

Automatically exported from code.google.com/p/magento-w2p
0 stars 0 forks source link

Localization #132

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
We need to take all the labels and texts into a separate file. It will be
easier to translate and maintain the translation with updates. 

Is there a standard way how Magento does it?
If not, we need 2 files. 

1. English, default
2. Local language

Both files are loaded and cached. If the local language file is absent it
uses Eng. If a particular key-value pair is missing from the local file M.
takes it from the Eng file.

All phrases need to be re-worded so that they are not broken up.
E.g.: Click on [this link] to win $17.95 now.
Should be: Win $17.95 now: [click here]

Basically, it needs to be either at the beginning or at the end.

Original issue reported on code.google.com by zetapri...@gmail.com on 15 Feb 2010 at 8:41

GoogleCodeExporter commented 9 years ago 
The way it's done in magento: http://nuzil.blogspot.com/2009/09/magento.html

Original comment by k.safro...@gmail.com on 5 Mar 2010 at 5:33

GoogleCodeExporter commented 9 years ago 
r588 Initial localization. More coming

Original comment by k.safro...@gmail.com on 5 Mar 2010 at 7:57

GoogleCodeExporter commented 9 years ago 
We need a test template in a language other than English, with non-latin 
character
set to test field names. Anything goes.

Original comment by zetapri...@gmail.com on 8 Mar 2010 at 12:14

GoogleCodeExporter commented 9 years ago 
Template with a Cyrillic font

Product URL:
http://www.zetaprints.com/magedev/index.php/email-signatures/localized-cyrilic.h
tml

Template ID:
3737023A-169D-4222-AA9F-2A525827780D

Original comment by agur...@gmail.com on 8 Mar 2010 at 1:13

GoogleCodeExporter commented 9 years ago 
We need to see if a non-developer can produce a localized version.
Post necessary files and instructions on how to do it here. You can just place 
links
to instructions.

Original comment by zetapri...@gmail.com on 10 Mar 2010 at 9:03

GoogleCodeExporter commented 9 years ago 
Ready to test on mageimage.

Original comment by k.safro...@gmail.com on 10 Mar 2010 at 12:43

GoogleCodeExporter commented 9 years ago 
Localization setup:
1. Create additional store view in system->manage stores
2. Go to system->configuration. Choose store newly created store view (Top left 
select box) and in General->Locale options choose locale.
3. Create (if not exists) locale folder in /app/locale. ex ru_RU and 
upload/create 
zetaprints_w2p.csv there. 
File format: "Original string","localized string". One per line.
List of used strings can take from Russian localization.
4. Clear cache.

Original comment by k.safro...@gmail.com on 10 Mar 2010 at 12:44

GoogleCodeExporter commented 9 years ago 
Need writing permission for the "locale" folder on FTP.

Original comment by agur...@gmail.com on 10 Mar 2010 at 3:25

GoogleCodeExporter commented 9 years ago 
Everything is already setup. Pls see mageimage.

Original comment by k.safro...@gmail.com on 10 Mar 2010 at 3:55

GoogleCodeExporter commented 9 years ago 
Yep, I saw the Russian language option. Just wanted to add a new one my self to 
see
how it works from a non-developer point of view. I quickly changed the csv file 
for
another language and wanted to try and install it.

(I believe) I have everything setup, just need to add the csv in that locale 
folder.

Original comment by agur...@gmail.com on 10 Mar 2010 at 4:17

GoogleCodeExporter commented 9 years ago 
Server was reset and ftp user rights accidentally dropped. Please drop file to 
me, I'll 
upload it.

Original comment by k.safro...@gmail.com on 10 Mar 2010 at 4:21

GoogleCodeExporter commented 9 years ago 
Thx, here's the file.

All you do is upload it right? No additional settings apart from the ones 
explained
in your previous instructions?

Original comment by agur...@gmail.com on 10 Mar 2010 at 4:44

Attachments:

GoogleCodeExporter commented 9 years ago 
File uploaded. Confirm no additional settings

Original comment by k.safro...@gmail.com on 10 Mar 2010 at 4:48

GoogleCodeExporter commented 9 years ago

Original comment by zetapri...@gmail.com on 10 Mar 2010 at 5:00

GoogleCodeExporter commented 9 years ago 
The settings that were already installed on /mageimage/ for the Russian language
option, work fine. The text fields that have a corresponding option inside the 
csv
file show up as they should.

I wasn't able to make it work in my language. I followed the instructions and 
you
uploaded the file for me. I still get a 404 page in Magento when I try to 
change to
the new language.

These are my settings:
Store view - see store_view.png
Configuration locale options - see configuration_locale.png
csv file changes - see csv_file.png (I just downloaded the RU version from the 
ftp
folder and changed the part that was in russian. Ex. "Rotate right","I CHANGED 
THIS
PART").

A question:
If I see a line of text on the site (Ex. "You have no items in your shopping 
cart.")
do I just add that line in the CSV file list and add a translation for it using 
the
same string format?

Original comment by agur...@gmail.com on 10 Mar 2010 at 5:17

Attachments:

GoogleCodeExporter commented 9 years ago 
"Reindex data" should be performed as well. It's working now.
Regarding question - No. This also should be coded on backend.

Original comment by k.safro...@gmail.com on 10 Mar 2010 at 5:51

GoogleCodeExporter commented 9 years ago 
The texts that are editable through the CSV file show up ok in the store. I 
think the
procedure is relatively easy even for a non-developer.

We should add a lot more options for translating though. The ones in the CSV 
file are
just a tiny portion of the store.

Original comment by agur...@gmail.com on 10 Mar 2010 at 7:00

GoogleCodeExporter commented 9 years ago 
We shouldn't translate all strings from M. in our extension. The task is to 
prepare
several translations as examples and describe how to make translation in another
language. I'm sure there's translations of M. interface for the most common 
languages
already.

Original comment by Anatoly....@gmail.com on 11 Mar 2010 at 2:30

GoogleCodeExporter commented 9 years ago 
Please merge localization branch

Original comment by k.safro...@gmail.com on 12 Mar 2010 at 7:50

GoogleCodeExporter commented 9 years ago

Original comment by Anatoly....@gmail.com on 14 Mar 2010 at 6:29

GoogleCodeExporter commented 9 years ago

Original comment by zetapri...@gmail.com on 24 Mar 2010 at 6:50