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.

Bug 58118 - I18N - info.xml should be i18ned to allow for localization.
Summary: I18N - info.xml should be i18ned to allow for localization.
Status: CLOSED FIXED
Alias: None
Product: platform
Classification: Unclassified
Component: Autoupdate (show other bugs)
Version: 4.x
Hardware: Sun All
: P2 blocker with 2 votes (vote)
Assignee: Jiri Rechtacek
URL:
Keywords: I18N
Depends on:
Blocks:
 
Reported: 2005-04-20 19:38 UTC by Unknown
Modified: 2007-03-30 00:15 UTC (History)
4 users (show)

See Also:
Issue Type: ENHANCEMENT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Unknown 2005-04-20 19:38:25 UTC
Currently a separate module nbm (xx.nbm, xx_ja.nbm) needs to be preapred for
each locale. The module jars themselves are i18ned and localized. The nbms have
to be different only because info.xml is not i18ned. Autoupdate client should
provide the ability to localize info.xml (info.xml, ifo_ja.xml etc) so that one
nbm can be prepared for all locales and the client should use the relevant
info.xml for a given locale.
Comment 1 Ken Frank 2007-03-22 21:25:48 UTC
is this about having info.xml in uc l10n or product l10n kits ?

That has been a request from translators for a long time;
if its not I can open separate issue on that - perhaps under nbbuild ?

ken.frank@sun.com
Comment 2 bugbridge 2007-03-22 21:33:54 UTC
This issue is certainly about having info.xml as part of the repository (which
would enable l10n kit process to then make use of it). I myself think we can
discuss all aspects of info.xml (checking it into repository, building multiple
nbms , using them in kits etc) in this bug itself, at least for the initial
conversation. Creating a separate issue and linking the two issues should also
be fine.

We should also start considering building ml nbms as per
http://platform.netbeans.org/articles/how-to-do-localization.html .
Comment 3 Ken Frank 2007-03-22 21:39:36 UTC
As to the other parts you mention, is it that current ways of building localized
uc or product nbms need to be changed ?  If so, then perhaps there needs
to be separate rfe in nbbuild category, since I think RE handles that.

as to getting info.xml into repos, you are right - it cant be in kit until it gets
in repos - would this category be correct one for solving that ?

ken.frank@sun.com
Comment 4 Jiri Rechtacek 2007-03-22 22:13:21 UTC
I'm surprise seeing that at least since NB5.0 and later there is a possibility
to read localized text from localized info.xml. For example if a module's NBM
has the structure:
-- Info
   |
   \--- info.xml
     |
     \--- locale
       |
       \--- info_ja.xml
        --- info_br.xml
then AU client read info by active locale. I guess I have written about this
feature earlier. I'm sorry I should resolve as FIXED long time ago.

But I wonder this feature could be helpful much because it comes in work if and
only if Autoupdate client reads locally downloaded NBMs. In common case when
Autoupdate reads a catalog.xml on some Update Center then all information are
obtained from catalog.xml. Unfortunately catalog.xml has no capability like
info.xml. I guess that the reason why each locale has own localized catalog.

I close the RFE about info.xml as FIXED for now, please reopen with more
clarified requirement or file an another RFE if these feature is not enough. Thanks
Comment 5 Ken Frank 2007-03-22 23:06:54 UTC
yes  i think localized info.xml shows as per locale -- but I think this issue
was really about

having info.xml in cvs so that it could be included in l10n kits.

Jirka, I can file a new issue - but where to I file it ?
I can file under nbbuild to get it built into kits but that assumes its
in each module's cvs.

But would there be one category to cover for all modules ?

or is it a nbtask or tteam kind of topic ?

and is it feasible that info.xml could be in the cvs ?

Thanks for your guidance with these questions.

ken.frank@sun.com
Comment 6 Karthikeyan Rajeswaran 2007-03-26 07:24:44 UTC
Please also see: http://www.netbeans.org/issues/show_bug.cgi?id=98893
Comment 7 khu 2007-03-30 00:15:39 UTC
The fix was verified by the following testcase (usinng NB55):
1. build a local nbm, for example, org-netbeans-api-web-webmodule.nbm (i.e.
web/webapi)
2. unzip the nbm
3. create the locale directory within Info, as following (as suggested by
jrechtacek)
 Info
   |
   \--- info.xml
     |
     \--- locale
       |
       \--- info_ja.xml
        
5. run NB55 in English Locale. 
6. using UC client to load the nbm and view the "Description" and
   License Agreement
7. run NB55 again in Ja locale
8. Repeat step 6, and I can see the "Description" and "License Agreement" comes 
   from info_ja.xml 

I will colse the bug as verified.