To create your own site-specific language file, all you have to do is select which strings you would like to override from
put them in a new file:
en_YS.dat. Then, you add
the language to your database using the steps below:
Procedure 17.1. Creating a new site-specific language file:
Create a new file under
en_YS.dat. This file should contain all of the text you would like to override from
If you do not have a local BML configuration file (
you should create one now. Add the following line to your local
DoGZIP 1 DefaultLanguage en_YS DefaultScheme nameofscheme
If you don't have a local language directive
create one now. Add the following lines to your local language file:
domain:100:faq # EnglishYS is child of English for general domain: lang:100:en_YS:English (YS):sim:en langdomain:en_YS:general # EnglishYS is root of FAQ: langdomain:en_YS:faq:1
The line “langdomain:en_YS:faq:1” is only required if
you want your FAQs to be translatable into other languages which derive from
en_YS. You probably do not want that, at least initially.
Once text is in the database, it is never changed with
load. This is to prevent
site local modifications (and modifications made at /translate/) from being lost.
To start over, use texttool.pl
and re-populate. Restart memcached if you are using it, as text lives
in there, too.