05 September 2004

The case of Turkish İ & Turkish I

This reminds me of a problem I had with a current developer-client. I am part of a team that is co-developing a new website CMS for a client. The lead developer for the client is also the designer of the application. The trouble is he's a terrible designer that is not very familiar with the .NET Framework. He's especially unfamiliar with the i18n portions. That's a big problem when the website is in six languages.

The client developer took the time to develop his own i18n facilities in the CMS. He completely bypassed the built-in objects. That was until I needed to change the format of a date by culture. To do this I created a table in the database to associate a custom date format string with specific cultures. I then set the executing thread to the culture provided by the client's custom objects. Finally, I set the date format provided by the database table. Simple.

Well, the client saw this and immediately wanted to set the ThreadCulture for the entire site. Now that would have been the right thing to do at the begining of the project. But we are only three weeks from testing. It took me a long time to explain to the client developer that ThreadCulture has an effect beyond data format.

Sometimes I really hate clients.


Post a Comment

Links to this post:

Create a Link

<< Home