User Tools

Site Tools


admin_menu:languages:setup_preparation

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
admin_menu:languages:setup_preparation [2010/10/27 13:37]
james
admin_menu:languages:setup_preparation [2014/09/25 16:55] (current)
Line 1: Line 1:
 ====== Setup and Preparation Guidelines for Multi-Language Sites ====== ====== Setup and Preparation Guidelines for Multi-Language Sites ======
  
-**This is a current work in progress.  Let us know where we can improve it** +This tutorial has been moved to our [[startup_tutorial_and_checklist:feature_configuration:multi_language_setup:creating_your_own_translation|setup and configuration section of the support wiki here]]
- +
-Important: These instructions are written specifically for customers who are using the default layout of GeoAuctions/GeoClassifieds and are adding a SECOND LANGUAGE to their site.  +
- +
-Existing Install - Adding a second Language to an existing installation. We have used "Spanish" as an example, but the same steps apply to all language imports. +
- +
-  - Initial Setup - Creating the new language within the system +
-    - Access the LANGUAGES > ADD NEW LANGUAGE admin tool menu +
-    - Enter your new Language Name (i.e. Spanish) and click "Save"+
-    - This should create your new language within the system.  This creates a new "text" set within the admin tool for the "body html" dynamically generated content and then creates the new language as a selection +
-  - Language Import (optional)- If you have been supplied with a language translation of the text in the software by Geodesic Solutions or another Geo site you will then need to import the text.csv provided into your system. +
-    - That translation comes in the form of at least a text.csv file.  You will need to upload that text.csv file into the base of the /admin directory of the Geo Installation. +
-    - Now use the LANGUAGES > LANGUAGES HOME > [IMPORT] feature of the newly created language to import that text.csv file into that language. +
-    - Once you have successfully imported the 'text.csv' file, delete the 'text.csv' file within the 'admin' folder on your domain. The translated text for your new language should now be in the database.  +
-    - Note that as we develop the software we occasionally need to add new text to the system.  If we have added any new text to the system it will be "added onto the end" of the current text.  You may find it necessary to export the language you just imported and check the text.csv file created.  Any new text added to the system and not translated yet will be at the end of that text.csv file.  Download that text.csv, translate that text locally, re-upload over the text.csv currently in your Geo /admin directory and re-import that back into the system. +
-    - IMPORTANTYou may not see any language/text differences on your site for a couple reasons: +
-      * You need to make the necessary changes to your template set.  The text import done in this step does not translate text contained within addons or the page template/sub-template system. Until you make the necessary changes to your templates in the system most of the "design" will still be in the default language. +
-      * You may not have changed the language cookie attached to your browser.  When anyone goes to the Geo installation on your site for the first time the software checks to see if that browser has a "language cookie" set.  If it doesn't a language cookie is set at that time.  This happens even if you only have one language in your system.  Now that you have added the new language to the system you can go to the language choice page in the system and change the language cookie set on your browser to that of the new language.  See the [[admin_menu/languages/changing_languages_client_side|language selection tutorial]] within this section of the support wiki+
-  - Create new Templates for New Language  +
-    - In addition to the 'database text' you have already uploaded, there is also text located within the html of the software's templates. Since you will be entering HTML into your admin panel in these next steps, we recommend using the source code editor instead of the WYSIWYG editor within the **DESIGN > MANAGER** admin tool until you are finished with this process.  +
-    - Next, you may need to change the CHARSET setting that matches your current language within the **SITE SETUP > GENERAL SETTINGS** admin page. We have set the default character set for the software to utf-8.  This the most universal character set and is actually said to contain all others.  We see no reason to change this but some clients insist that utf-8 will not work on their sites.  We suggest at least starting out with utf-8 to see if it will work for you.  But if you do decide you need to use a different character set on your site the [[tutorials/using_different_character_sets/start|using different character sets]] tutorial will show you all that is needed to change the character set. +
-    - At this point you will need to do a little planning.  You will need to create "2nd language" copies of all language specific templates in the design you are translating: +
-      * You can create the "2nd language" files "right next" to the current default template files.  For example if you needed to make a Spanish copy of the default design's **basic_page.tpl** file you could copy that file into **basic_page_spanish.tpl**.  This puts both language files next to each other in the same directory of the template set. +
-      * Or you can create a "2nd language" directory within the current same template set labeled **/spanish** .  You could then copy the **basic_page.tpl** file into that directory for translation. +
-      * Or if you have been provided with translated templates you can upload them into the same directories over the same template files of the same name in your working template set.  Or if you are still going to need the original template files rename one set of templates (or both) to show which language is represented in each template set. +
-    - Which ever way you go with the choices above you will need to copy and then translate any or upload any template file you feel will need translation.  If you are translating the default design the only templates you should need to translate those templates within the **/main_page** and **/external** directories.  And consequently where you should look when uploading those templates you've received in the translation zip file. These are not the only templates used by the system but they are the only templates with text included within "seen" on the client side.  All of the "system/body_html" text is already translated by your text.csv file you have already translated. +
-    - The DESIGN > MANAGER tool allows you to create and edit files. +
-    - Once you have created all those language specific templates you will need to assign them to each page within the DESIGN > PAGE ATTACHEMENTS admin tool.  For each page you will see the ability to assign a page template for your other languages.  Any language within your system will be in that list for that page so you can assign a language specific template. +
-    - NOTE: Within the default design the **listing_auction.tpl** and **listing_classified.tpl** templates do not need to be translated as their content has already been translated by the text.csv file. +
-  - Set Up Language Specific Extra Pages +
-      - By default, we created several 'extra pages' for you to display additional information to users, such as, 'contact us', 'about us', etc. For each 'extra page' you are currently using on your site, you will need a "2nd Language equivalent" for that page.  You will find all of the extra page templates of the default design within the **/main_page/extra_pages/** directory of the template set.  If you have not translated these templates yet do so now for the extra pages you use within your design.   +
-      - Note by default all extra page templates have two templates set for each.  The outer page design template and the specific page content template for that page.  The default design uses the **basic_page.tpl** page template for the design and each extra page has a unique content template for each.  You most likely already translated the **basic_page.tpl** template in a step above.  You should only need to translate each extra pages specific content within that extra pages content template and assign the language specific content and page templates within each page. +
-  - Edit Addon Management Text.  +
-    - Module Addons have their own text fields. Therefore, it is necessary to edit the text for each Addon Module individually. This can be done through the **ADDONS > MANAGE ADDONS** admin tool for each module you use.  Note that if you disable AND uninstall an addon you will need to re-translate the text for that addon again. +
-  - Setup the way you want your clients change language on the client side as described in [[admin_menu/languages/changing_languages_client_side|language choice configuration tutorial]] +
-  - Other Language Specific Items to Review/Edit.  +
-    - If you have the Attention Getter Addon, add 'attention getter' images for your new language.  You may need to translate these images for the new language also.  That may entail creating each image from scratch unless those have been provided in the translation your were provided. +
-      * Create your images and upload (ftp) them into the **/addons/attention_getters/images/** folder on your domain or where ever your attention getter images are kept. +
-      * Enter the paths to the images into the software's admin panel under **ADDONS > ATTENTION GETTERS > SETTINGS**. +
-    - Enter the Currency Type for your new language if applicable under in the **LISTING SETUP > CURRENCY TYPES** and **PAYMENTS > CURRENCY DESIGNATION**  +
-      * Note: Certain currency symbols require that you enter their ASCII value. Please refer to the following link for your currency's ASCII designation and enter it into the appropriate field.  We found them here: http://www.ascii.cl/htmlcodes.htm  For example, the British Pound Sign would be: £ +
-    - Edit the Listing Durations to reflect your new language if applicable. Each Duration displays the appropriate day/month/year based upon language. Listing durations display in a dropdown box to the user during the listing process within the **LISTING SETUP > LISTING DURATIONS** +
-    - If you have the Signs and Flyers Addon, you may need to edit the template for each to reflect the appropriate text and images for your new language. Each template is stored in the TEMPLATES menu, but applied on the following pages: +
-      * PAGES MANAGEMENT > USER MANAGEMENT > USERS CURRENT LISTINGS > FLYER PAGE +
-      * PAGES MANAGEMENT > USER MANAGEMENT > USERS CURRENT LISTINGS > SIGN PAGE +
-    - Each category/subcategory name can be translated so that the category name/description displays in the appropriate language: +
-      * CATEGORIES > CATEGORIES SETUP > [EDIT] FOR EACH CATEGORY +
-    - Set the site default language to the language that you want your visitors to see when they first access your site. This is specified through the LANGUAGES menu for each language. +
-    - If you are using GeoClassAuctions Enterprise, a 'listing type' column displays throughout the browsing pages of the site. This 'listing type' column by default displays an "icon" for classifieds and another "icon" for auctions. You may want to edit these icons to a generic image and include a "key" on your page that informs the user as to what each icon represents. +
- +
-=====Setting Up for Right-to-Left Text===== +
- +
-Controlling the display of languages such as Hebrew and Arabic are not controlled within the software itself.  You will need to set this up within the html design you implement within the software.  You will need to make changes to the html in the language specific page templates for the language that requires right-to-left character display.  Here are a couple pages around the Internet that provide suggestions on how to implement this page wide or for specific blocks of text within html pages: +
- +
-  http://www.i18nguy.com/markup/right-to-left.html +
-  http://www.w3.org/TR/i18n-html-tech-bidi/+
admin_menu/languages/setup_preparation.1288186665.txt.gz · Last modified: 2014/09/25 16:55 (external edit)