>1.
Calm down Joe, I didn't mean to insult you. I told you to learn a lot
didn't mean that I insulted you that you're a newbie. Please Don't take
emotion with my suggestion, I didn't force you right? Actually, the
sentence learn a lot is a high philosophy of life. I especially learn
it from a respective Software Architect who always said that he's still
a newbie and have a lot to learn because a newbie may think to enough
to learn whilst an expert always thinks has a lot to learn.
If you don't like with this philosophy then just throw it away, but
don't take negative thinking when someone says you to learn a lot .
-- OK , if you say no insult intended, then I accept that as a misunderstanding on my part. No hard feelings.
>2.
I know taht you're aware of Rainbow Portal but I did think you're not
aware of it's localization feature. I mentioned Rainbow as an example
of good Localization portal which supports multiple culture in one
site. I didn't mention that you're not aware of Rainbow portal, did I?
-- you said it in the same sentence with "I think you have a lot to learn" so I took it this way.
>date
time and number formats have not been part of our discussion. don't
assume I don't understand those issues just because we have not
discussed them.
3. Actually, It's part of main discussion
because It's one of the most important part of the .NET localization so
I think mojoPortal missed the point here.
-- we did not discuss it, if you have a specific problem with how mojoportal handles it I'm glad to hear about it as long is it doesn't involve storing anything in resource files
>4.
No, I think I'm not overly enamoured with guidelines, I've already
built and architected web sites with this guideline and everything
works and is easy. So I speak with my experience not just in theory.
-- I don't doubt you have been successful with it but perhaps your requirements are not the same. I don't think storing anything in resource files makes it easy to change for people who are not developers, that is a requirement for mojoportal that is not met by using the .NET localization guidlines. I won't throw away my requirement just because msdn says thats how you do localization. Throughout our duscussion I have read a lot of the localization articles and I still say that I am doing localization with mojoportal without using the guidelines. The definition of localization is supporting any single culture. What I am not doing is internationalization which means supporting multiple cultures in one site. My view is that everthing visible in a web site is content including what is in the database and in labels and buttons. That is the essential difference with a web application and other types and I think this is the essential difference in how we look at the problem. The content stakeholders must be able to change anything easily.
> Last but not least, take it easy and be happy
-- Thanks, same to you!