This scenario has a narrative bug. The river the party is following is
flowing in the opposite direction than the narrative says.
I've avoided the problem by formulating all sentences to have "along the
river" form instead of "up the stream". However, I couldn't avoid the
main problem in such a manner -- the waterfall. I've translated this
inconsistency blindly, as if unnoticed.
The bug is reported and already fixed upstream (pun intended).
pre-commit hook does the following actions:
Changes PO-Revision date to 2010-01-01 00:00+0300
Changes Last-Translator to Andrius Štikonas <stikonas@gmail.com>
Wraps all strings with msgattrib.
Source code of pre-commit hook:
for FILE in `git diff-index --name-only --cached HEAD --` ; do
msgattrib "$FILE" > "$FILE"e
mv "$FILE"e "$FILE"
sed -ie '/^\"PO-Revision-Date*/{G;x;s/^/\"PO-Revision-Date: 2010-01-01 00:00+0300\\n\"/}' "$FILE"
sed -ie '/^\"Last-Translator*/{G;x;s/^/\"Last-Translator: Andrius Štikonas <stikonas@gmail.com>\\n\"/}' "$FILE"
rm "$FILE"e
git add $FILE
done
Changed Aetenvudas back to Aethenvudas, since that's how we call it in
all other places. Such a change should be either massive, or a part of
incremental change.
We agreed upon translating Asheviere as Aševierė couple weeks ago, so I
changed all the places we had her name and translated those that
remained untranslated. This changeset can be held a reference point in
case we ever decide to change the Lithuanian transcription.
This reverts commit cdef479ee9.
I'm doing this because I noticed several more untranslated strings with
Asheviere's name in them. I want to have all such strings in one single
changeset for easier tracking in possible re-editions. This commit will
be reintroduced shortly along with the new strings as a single changeset.
We agreed upon translating Asheviere as Aševierė some time last week, so
I changed all the places we had her name and translated those that
remained untranslated. This changeset can be held a reference point in
case we ever decide to change the Lithuanian transcription.