Hmm - good question. I don't know how Japanese
developers would normally see 'FileNotFoundException' - but I'd go with the 'keep it in CLR speak' (english) when it comes to class names etc..
> Where terms are descriptive but have no Japanese equivalent I assume it's okay to attempt a 'closest match'?
Closest match is a good approach - one thing to be aware of is the length of the resulting string, it may become to long to actually fit in the UI. This was occasionally a problem on the Russian translation and can lead to some trade-offs in meaning, but
I guess Japanese might have an edge there.
About the en-US typos - if you could provide us with the wrong texts we can fix it - if you send us fixed xml files, please include info about the version they came from so we may merge.
Again, I'd like to thank you (and your girlfriend) for doing this - it can be a huge "adoption booster" to be available in many languages and since "adoption" is a key performance indicator for open source, this actually mean a lot!
I'll get back to your other post - I mentally moved it to the to-do list because the question was pretty wide and could be a time consuming one to tackle. You are very welcome to follow up with some concrete scenarios/features, then it is a bit easier to
give a quick answer.