>>[Lilley] >>And thus, an authoring tool - or more precisely, a translation tool - >>has no way to know how to save out a set of linguistic versions of a >>resource. Each individual user has to make up their own system. >> >>If there was a standardised system, people and authoring tools could >>choose to use it, or not. Right on the nail. > >[Duerst] >Yes. But there is also some middle ground. My guess is that >a good content management system or translation support tool >can be configured to use the language information in the appropriate >place, e.g. with something like > LanugageSpecificFilename = GenericFilename_$lang$ >or >LanugageSpecificFilename = GenericFilename.$lang$ >or whatever the webmaster wants. If systems can't do that >yet, I hope they will allow it in the future. I am not inventing anything and the proposal is to formalize current practices. >From the moment there is a recommendation vendors/users will follow it. Regards Tomas Send instant messages to your online friends http://uk.messenger.yahoo.comReceived on Wednesday, 30 March 2005 08:56:16 GMT
This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 2 June 2009 19:17:05 GMT