This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
Summary: | I18N - allow AU client to recognize proper localized info.xml | ||
---|---|---|---|
Product: | platform | Reporter: | Ken Frank <kfrank> |
Component: | Autoupdate | Assignee: | akemr <akemr> |
Status: | RESOLVED FIXED | ||
Severity: | blocker | CC: | jf4jbug, jglick, keiichio |
Priority: | P2 | Keywords: | I18N |
Version: | -FFJ- | ||
Hardware: | Sun | ||
OS: | Solaris | ||
Issue Type: | ENHANCEMENT | Exception Reporter: |
Description
Ken Frank
2002-06-17 15:51:37 UTC
Probable duplicate of issue #22948? I don't think so. This issue is just about recognizing proper info.xml, if there are more than one in the nbm. But I agree, both issues should be solved together. Target milestone was changed from '3.4' to TBD. Implemented in trunk AU looks for Info/locale/info_xx.xml (for locale lang xx) at first, then for Info/info.xml Info/locale/info_*.xml within the NBM, I guess you mean. What about within the server XML file? Trying to think of what the complete usage will be, from 1. Building base module. 2. Building localized NBMs. 3. Publishing server XMLs mentioning both. 4. Client running in non-default locale finds existence of localized NBMs. 5. Client downloads & installs localized NBMs. > What about within the server XML file?
Server XML file should be sent straight in localized form. Value of
used Locale is sent to server as parameter (as S1S Update Center use it).
However, I agree there should be support for build process.
"Server XML file should be sent straight in localized form. Value of used Locale is sent to server as parameter (as S1S Update Center use it)." - OK, makes sense for S1S I think, but maybe problematic for NB or for any small, third-party update servers, I think. If you need to use a special update protocol to send the locale, this requires a servlet, not just static XML. Even if you encode the locale as part of the URL, you still need a servlet: maybe some user in Hungary is sending http://www.netbeans.org/updates/40_1.5_stable_hu_HU.xml (or whatever). Obviously this file will not exist if there is no Hungarian translation; you want to get the English file. The AU client could retry in a base locale, of course, if it gets a 404 from the HTTP request. What do you suggest? I think simple perl/cgi could solve instead of servlet. I don't know about good solution for static XML - instead of packing all l10n versions in one big xml :-( Maybe list of available locals can be an attribute of UC (AutoupdateType)? Then AU could try {url}_xx.xml and probably it succeed. If not (404), try {url}.xml Is this fixed now in context of new chinese localization and need for quantum server to recognize underscores so that zh_CN and zh_TW are treated differently if only localized nbm for zh_CN ? (this is coming in next quantum) If this is fixed now, could someone summarize fix so I can test it using UC ? ken.frank@sun.com |