In my previous company our Systems Analyst always gave emphasis on User Interface and always reminded us that it's not a trivial thing. I thought that it was a mature way of thinking to develop all the functionalities first. Yeah, if you're just a coder then that might be a more important thing...
When you plan to make your project multi-language and you are nearing its completion it is not smart to put those resource strings on a .resex files and edit right from your IDE. Why? Simply because it is not maintainable and hard to track changes whenever you add new entries. Also, your translators...
I hope that one day I will wake up that all web-shoppers are using IE7, firefox and opera... and IE6 will be burned into forgetten in the e-commerce arena. I hate it when simple CSS rules never worked on IE but works fine on Firefox, Opera and Safari where 80% of our consumers uses IE6 and 20% users...
When you are developing software product to be catered to diverse customers, it must be a standard to localized your software. With .NET this has never been easy, on .NET 2.0 its even easier with striongly typed resource files. But localizing application must be part of the architectture and should not...
Posted to
Rodel E. Dagumampan
by
rdagumampan
on
11-07-2006
Filed under:
Filed under: .NET, sql server , ASP.NET, usability and design, Development Process, how to, L10N, localization, scripts, stored procedures, user interface, sql, sequel server