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

Fix markup in README.

Browse source 
Fixes #3864
This commit is contained in:
josteph 2019-01-12 16:21:58 +00:00
parent e0fe47a6e2
commit 8cbc3a4477
1 changed files with 28 additions and 28 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

56
data/tools/wesnoth/README.md
View file

@ -6,55 +6,55 @@ written in python.
###
__init__.py
`__init__.py`
Cause Python to execute any code in this directory on "import wesnoth".
campaignserver_client.py
`campaignserver_client.py`
textmode-client for uploading + downloding campaigns to the server.
wescamp.py
`wescamp.py`
This utility provides two tools
* sync a campaign with the version on wescamp (using the packed campaign
as base)
* update the translations in a campaign (in the packed campaign)
wmldata.py
`wmldata.py`
This module represents the internal appearance of WML.
wmliterator.py
`wmliterator.py`
Python routines for navigating a Battle For Wesnoth WML tree
wmlparser.py
`wmlparser.py`
Module implementing a WML parser.
wmltools.py
`wmltools.py`
Python routines for working with a Battle For Wesnoth WML tree
###
From IRC #wesnoth-dev - 2007-11-27
<hajo> I just don't see the big picture about the files in that directory - who needs it for what task ?
<Sapient> well, let's say you want to process some WML files and transform them or understand them in a program
<Sapient> if you want to perform lexical analysis, then using wmliterator would save you a lot of work
<Sapient> if you want to parse it and get the overall tree, then wmlparser would be the choice
<hajo> Ok, but campaign / scenario-authors rarely do that
<Sapient> right...
<Sapient> if you want to write tools to help you author those campaigns,
<Sapient> you might write some programs or to maintain them
<Sapient> so it is only useful if you are a programmer
<Sapient> although wmliterator can do a decent job of detecting unbalanced WML
<Sapient> if that's all you need to do just run it from the command line for that
<Sapient> so it would let you know that [a][/b][/a] is invalid, and give you a line number
<Sapient> or [a][b][/a]
<hajo> it just says "reading x.cfg" and "y lines read"
<Sapient> right, no errors
<Sapient> it iterated successfully
<hajo> I just don't see the big picture about the files in that directory - who needs it for what task ?
<Sapient> well, let's say you want to process some WML files and transform them or understand them in a program
<Sapient> if you want to perform lexical analysis, then using wmliterator would save you a lot of work
<Sapient> if you want to parse it and get the overall tree, then wmlparser would be the choice
<hajo> Ok, but campaign / scenario-authors rarely do that
<Sapient> right...
<Sapient> if you want to write tools to help you author those campaigns,
<Sapient> you might write some programs or to maintain them
<Sapient> so it is only useful if you are a programmer
<Sapient> although wmliterator can do a decent job of detecting unbalanced WML
<Sapient> if that's all you need to do just run it from the command line for that
<Sapient> so it would let you know that [a][/b][/a] is invalid, and give you a line number
<Sapient> or [a][b][/a]
<hajo> it just says "reading x.cfg" and "y lines read"
<Sapient> right, no errors
<Sapient> it iterated successfully
# vim: tabstop=4: shiftwidth=4: expandtab: softtabstop=4: autoindent: