My recommendation...it's a long job so it needs to be split into stages.
-
Get Beyond Compare or equivalent: it's your primary tool.
and install ZC on a local computer: much easier to search for texts.
-
Understand that there are two sets of files: one for the shopfront, one for the admin.
Each one has an english.php file and an /english folder with lots of files in it. Each files has lots of constants defined in it, that get used by the code to display the texts.
-
Understand that a language pack is for general use, so there may be translations personal to you that are not suitable for other users.
So, you should really fix all the problems with the language pack on an uncustomised ZC157 site before copying the files to your site and then making overrides with your custom texts.
-
Duplicate the english.php files and folders and rename them french.
-
"install" french in the admin...this is just telling ZC that the language exists so it shows up in the menus.
Check that you can select french in the admin and in the shopfront and all works without errors....despite it still being in english of course.
-
Compare the old french language pack to the new french site files. There will be files that exist in one and not the other.
-
I suggest you work on the shopfront files first.
Where the same files exist: copy the old files to overwrite the copies of the english files.
The reason for this is that the files need to be in utf-8 format, and it is easier to start with the old files and add new constants.
-
Now compare the English fileset to the French fileset, one by one, to add/remove constants as necessary so all constants exist in both languages.
No need to translate them yet, just make sure they exist. And add the comment //todo at the start of the file so it can be found easily.
New files (that will be in english) will be in ANSI format and should be in utf-8, if not then you get odd characters displayed where accents are used.
I use Notepad++ for this: open the ANSI file, select all, cut, change the encoding, paste, save.
-
When you have equalised the constants and files, and you can navigate around the site without any errors, (but the text is a mixture of french and english phrases): the pack is "complete" and ready for the long work-in-progress that is the translation.
You will get white pages of death when you miss out a quotation mark, but the corresponding debug log will tell you where your mistake is.
I think people start with the best intentions of translating and submitting a translation like it is a few hours work. It is not.
As there are so many texts, it can be hard/impossible to translate them without seeing the context in which they are used and so there are constant minor changes to make as you find them in real use, later on (but mainly in the admin).
I suggest you learn how Github works, to host your translation.
I've been doing the Spanish pack for 10 years and there are still some parts I have never reviewed. It is a LOT of work to do it 100%...so do not try...get it on Github and do it when you want / when it is convenient / when you spot an error.
On Github you can make it available part-finished/as you go along: for others to contribute, and so you don't feel any pressure to hurry-up and submit a final/updated version to the Zen Cart site, and lose your enthusiasm on the way.
Steve
github.com/torvista: BackupMySQL, Structured Data, Multiple Copy-Move-Delete, Google reCaptcha, Image Checker, Spanish Language Pack and more...