Post by dennisforrest » Mon Sep 10, 2007 10:13 pm

Hi Daniel,

I suggest you a new and easy way for manage the localization.

Actually, every file in language directory contain all the key used in a specific module or page, but there are some function that use the same keyword or message.
For example, the keywords:
$_['entry_firstname']  = 'First Name:';
...
$_['error_firstname']  = '* First Name must be greater than 3 and less than 32 characters!';
are used in many controller language file such:

language/english/controller/account_address.php
language/english/controller/account_create.php
etc...

My suggestion is to put all the common keyword in a single file, and use the specific files only for define the variation from the default value.
If there is no variation, is it not necessary to define the keyword.


What do you think about it?

Another good idea is to create a translator tool, that permit to display a table with the english (default) translator and an input text for insert the translation for the specific language.

regards,
denis
Last edited by dennisforrest on Mon Sep 10, 2007 10:15 pm, edited 1 time in total.

Newbie

Posts

Joined
Tue Aug 07, 2007 7:55 pm

Post by petpetep » Tue Sep 11, 2007 4:51 pm

i'm not sure, but if be only in one file ... then the all thing will be slower, and this is not a problem to be in different files.

i think that the better way is opencart can be work only in one language different of english :)

New member

Posts

Joined
Sat Aug 11, 2007 4:19 pm


Post by Tunox » Tue Sep 11, 2007 9:04 pm

your opinion is valid Denis and maybe in the future I would like to see it too. In the meantime it ain't anything that will worry the shop editors as they have no business with the language files. As for us it ain't a problem as Ctrl+C still works but for Daniel it might present some extra work and I wouldn't like to see him overloaded with these details ;)

Newbie

Posts

Joined
Sat Sep 08, 2007 5:43 pm

Post by luvz2drv » Thu Sep 13, 2007 4:22 am

also just a point..  having the lang files split up - alows for more customization...  on one page you can call it

for example -- Buy Now  and on a another page just call it buy

I think it helps when you start customizing it it alows for better non hard coded words

just MHO

luvz2drv


Post by Daniel » Thu Sep 13, 2007 4:50 am

The problem is with language files all together is that you need to start doing:

heading_account_create
heading_account_edit

etc..

Also if some one releases a contribution to extend the account system they then have to write instructions for updating the account laguage file.

OpenCart®
Project Owner & Developer.


User avatar
Administrator
Online

Posts

Joined
Fri Nov 03, 2006 6:57 pm
Who is online

Users browsing this forum: No registered users and 6 guests