-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Frank Peters wrote:
| You hit us right in the middle of the discussion. I would be curious | to hear your opinion on the matter. I am fairly comfortable using the ISO code for language (locale identifier) as the root for the wiki for eg. http://fedoraproject.org/es/join-fedora and http://fedoraproject.org/en/join-fedora or, http://www.redhat.com/docs/manuals/enterprise/RHEL-5-manual/bn-IN/index.html The logic applied in the above cases is that domain_name.domain/locale should be the translated version of the page available via domain_name.domain/ and thereon other pages would have /locale/Page_name So, something along the lines of wiki/Documentation/bn/FAQ for FAQs in bn looks like a works_for_me. However, being not conversant with Mediawiki, I am not in a position to provide inputs on the searching capabilities. However, this of course brings into picture another complexity - how would that kind of structure hook back into the concept that translations/localizations of content is a purview of NLC ? ~sankarshan ps: This does mean that the pages I translated need to be re-structured *sigh* - -- You see things; and you say 'Why?'; But I dream things that never were; and I say 'Why not?' - George Bernard Shaw www.linkedin.com/in/sankarshan -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iD8DBQFHi2zvXQZpNTcrCzMRAj9VAJ9nrLGmskHLwyG+TQigNzIjx4MIHwCfdRW2 uPyIPcVHslqg8YjuiIuoiAI= =+kUK -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
