pofile

unistack-org/pofile

Fork 0

Commit Graph

Author	SHA1	Message	Date
Julian Bäume	e1742e66a6	properly escape all unprintable characters writing messages should no be in line with gettext tools. I tested using msgcat, it provides the same results. For some common use-cases I wrote explicit tests, for uncommon and even unwanted use-cases I wrote one test to make sure pofile works like msgcat for those messages	2014-06-23 18:24:02 +02:00
Julian Bäume	851a87ebf2	add some real world examples for c-strings in po files make sure, if a file containing c-string messages is identical after being parsed and written afterwards.	2014-03-05 11:37:48 +01:00

Author

SHA1

Message

Date

Julian Bäume

e1742e66a6

properly escape all unprintable characters

writing messages should no be in line with gettext tools. I tested
using msgcat, it provides the same results.

For some common use-cases I wrote explicit tests, for uncommon and
even unwanted use-cases I wrote one test to make sure pofile works
like msgcat for those messages

2014-06-23 18:24:02 +02:00

Julian Bäume

851a87ebf2

add some real world examples for c-strings in po files

make sure, if a file containing c-string messages is identical after being
parsed and written afterwards.

2014-03-05 11:37:48 +01:00

2 Commits