20Feb/100
Article: Using XNA Content pipeline extensions for localization. (Part 2)
by Roy Triesscheijn
Recap
So… last time we made our strings localizable and added-in a new content manager. Today we are going to make all our content localizable, but first we should revisit and refactor “yesterday’s code”.
After publishing part one and having a good week to think about part two, I found that some of my design choices, which seemed nice, where actually at bit cumbersome.
Also the xml parsing (in BABProcessor) wasn’t as robust as I wanted it to be because I forgot about localized formats for dates and numbers.
Fixing our xml loading is easy, so let’s first fix that!