|Unjustified fun making|
The QA section at work just found the Klingon translation for the Web Service project I've been working on, and is making unjustified fun of me. To defend myself, here's how it happened...
Global product, with a few languages currently supported. I need to support different languages in my Web Service, but there aren't any other translations available for the messages yet. In fact, we're not inclined to spend the money until the messages stabilise a bit more. But I need that translation. Simon happens to own an English to Klingon dictionary, which is better than anything else we can find.
Klingon translation it is then.
Oh, it's never been shipped, and it never will be. It did test the message infrastructure though, and provided some cube fun. If only I hadn't got busted by QA.
Tags for this post: dotnet international internationalisation message translation klingon test
Related posts: Broken VSS integrations; Mono return codes; Tech talk blogs; A small example of how to find all the properties on an object using .NET reflection; Random fact for the day; Names for longhorn
posted at: 17:58 | path: /dotnet | permanent link to this entry