Fix SQL translation script and associated unit tests
authordbs <dbs@dcc99617-32d9-48b4-a31d-7c20da2025e4>
Sun, 5 Jul 2009 05:28:40 +0000 (05:28 +0000)
committerdbs <dbs@dcc99617-32d9-48b4-a31d-7c20da2025e4>
Sun, 5 Jul 2009 05:28:40 +0000 (05:28 +0000)
commit9a71157ceb3a2c9b60df05a5d4c167a3c57375a1
tree52d2b5a5e44d6ff04a55b3f9a39112ec235d5455
parent95ca13d5cb9fe7c62945455dafbdf0cbfe6dfd53
Fix SQL translation script and associated unit tests

It looks like polib became stricter about forcing the line number portion of
filename:line occurrences in the PO to actually be an integer, with the result
of simply concatenating the text "line numbers" that we had been using to
store ID values to the table names.

Now we're using specially formatted translator comments to hold the ID values,
and using the filename:line occurence entries to actually hold the source filename
and line number for occurrences. Fancy that!

git-svn-id: svn://svn.open-ils.org/ILS/trunk@13500 dcc99617-32d9-48b4-a31d-7c20da2025e4
build/i18n/scripts/db-seed-i18n.py
build/i18n/tests/data/po2sql.sql
build/i18n/tests/data/sql2pot.pot
build/i18n/tests/data/sqlsource.po
build/i18n/tests/data/sqlsource.sql