In-Portal Issue Tracker

Welcome to the In-Portal Open Source CMS Issue Tracker! This is a central management / tracking tool for all types of tasks / issues / bugs for the In-Portal Project. Before reporting any issues, please make sure to read the Guide into Issue Tracker and How to Properly Test and Report Bugs!

Dependency Graph View Issue ] Relation Graph ] Vertical ]
related to child of duplicate of

Viewing Issue Simple Details
ID Category Type Reproducibility Date Submitted Last Update
0000279 [In-Portal CMS] Optimization feature request N/A 2009-09-09 07:01 2010-07-22 15:06
Reporter alex View Status public  
Assigned To alex
Priority normal Resolution fixed  
Status closed      
Summary 0000279: Phrases of state and country names
Description Currently we have around 400 phrases of for countries and states used for ex. during checkout process. Translation of such kind of phrases almost never got changed and they provide additional load to each template, because they are used for Country field for users and user object is loaded on every page and these phrase with it.

I propose to create multilingual column Translation in StdDestinations table and move all current state/country translations there. Then loading of these moved values should be done using "options_sql" option in field definition in unit config.

Later we can add separate grid, where administrators could enable/disabled unneeded countries/states and change their translation.
Additional Information Same idea with currency translations.

In total we could decrease language pack by approximately 600 phrases, that never got changed.

---------

Country and state names and currencies should stay in language pack but not under <phrases> node by now. We can create special nodes for them, and language pack format will be like:

<LANGUAGES>
    <LANGUAGE PackName="English" Encoding="base64">
        <PHRASES>
            ...
        </PHRASES>
        <COUNTRIES>
            <COUNTRY iso="USA" translation=".....">
                <STATE iso="IL">...</STATE>
                ...
            </COUNTRY>
            ...
        </COUNTRIES>
        <CURRENCIES>
            ...
        </CURRENCIES>
        <EVENTS>
            ...
        </EVENTS>
    </LANGUAGE>
</LANGUAGES>

This way different language translation of countries/states/currencies could be still transferred in language packs, but won't be stored in Phrase table.



Web Development by Intechnic
In-Portal Open Source CMS
In-Portal Open Source CMS
Copyright © 2000 - 2009 MantisBT Group

Powered by Mantis Bugtracker