diff options
| author | Timothy Pearson <kb9vqf@pearsoncomputing.net> | 2011-11-16 13:50:19 -0600 |
|---|---|---|
| committer | Timothy Pearson <kb9vqf@pearsoncomputing.net> | 2011-11-16 13:50:19 -0600 |
| commit | c954cd41d38d75615d182ca8649fb4320148bdb3 (patch) | |
| tree | 125eb6216c2d08800783cf36d87013b4df8d8b3e /kturtle/scripts | |
| parent | 3fe5b9df0c463a3e9508242ab01f4c0242cf988b (diff) | |
| download | tdeedu-c954cd41d38d75615d182ca8649fb4320148bdb3.tar.gz tdeedu-c954cd41d38d75615d182ca8649fb4320148bdb3.zip | |
Additional renaming of kde to tde
Diffstat (limited to 'kturtle/scripts')
| -rw-r--r-- | kturtle/scripts/README.scripts | 16 |
1 files changed, 8 insertions, 8 deletions
diff --git a/kturtle/scripts/README.scripts b/kturtle/scripts/README.scripts index 2df17a38..f3b3aed3 100644 --- a/kturtle/scripts/README.scripts +++ b/kturtle/scripts/README.scripts @@ -6,9 +6,9 @@ When translating KTurtle more than just the usual 'documantation and strings' ha - the logokeyword.*.xml files, and - the logohighlightstyle.*.xml files. -These files are called data files, and their English originals can be found in kdeedu/kturtle/data. +These files are called data files, and their English originals can be found in tdeedu/kturtle/data. For more information on these files and their translation read: -kdeedu/kturtle/data/README.data +tdeedu/kturtle/data/README.data In this directory you find Rafael Beccar's nifty tranlaton perl scripts that can make translating KTurtle human resourcefriendly. @@ -20,26 +20,26 @@ If everything is working fine the general process is something like: 1. MANUALLY TRANSLATE THE KEYWORD -Copy the logokeywords.en_US.xml file (from kdeedu/kturtle/data) to the kturtle directory in your branch of the kde-i18n module (for Dutch this would be: kde-i18n/nl/data/kdeedu/kturtle). Translate the file, and change the name to: +Copy the logokeywords.en_US.xml file (from tdeedu/kturtle/data) to the kturtle directory in your branch of the tde-i18n module (for Dutch this would be: tde-i18n/nl/data/tdeedu/kturtle). Translate the file, and change the name to: logokeywords.YOURLANGCODE.xml 2. AUTOMAGICALLY GENERATE THE HIGHLIGHTSTYLE FOR YOUR LANGUAGE -- Copy logokeywords.YOURLANGCODE.xml to kdeedu/kturtle/scripts -- change directory to kdeedu/kturtle/sripts, and run: +- Copy logokeywords.YOURLANGCODE.xml to tdeedu/kturtle/scripts +- change directory to tdeedu/kturtle/sripts, and run: ./i18n_highlighting.pl logokeywords.YOURLANGCODE.xml -- Now you have a translated logohighlightstyle.YOURLANGCODE.xml under current directory (kdeedu/kturtle/scripts) +- Now you have a translated logohighlightstyle.YOURLANGCODE.xml under current directory (tdeedu/kturtle/scripts) 3. AUTOMAGICALLY GENERATE NEARLY FINISHED TRANSLATIONS OF THE EXAMPLES -- change directory to kdeedu/kturtle/scripts, and run: +- change directory to tdeedu/kturtle/scripts, and run: ./i18n_examples.pl logokeywords.YOURLANGCODE.xml - the translated examples can then be found in current directory. Some manual adjusments are needed, namely: the sings in the code and the comments 4. LAST BUT NOT LEAST!!! CHECK IF EVERYTHING WORKS -- move all the generated files to the kturtle directory in your branch of the kde-i18n module +- move all the generated files to the kturtle directory in your branch of the tde-i18n module - check if it installs correctly - check if the fresh logo examples in your language run when KTurtle is set to your language (see the Settings) |