On Mon, Apr 02, 2012 at 06:02:08PM +0000, Richard Rodgers wrote: > I think Mark makes a number of good points here - esp. regarding modularity > - and it's worth emphasizing that the net effect should be *less* > localization effort, even if there are potentially more files, since one > would only need to worry about the locally deployed modules - but I'm a bit > puzzled about the 'single catalog scheme' as a desired future state. > > Without much thought, I can come up with 4-5 quite distinct sites (places, > files, ways) where localization occurs in DSpace: > > * in email templates (config/email)
Good catch. I hadn't thought of those. There's nothing built into Java to handle these. > * in dspace,cfg and many other config files (starting with the 'dspace.name' > property) Picky point: I don't really think of that as localization. You get only one value per site. If we want e.g. 'dspace.name' to be localizable then we need to pull it out of dspace.cfg and tuck it into a catalog. Probably not the same one that the code depends on for its own internal messages, because sites want to customize this value and shouldn't have to edit stuff that's properly part of DSpace rather than the site. > * in input_forms.xml > * messages.xml and that ilk For completeness I'll throw in one we don't do yet but which has been requested: community and collection descriptions. > and I'm sure there are others; the curation stuff does not introduce a new > locus of localization: localizability permeates the application already. But if the texts are stored in dspace.cfg then it can't actually be localized, only customized in any single language you choose. It's not internationalized. > It's also worth noting that localized strings occur not just in the UI proper > - they can appear in RSS feeds, OAI-PMH harvests, etc > So I'd be leery of a plan to shoehorn all localization into any single > 'catalog scheme' , esp. one that is explicitly tied to a UI presentation > layer. Yes, the task is more varied than I thought. I was thinking only of having two distinct "messages" files, in different formats, containing (essentially) many of the same messages: one for API and JSPUI and the other for XMLUI. But there is more to DSpace than those. -- Mark H. Wood, Lead System Programmer [email protected] Asking whether markets are efficient is like asking whether people are smart.
pgpyQcpe50otc.pgp
Description: PGP signature
------------------------------------------------------------------------------ Better than sec? Nothing is better than sec when it comes to monitoring Big Data applications. Try Boundary one-second resolution app monitoring today. Free. http://p.sf.net/sfu/Boundary-dev2dev
_______________________________________________ DSpace-tech mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dspace-tech
