Talk:Language editing: Difference between revisions
(→Instructions are not 1.9 friendly: reformat added screenshot comment) |
|||
(5 intermediate revisions by 5 users not shown) | |||
Line 1: | Line 1: | ||
==Instructions are not 1.9 friendly== | |||
I want to change this file to reflect 1.9 but do not want to eliminate information that might be useful for 1.8 users. | |||
I would propose to replace the instructions with those below and copy the old instructions to a new subheading called 1.8 instructions or something. | |||
Here is how the instructions should read for 1.9: | |||
To edit a word or phrase: | |||
#Go to the site administration block > Language > Language editing''. | |||
#Select the installed language pack you wish to edit from the pulldown menu. | |||
#Click the "Edit words or phrases" link in the middle of the page. A local folder will be created in moodledata/lang. Files of edited strings will then be saved in this folder. This is necessary to prevent changes that you make being overwritten by a newer language pack when updating. | |||
#Choose a file to edit from the pulldown menu. You may need to search through a few files before finding the file containing the word you wish to change. The file ''moodle.php'' contains all common site-wide phrases. | |||
#Change the word or phrase in the box provided to the right of the default phrase. | |||
#Click the "Save changes" button. The changed phrase will be highlighted in a different color. | |||
More comments | |||
*I don't understand the black arrows that point up and down which seem to be associated with every edit box. | |||
**Also when dealing with a sublanguage pack, such as en_us, the screens look very different from the primary language en. I suspect my lack of understanding of the interaction of these two files (perhaps 4 if I also altered the en and include the locals) has caused me problems. | |||
*And the screen shot for 1.9 is not what I see in demo.moodle--[[User:chris collman|chris collman]] 07:57, 12 May 2008 (CDT) | |||
==Double brackets== | ==Double brackets== | ||
Line 8: | Line 28: | ||
TODO: Ability to edit language files in non-standard locations... | TODO: Ability to edit language files in non-standard locations... | ||
Yes, that would be nice, since more and more 3rd-party modules carry their own language files in their folders, and the translation system does not yet apply to them. | Yes, that would be nice, since more and more 3rd-party modules carry their own language files in their folders, and the translation system does not yet apply to them. | ||
[[User:Joseph Rézeau|Joseph Rézeau]] | |||
==Correct paths?== | |||
"# From Moodle 1.9 onwards, only users with the capability moodle/site:langeditmaster may modify the master language packages (i.e. those being saved in moodledata/lang/). It is prevented from all roles by default. It is expected that only language maintainers will manually allow this to themselves. | |||
# From Moodle 1.9 onwards, only users with the capability moodle/site:langeditlocal may customize the site translation (i.e. files being saved in moodledata/lang_local/)." | |||
I've just tried this out on a test 1.9 install. Should the reference to "moodledata/lang" be "moodle/lang"? | |||
[[User: Ray Lawrence| Ray Lawrence]] | |||
No Ray. It's correct. Since 1.6, all languages except en_utf8, moved to the moodledata folder. This makes it possible to edit them and and download new versions through Moodle without running into problems with security settings. | |||
--[[User:koen roggemans|koen roggemans]] 09:04, 19 August 2007 (CDT) | |||
==Language editing in Moodle 1.5== | |||
Text in Moodle 1.5 may be changed by editing the language strings, either via ''Administration > Configuration > Language'' or directly e.g. in ''lang/en''. | |||
To ensure that any changes are not overwritten by a new version when upgrading, you need to create your own local language pack as follows: | |||
* Copy the contents of your language folder (e.g. ''lang/en'') into a new folder (e.g. ''lang/en_local'') - you will need access to the server to achieve this step, it cannot be done from within Moodle. | |||
* Make your local language pack the default for the site via ''Administration > Configuration > Variables''. | |||
--[[User:Helen Foster|Helen Foster]] 09:01, 20 January 2008 (CST) |
Latest revision as of 13:00, 12 May 2008
Instructions are not 1.9 friendly
I want to change this file to reflect 1.9 but do not want to eliminate information that might be useful for 1.8 users.
I would propose to replace the instructions with those below and copy the old instructions to a new subheading called 1.8 instructions or something.
Here is how the instructions should read for 1.9:
To edit a word or phrase:
- Go to the site administration block > Language > Language editing.
- Select the installed language pack you wish to edit from the pulldown menu.
- Click the "Edit words or phrases" link in the middle of the page. A local folder will be created in moodledata/lang. Files of edited strings will then be saved in this folder. This is necessary to prevent changes that you make being overwritten by a newer language pack when updating.
- Choose a file to edit from the pulldown menu. You may need to search through a few files before finding the file containing the word you wish to change. The file moodle.php contains all common site-wide phrases.
- Change the word or phrase in the box provided to the right of the default phrase.
- Click the "Save changes" button. The changed phrase will be highlighted in a different color.
More comments
- I don't understand the black arrows that point up and down which seem to be associated with every edit box.
- Also when dealing with a sublanguage pack, such as en_us, the screens look very different from the primary language en. I suspect my lack of understanding of the interaction of these two files (perhaps 4 if I also altered the en and include the locals) has caused me problems.
- And the screen shot for 1.9 is not what I see in demo.moodle--Chris collman 07:57, 12 May 2008 (CDT)
Double brackets
It seems to me there should be a mention somewhere of why sometimes you might see double brackets [[like this]], but I'm not quite sure what the most appropriate place might be.--N Hansen 10:48, 9 February 2006 (WST)
- Yes, you're right. The information could also be added to Administration FAQ. --Helen Foster 17:10, 6 July 2006 (WST)
Ability to edit language files in non-standard locations
TODO: Ability to edit language files in non-standard locations... Yes, that would be nice, since more and more 3rd-party modules carry their own language files in their folders, and the translation system does not yet apply to them.
Correct paths?
"# From Moodle 1.9 onwards, only users with the capability moodle/site:langeditmaster may modify the master language packages (i.e. those being saved in moodledata/lang/). It is prevented from all roles by default. It is expected that only language maintainers will manually allow this to themselves.
- From Moodle 1.9 onwards, only users with the capability moodle/site:langeditlocal may customize the site translation (i.e. files being saved in moodledata/lang_local/)."
I've just tried this out on a test 1.9 install. Should the reference to "moodledata/lang" be "moodle/lang"?
No Ray. It's correct. Since 1.6, all languages except en_utf8, moved to the moodledata folder. This makes it possible to edit them and and download new versions through Moodle without running into problems with security settings.
--Koen roggemans 09:04, 19 August 2007 (CDT)
Language editing in Moodle 1.5
Text in Moodle 1.5 may be changed by editing the language strings, either via Administration > Configuration > Language or directly e.g. in lang/en.
To ensure that any changes are not overwritten by a new version when upgrading, you need to create your own local language pack as follows:
- Copy the contents of your language folder (e.g. lang/en) into a new folder (e.g. lang/en_local) - you will need access to the server to achieve this step, it cannot be done from within Moodle.
- Make your local language pack the default for the site via Administration > Configuration > Variables.
--Helen Foster 09:01, 20 January 2008 (CST)