summaryrefslogtreecommitdiff
path: root/README.translators
diff options
context:
space:
mode:
authorAndreas Mair <amair.sob@googlemail.com>2006-07-07 11:43:39 +0200
committerAndreas Mair <amair.sob@googlemail.com>2006-07-07 11:43:39 +0200
commitf04236038448cce41ff2af10e2d0ccfcd8df378a (patch)
tree33979f482e9c11cf86a0ba10c3d0ed47a1e3d1a4 /README.translators
parentada389d94b34bfef75be700a6cb4e3f05ee102ff (diff)
downloadvdradmin-am-3.4.6rc.tar.gz
vdradmin-am-3.4.6rc.tar.bz2
2006-07-07: 3.4.6rcv3.4.6rc
- Replaced: Makefiles by make.sh (run "./make.sh" for usage information"). - Removed: LinVDR logo. - Changed: colors in timeline. - Fixed: layout problems in prog_summary detail view (Reported by Sven Soltau). - Fixed: moving forward/backward at the end/start of a month (Reported by foobar42).
Diffstat (limited to 'README.translators')
-rw-r--r--README.translators6
1 files changed, 3 insertions, 3 deletions
diff --git a/README.translators b/README.translators
index 2693a89..18c4c1c 100644
--- a/README.translators
+++ b/README.translators
@@ -1,4 +1,4 @@
-VDRAdmin-am translators guide
+VDRAdmin-AM translators guide
==============================
Since vdradmin-0.97-am3.2 almost every text has been extracted from the
@@ -53,7 +53,7 @@ The basic work flow for a translation looks like this:
a new *.mo-file from your changed *.po-file.
Please note, that you have to restart vdradmind.pl after any changes you
- make to the translation. In order to allow vdradmin to select your language,
+ make to the translation. In order to allow VDRAdmin-AM to select your language,
you must have the appropriate locales installed on your system (see
`locale -a`). You should make sure, that the correct locale is selected
with the LANG and LC_* environemt variables.
@@ -62,7 +62,7 @@ The basic work flow for a translation looks like this:
mail AT andreas DOT vdr-developer DOT org
-6) When changes have been made to vdradmin-am, that cause some messages to
+6) When changes have been made to VDRAdmin-AM, that cause some messages to
change, the *.po-files will by modified and we will send them to the
translators. The process then starts with 2) again and we will include your
new translation with the next release.