Join GitHub today
GitHub is home to over 20 million developers working together to host and review code, manage projects, and build software together.
attempt to fix #176 by unescaping XML in key values from transifex. #180
I'm not a huge fan of this solution because if transifex ever starts unescaping key values itself, we won't really know ... and it's hard to write integration tests w/ transifex because accessing the translations of an open-source project using their API still requires username/password authentication.
This comment has been minimized.
This comment has been minimized.Show comment Hide comment
It seems like we should file a bug with transifex. At the very least then we might be able to track a fix on their side through Github, although it still might be hard to know when it hits production.
I suppose we could also write a test script to compare the dummy data to real transifex data that takes a user:pass pair to run. Of course it would need to be run manually, and someone would have to remember it's there if/when another escaping/unescaping problem came up.