0ct0pu5/wesnoth
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

updated British English translation

Browse source
This commit is contained in:
Nils Kneuper 2023-09-02 12:40:26 +02:00
parent 7cb5f09bcf
commit 800060bce3
2 changed files with 7 additions and 7 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
changelog.md
View file

@ -8,7 +8,7 @@
### Packaging
### Terrain
### Translations
* Updated translations: Japanese
* Updated translations: British English, Japanese
### Units
### User interface
### WML Engine

12
po/wesnoth-help/en_GB.po
View file

@ -1293,7 +1293,7 @@ msgid ""
msgstr ""
"When loading a .cfg file, the scenario editor understands files created by "
"the scenario editor, but is likely to have difficulty with files that have "
"been edited by hand.\n"
"been edited manually.\n"
"\n"
"Files created by the scenario editor omit the opening [scenario] and closing "
"[/scenario] tags. If you are creating a campaign (or other add-on), then "
@ -1302,9 +1302,9 @@ msgstr ""
"\n"
"One workflow is to create a separate WML file, also with the .cfg extension, "
"which uses the WML preprocessor to include the editor-created file. This "
"separate file contains both the [scenario] tag and any hand-edited WML such "
"as events. With this workflow, the add-on’s file structure could look like "
"this:\n"
"separate file contains both the [scenario] tag and any manually-edited WML "
"such as events. With this workflow, the add-on’s file structure could look "
"like this:\n"
"\n"
"<header>text='For Wesnoth 1.14'</header>\n"
"\n"
@ -1548,9 +1548,9 @@ msgstr ""
"In scenario mode, the editor saves the data as a .cfg file with embedded map "
"data. When loading a .cfg file, the scenario editor understands files "
"created by the scenario editor itself, but is likely to have difficulty with "
"files that have been edited by hand; problems can be avoided by "
"files that have been edited manually; problems can be avoided by "
"<ref>dst='editor_separate_events_file' text='using a separate .cfg file'</"
"ref> for the hand-edited parts."
"ref> for the manually-edited parts."
#. [topic]: id=editor_map_format
#: data/core/editor/help.cfg:463