https://issues.apache.org/ooo/show_bug.cgi?id=123260
--- Comment #10 from Ariel Constenla-Haile <[email protected]> --- (In reply to Oliver-Rainer Wittmann from comment #6) > I would volunteer to improve/change the update functionality, but we should > figure out what the result of this improvement/change shall be. > Any feedback on this? IIRC the update mechanism provides information about the office installation in two HTTP headers: 1) User-Agent is read from version(rc|.ini), where ${AllLanguages} in UpdateUserAgent=<PRODUCT> (${buildid}; ${_OS}; ${_ARCH}; BundledLanguages=${AllLanguages}) is expanded to the value of AllLanguages in that file; this value is the locale of the full installation set. AFAIK it is always a single language (it is possible to build multi-lingual full install sets, but I've never seen them released by OOo). 2) Accept-Language is read from the configuration registry org.openoffice.Setup/L10N/ooLocale with the current user interface locale All these isn't taken into account because the update feed is static. It might be worth to investigate if infra allows to develop a CGI script to generate the feed dynamically. It is also possible to know all installed language packs, by reading the configuration registry (vid. how they fill the listbox in "Tools" - "Options..." - "Language Settings" - "Languages" - "Language of" - "User interface" http://svn.apache.org/viewvc/openoffice/trunk/main/cui/source/options/optgdlg.cxx?view=markup#l1220 ) For 4.0.1 it might be enough to check the list of installed language packs and warn that the offered download is only about the full install set; also warn if there is no language pack available for one of the installed language packs. Side note: the whole update design might to be broken since the beginning, if it only offered updates for the full install set, regardless of the installed language packs - I don't have old version with language packs to test this right now. But in general, I see no regression here compared to Sun/Oracle times. -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug. You are watching all bug changes.
