Álvaro Tejero Cantero a écrit : > I'm not versed in po-file handling, but when I translated CPS to spanish > I somehow found the following directive: > > "X-Is-Fallback-For: es-ar es-bo es-cl es-co es-cr es-do es-ec es-sv > es-gt es-hn es-mx es-ni es-pa es-py es-pe es-pr es-us es-uy es-ve\n" Never noticed. But as I know Localizer and especially CPS, those are not taken into account: knowing this is the Spanish po file is enough for their work at install time. > Naturally, I set the es-ES spanish variant to work as fallback for all > the others, since es-* do understand each other, at least more so than > they understand English. Well, since I get you... which Spanish do you use? Castillan I guess. Are other Spanish forms close enough for a single translation? American Spanish is ok I think but is Catalan too different? > Now, what I don't know is how CPS handles this extra information. I > guess The Right Thing would be to make all the fallbacks also available > at creation time. In the long term, TranslationService would replace and extend Localizer. We'll see. > The problem with all these language variants is that the user interface > will suffer if the dropdown list gets too long. I don't know about > performance, does anybody know if it worsens if too many message > catalogs are added? (OTOH, the es-* fallbacks would be all aliases for > the one and only spanish message catalog, es-ES, at least until they get > their own). Only CPSDefault would use the whole list; users would just keep the languages they are interested in at install time. I don't think a comprehensive list would slow things down that much. Localizer looks for the Accepted-Languages header and selects the best default language; Once you get there, CPS uses just one message catalog. More a memory issue if there is one... -- Hervé
Hosting: Nuxeo: Zope service provider