TranslatorShellscript - Revision history

Egallager: /* Fusing commands */ typo

2021-04-02T10:01:04Z

‎Fusing commands: typo

Trewe: /* poEdits Wrath */ keep it simple

2014-11-17T21:48:57Z

‎poEdits Wrath: keep it simple

Trewe: /* First of all */ No poedit needed

2014-11-17T21:47:33Z

‎First of all: No poedit needed

Crommy: /* Extracting a target language script */ added a "./"

2014-11-17T21:10:07Z

‎Extracting a target language script: added a "./"

Crommy: /* Extracting a target language script */ "> target-language-script" included in command line

2014-11-17T20:52:07Z

‎Extracting a target language script: "> target-language-script" included in command line

Crommy: added category Tools

2011-07-10T10:29:19Z

added category Tools

Crommy: /* Style scripts following the typographic style guide */ correcting typos, explained a bit more

2011-03-12T13:31:27Z

‎Style scripts following the typographic style guide: correcting typos, explained a bit more

Crommy: /* Style scripts following the typographic style guide */

2011-03-11T22:32:45Z

‎Style scripts following the typographic style guide

Crommy: Added "Typographic style scripts" for Ellipsis, Dash, Apostrophe, Multiple Spaces and Quotes

2011-03-11T18:39:09Z

Added "Typographic style scripts" for Ellipsis, Dash, Apostrophe, Multiple Spaces and Quotes

Crommy: /* Extracting a target language script */ hinzufügen sed-version, nur Zielsprache

2010-01-06T18:08:46Z

‎Extracting a target language script: hinzufügen sed-version, nur Zielsprache

@@ Line 142: / Line 142: @@
 === Fusing commands ===
-Use the followoing style:
+Use the following style:
     cat de.po | sedcommand1 | sedcommand2 | sedcommand3 > de.po1

@@ Line 8: / Line 8: @@
 == poEdits Wrath ==
 Anyhow, those changes introduced by poEdit should be undone prior sending the new po-File to your language maintainer. Especially, it must be undone prior to "diff" the new version against the old one. This may be done by executing the following:
-    msgattrib file.po > file.po1
+    msgcat file.po -o file.po
 Now, if you

@@ Line 3: / Line 3: @@
 == First of all ==
 Prior to use the shell scripts, the po-File needs to be opened and saved with poEdit. The reason is, that then the texts are saved in separated lines without interfering  /n's. As result, a normal entry consists of 4 lines, where one line contains the "characters text" and a prior line the "characters name". Without saving the file with poEdit, the number of text-lines would be undefined.
 == poEdits Wrath ==

@@ Line 28: / Line 28: @@
 An even nicer extraction method without saving via poedit is the following :
-::> sed -n 's/#\. \(\[scenario\]: id=.\+\)$/\n\n\1/p;s/#\. \(\[part\]\)$/\n\1/p;t msgid;s/#\. \[message\]: speaker=\(.\+\)$/\1/;t speaker;b;:speaker;H;n;s/#\. \[message\]: speaker=\(.\+\)$/, \1/;t speaker;x;s/$/:\t/;s/\n//g;x;t msgid;:msgid;s/msgid \(".*"\)/\1/;t nextmsgid;n;b msgid;:nextmsgid;H;n;/^".*"$/b nextmsgid;x;s/"\n"//g;s/\n//;;s/".*"//;x;s/msgstr \(".*"\)/\1/;:nextmsgstr;H;n;/^".*"$/b nextmsgstr;x;s/"\n"//g;s/\n//;s/$//;p' de.po > target-language-script.txt
+::> sed -n 's/#\. \(\[scenario\]: id=.\+\)$/\n\n\1/p;s/#\. \(\[part\]\)$/\n\1/p;t msgid;s/#\. \[message\]: speaker=\(.\+\)$/\1/;t speaker;b;:speaker;H;n;s/#\. \[message\]: speaker=\(.\+\)$/, \1/;t speaker;x;s/$/:\t/;s/\n//g;x;t msgid;:msgid;s/msgid \(".*"\)/\1/;t nextmsgid;n;b msgid;:nextmsgid;H;n;/^".*"$/b nextmsgid;x;s/"\n"//g;s/\n//;;s/".*"//;x;s/msgstr \(".*"\)/\1/;:nextmsgstr;H;n;/^".*"$/b nextmsgstr;x;s/"\n"//g;s/\n//;s/$//;p' ./de.po > target-language-script.txt
 (derived from the SED-command below- thanks to Soliton)

@@ Line 28: / Line 28: @@
 An even nicer extraction method without saving via poedit is the following :
-::> sed -n 's/#\. \(\[scenario\]: id=.\+\)$/\n\n\1/p;s/#\. \(\[part\]\)$/\n\1/p;t msgid;s/#\. \[message\]: speaker=\(.\+\)$/\1/;t speaker;b;:speaker;H;n;s/#\. \[message\]: speaker=\(.\+\)$/, \1/;t speaker;x;s/$/:\t/;s/\n//g;x;t msgid;:msgid;s/msgid \(".*"\)/\1/;t nextmsgid;n;b msgid;:nextmsgid;H;n;/^".*"$/b nextmsgid;x;s/"\n"//g;s/\n//;;s/".*"//;x;s/msgstr \(".*"\)/\1/;:nextmsgstr;H;n;/^".*"$/b nextmsgstr;x;s/"\n"//g;s/\n//;s/$//;p' de.po
+::> sed -n 's/#\. \(\[scenario\]: id=.\+\)$/\n\n\1/p;s/#\. \(\[part\]\)$/\n\1/p;t msgid;s/#\. \[message\]: speaker=\(.\+\)$/\1/;t speaker;b;:speaker;H;n;s/#\. \[message\]: speaker=\(.\+\)$/, \1/;t speaker;x;s/$/:\t/;s/\n//g;x;t msgid;:msgid;s/msgid \(".*"\)/\1/;t nextmsgid;n;b msgid;:nextmsgid;H;n;/^".*"$/b nextmsgid;x;s/"\n"//g;s/\n//;;s/".*"//;x;s/msgstr \(".*"\)/\1/;:nextmsgstr;H;n;/^".*"$/b nextmsgstr;x;s/"\n"//g;s/\n//;s/$//;p' de.po > target-language-script.txt
 (derived from the SED-command below- thanks to Soliton)

← Older revision		Revision as of 10:29, 10 July 2011
Line 156:		Line 156:

	[[Category:Translations]]		[[Category:Translations]]
		+	[[Category:Tools]]

@@ Line 106: / Line 106: @@
 Here, I show possibilities using an UNIX-environment (Windows-user - check "cygwin" or similar for getting something like this). I like to use pipes ("|"), as you may easily put those commandos one after another as you need it for your purpose.
-Those scripts only work on po-files re-saved with po-Edit, thus guaranteeing "single-line strings". The "single-line string" is important, as  it is a simple ay to separate the original and translated string. Otherwise you will introduce changes in the original strings as well as in the translated ones and subsequent patching your translation to the game might fail.
+Those scripts only work on po-files re-saved with po-Edit, thus guaranteeing "single-line strings". The "single-line string" is important, as it is a simple way to separate the original from the translated string. Otherwise you will introduce changes in the original strings as well and subsequent patching your translation to the game might fail.
 === No double spaces ===
@@ Line 131: / Line 131: @@
 === Apostrophes ===
-This command line exchanges all occurrences of the keyboard »'« with the curly one »’«. This might not be applicable for all languages.
+This command line exchanges all occurrences of the keyboard »'« with the curly one »’«. This might not be applicable for all languages depending on its use.
     cat de.po |  sed "/msgstr/s/'/’/g" > de.po1
 === Use of » or « for Quotes ===
-If your language team decided on using » and « as quotation marks (instead of " or ' or similar) you may type << and >> in your po-file
+If your language team decided on using » and « as quotation marks (instead of " or ' or similar) you may type >> and << in your po-file and the command line below changes it into the nice ones:
     cat de.po | sed '/msgstr/s/>>/»/g;/msgstr/s/<</«/g' > de.po1
@@ Line 143: / Line 143: @@
     cat de.po | sedcommand1 | sedcommand2 | sedcommand3 > de.po1
-e.g. changing apostrophes and quotes and ellipsis in one step:
+e.g. changing apostrophes and quotes and ellipsis in one step and producing a new file called "de.po1":
     cat de.po |  sed "/msgstr/s/'/’/g" | sed '/msgstr/s/>>/»/g;/msgstr/s/<</«/g' | sed '/msgstr/s/\.\.\./…/g' > de.po1

@@ Line 104: / Line 104: @@
 == Style scripts following the typographic style guide ==
-Here, I show possibilities using an unix-environment (Windows-user - check "cygwin" or similar for getting something like this). I like to use pipes ("|"), as you may easily put those commandos one after another as you need it for your purpose.
+Here, I show possibilities using an UNIX-environment (Windows-user - check "cygwin" or similar for getting something like this). I like to use pipes ("|"), as you may easily put those commandos one after another as you need it for your purpose.
-Those scripts only work on po-files re-saved with po-Edit, thus guaranteeing "single line strings". The "single lined string is important", because otherwise you will introduce changes in the original strings as well and patching your translation to the game might fail.
+Those scripts only work on po-files re-saved with po-Edit, thus guaranteeing "single-line strings". The "single-line string" is important, as  it is a simple ay to separate the original and translated string. Otherwise you will introduce changes in the original strings as well as in the translated ones and subsequent patching your translation to the game might fail.
 === No double spaces ===

@@ Line 1: / Line 1: @@
 Feel free to post improvements as well. In which languages it does not work at all? What kind of shell script are needed as well?
 == First of all ==
@@ Line 25: / Line 23: @@
 == Extracting a target language script ==
-For proof-reading of a campaign it might be much easier to print it out in a more "scriptlike" format (<charactername>: <text>) (target language only), e.g. to read it in a bus, a train or in a car.
+For proof-reading of a campaign it might be much easier to print it out in a more "scriptlike" format (<charactername>: <text>) (target language only), e.g. to read it in a bus, a train or in a car. Thanks to the programmer(s) that included the "speaker" in the comments of the po-files (Ivanovic?)! Those are definitely helpful and make this approach possible.
 ::>cat ./de.po | grep -v "msgid \"" | grep -v "#: data" | sed "s/\[message\]: speaker//g" | sed "s/#. =//g" | sed "s/msgstr/:/g" |grep -v ": \"\"" | sed ':;s/\n:/:/;N;T' | sed ':;s/\n\n/\n/;N;T'| sed "s/#. \[scenario\]/\n#. \[scenario\]/g"   > target-language-script.txt
@@ Line 35: / Line 31: @@
 (derived from the SED-command below- thanks to Soliton)
 == Extracting an English script ==
@@ Line 88: / Line 86: @@
 I have a Slovak translation "sk.po", and would like to use a Czech translation as help:
-multi_po.pl sk.po --add cs.po CS > sk_multi.po
+   multi_po.pl sk.po --add cs.po CS > sk_multi.po
 In file "sk_multi.po" there is for every phrase added corresponding Czech translation from "cs.po" file, labeled as "CS". (My original comments in "sk.po" file are there, too.)
@@ Line 94: / Line 92: @@
 Before sending to translation maintainers, I remove unnecessary comments:
-multi_po.pl sk_multi.po --remove > sk.po
+   multi_po.pl sk_multi.po --remove > sk.po
 The Czech translations are removed. (My original comments remained.)
@@ Line 105: / Line 103: @@
 http://www.wesnoth.org/forum/download/file.php?id=5872
 == Comments ==

← Older revision		Revision as of 18:08, 6 January 2010
Line 30:		Line 30:

	::>cat ./de.po \| grep -v "msgid \"" \| grep -v "#: data" \| sed "s/\[message\]: speaker//g" \| sed "s/#. =//g" \| sed "s/msgstr/:/g" \|grep -v ": \"\"" \| sed ':;s/\n:/:/;N;T' \| sed ':;s/\n\n/\n/;N;T'\| sed "s/#. \[scenario\]/\n#. \[scenario\]/g" > target-language-script.txt		::>cat ./de.po \| grep -v "msgid \"" \| grep -v "#: data" \| sed "s/\[message\]: speaker//g" \| sed "s/#. =//g" \| sed "s/msgstr/:/g" \|grep -v ": \"\"" \| sed ':;s/\n:/:/;N;T' \| sed ':;s/\n\n/\n/;N;T'\| sed "s/#. \[scenario\]/\n#. \[scenario\]/g" > target-language-script.txt
		+
		+	An even nicer extraction method without saving via poedit is the following :
		+	::> sed -n 's/#\. \(\[scenario\]: id=.\+\)$/\n\n\1/p;s/#\. \(\[part\]\)$/\n\1/p;t msgid;s/#\. \[message\]: speaker=\(.\+\)$/\1/;t speaker;b;:speaker;H;n;s/#\. \[message\]: speaker=\(.\+\)$/, \1/;t speaker;x;s/$/:\t/;s/\n//g;x;t msgid;:msgid;s/msgid \("."\)/\1/;t nextmsgid;n;b msgid;:nextmsgid;H;n;/^"."$/b nextmsgid;x;s/"\n"//g;s/\n//;;s/"."//;x;s/msgstr \("."\)/\1/;:nextmsgstr;H;n;/^".*"$/b nextmsgstr;x;s/"\n"//g;s/\n//;s/$//;p' de.po
		+
		+	(derived from the SED-command below- thanks to Soliton)

	== Extracting an English script ==		== Extracting an English script ==