tek1 escribi�::
i vote yes.
there are still lots of people in the world who cannot speak english. making messages localized will help increase the worldwide adoption of xdoclet.
I wholeheartedly agree.
*if multilingual support cannot be offered initially*, perhaps it could be incorporated in say version "2.1". version "2.0" could be the initial version to get it out the door to the masses quickly. and then, along with bug fixes and improved stability, the next incremental version could add multilingual support (i.e. using ResourceBundles).If 2.0 is really supposed to be the major re-write to clean up the "code hairballs" I've heard about, then 2.0 is the time to do it, not 2.1. I18N'ing code is vastly more difficult to bolt-on to already written code. Starting out with I18N in place is soooo much easier.
Remember, you don't have to do all tranlations at the outset. You should just have the framework in place at the outset, and provide a default localization (English) at first. Once the framework is in place, you ask your open-source buddies from around the world to contribute to tranlating your messages, and add those to the project as they come in (plug-n-play = no pressure).
Speaking from experience (of doing both),
David
-------------------------------------------------------
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com
_______________________________________________
xdoclet-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/xdoclet-user
