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 32273 - I18N - Empty profile menu is not localizable
Summary: I18N - Empty profile menu is not localizable
Status: VERIFIED FIXED
Alias: None
Product: obsolete
Classification: Unclassified
Component: vcsgeneric (show other bugs)
Version: -S1S-
Hardware: Sun Solaris
: P1 blocker (vote)
Assignee: Martin Entlicher
URL:
Keywords: I18N
Depends on:
Blocks:
 
Reported: 2003-03-25 10:12 UTC by ohsumi
Modified: 2003-04-02 04:21 UTC (History)
2 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
I have attached the snapshot on Solaris. (65.86 KB, image/gif)
2003-03-25 10:13 UTC, ohsumi
Details
The text patch with respect to release35 branch. (16.52 KB, patch)
2003-03-27 09:19 UTC, Martin Entlicher
Details | Diff
The binary patch, that fix this issue. (3.60 KB, application/octet-stream)
2003-03-27 09:21 UTC, Martin Entlicher
Details
I have attached Bundle_ja.properties (English msg) for testing. (1.08 KB, text/plain)
2003-03-28 01:24 UTC, ohsumi
Details
Screenshot of localized menu (62.96 KB, image/jpeg)
2003-03-28 08:56 UTC, Richard Gregor
Details

Note You need to log in before you can comment on or make changes to this bug.
Description ohsumi 2003-03-25 10:12:07 UTC
When I created the 'Empty' profile in 'New Wizard
- Generic VCS',
the context menu of created Empty filesystem
appears in English.

This occurs in both Solaris 9 and Windows 2000.
Tested build is Nevada build 030323 and I added
_ja.jar files to it.

Steps:
1. run IDE in ja locale
2. select 'Versioning' -> 'Mount Version Control'
-> Generiv VCS
3. select 'Empty (Unix)' on Sol9 or select 'Empty
(Windows) on win2k
4. click 'Finish'
   At this point, 'Empty /xxx/yyy' is mounted on
Explore.
5. right-click 'Empty /xxx/yyy' on Explore

The menu 'Empty' and the context menu of Empty
appear in English.

   Empty --> Refresh
             Refresh Recursively
             Check in
             Check out
             Lock
             Unlock
             Add
             Remove


These menu items seem to come from the following
files and be hard-coded.

vcsgeneric/src/org/netbeans/modules/vcs/profiles/config/emptyUnix.xml
vcsgeneric/src/org/netbeans/modules/vcs/profiles/config/emptyWin.xml
    <command name="ROOT" displayName="Empty">
    <command name="LIST" displayName="Refresh">
    <command name="LIST_SUB" displayName="Refresh
Recursively">
    <command name="CHECKIN" displayName="Check
in">
    <command name="CHECKOUT" displayName="Check
out">
    <command name="LOCK" displayName="Lock">
    <command name="UNLOCK" displayName="Unlock">
    <command name="ADD" displayName="Add">
    <command name="REMOVE" displayName="Remove">
Comment 1 ohsumi 2003-03-25 10:13:52 UTC
Created attachment 9512 [details]
I have attached the snapshot on Solaris.
Comment 2 Martin Entlicher 2003-03-25 10:54:17 UTC
That's true. However the Empty profile is there for users, who need to
create a new profile for version control system that we do not
support. I'm not sure whether it's really necessary to localize it,
because the profile is not really functional anyway. It's expected
that the user will edit the profile.

However if you feel like it should be localized, it's not too hard to
do it.
Comment 3 ohsumi 2003-03-25 11:55:21 UTC
I am sorry that I have filed this before I understand a function of
the Empty profile.

I verified that I can create my profile using the Empty profile. I
think it would be better that menu items of
created filesystem are translated without clicking the
'Edit Commands' button (in short, withtou editing label of
each properties). 

Is it possible the changes that displayName in emptyUnix.xml and
emptyWin.xml will come from Bundle.properties?
I do not know the implementation, so this may be no make sence.

Comment 4 Martin Entlicher 2003-03-26 18:02:33 UTC
> Is it possible the changes that displayName in emptyUnix.xml and
> emptyWin.xml will come from Bundle.properties?

Yes, it is possible. I've fixed it in the main trunk:

Checking in emptyUnix.xml;
/cvs/vcsgeneric/src/org/netbeans/modules/vcs/profiles/config/emptyUnix.xml,v 
<--  emptyUnix.xml
new revision: 1.3; previous revision: 1.2
done
Checking in emptyWin.xml;
/cvs/vcsgeneric/src/org/netbeans/modules/vcs/profiles/config/emptyWin.xml,v 
<--  emptyWin.xml
new revision: 1.3; previous revision: 1.2
done
RCS file:
/cvs/vcsgeneric/src/org/netbeans/modules/vcs/profiles/config/Bundle.properties,v
done
Checking in Bundle.properties;
/cvs/vcsgeneric/src/org/netbeans/modules/vcs/profiles/config/Bundle.properties,v 
<--  Bundle.properties
initial revision: 1.1
done

I guess this is necessary for NB 3.5 as well. Considering that this is
a very low risk I hope I'll get an approval. In order I can get an
approval it must be a showstopper ( == P1 priority). So I'm upgrading
this to P1 - our software must be localizable.

Comment 5 Martin Entlicher 2003-03-27 09:19:54 UTC
Created attachment 9552 [details]
The text patch with respect to release35 branch.
Comment 6 Martin Entlicher 2003-03-27 09:21:53 UTC
Created attachment 9553 [details]
The binary patch, that fix this issue.
Comment 7 Martin Entlicher 2003-03-27 09:24:27 UTC
The binary patch attached.
To apply: create folder patches/org-netbeans-modules-vcs-advanced in
"modules" folder in the NetBeans 3.5 installation directory and copy
the attached Patch32273.jar into that folder:

cp Patch32273.jar \
netbeans/modules/patches/org-netbeans-modules-vcs-advanced

Then restart NetBeans.
Comment 8 ohsumi 2003-03-28 01:22:10 UTC
Thank you for creating the patch.

I tested with the following steps for Nevada build, 
but I was not able to see japanese messages.

1. create Bundle_ja.properties and add it to Patch32273.jar
2. create the directory org-netbeans-modules-vcs-advanced
   in /opt/studio5_se/modules/patches
3. copy Patch32273.jar that has ja file to created directory
4. run runide.sh

Could you please tell me what I should do?
Comment 9 ohsumi 2003-03-28 01:24:57 UTC
Created attachment 9583 [details]
I have attached Bundle_ja.properties (English msg) for testing.
Comment 10 Richard Gregor 2003-03-28 08:54:55 UTC
Hi,

I have just reviewed code. Fix is ease. 

I built vcsegeneric module with files patched with attached patch,
used attached Bundle_ja.properties and run release35 build with
vcsgen.jar module and vcsgen_ja.jar. In ja locale it shows localized
ja labels, so I think it is correct. 

I didn't try attached binary patch. Shouldn't be there localized
module patch containig Bundle_ja.properties somewhere inside the
locale subdir? Or there could be also problem that simply restart IDE
is not enough - you usually need to change userdir to see changed
profile.  

Anyway, from my point of view reviewed without objections.

Comment 11 Richard Gregor 2003-03-28 08:56:54 UTC
Created attachment 9586 [details]
Screenshot of localized menu
Comment 12 _ ttran 2003-03-28 09:04:35 UTC
approved for 3.5
Comment 13 ohsumi 2003-03-28 09:48:04 UTC
When I created vcsgen.jar and vcsgen_ja.jar and run IDE,
I was able to see translated messages.
When I tried this yesterday, it was not successful.
I think my operation was wrong.

I believe this fix works fine.
Thank you very much for the fix.
Comment 14 Martin Entlicher 2003-03-28 15:24:48 UTC
Thanks for the review and approval. The issue is fixed in release35
branch:

Checking in Bundle.properties;
/shared/data/helm/cvs/repository/vcsgeneric/src/org/netbeans/modules/vcs/profiles/config/Bundle.properties,v 
<--  Bundle.properties
new revision: 1.1.2.1; previous revision: 1.1
done
Checking in emptyUnix.xml;
/shared/data/helm/cvs/repository/vcsgeneric/src/org/netbeans/modules/vcs/profiles/config/emptyUnix.xml,v 
<--  emptyUnix.xml
new revision: 1.2.2.1; previous revision: 1.2
done
Checking in emptyWin.xml;
/shared/data/helm/cvs/repository/vcsgeneric/src/org/netbeans/modules/vcs/profiles/config/emptyWin.xml,v 
<--  emptyWin.xml
new revision: 1.2.42.1; previous revision: 1.2
done
Comment 15 ohsumi 2003-04-02 04:21:26 UTC
We verified that this was fixed in Nevada build 030331.
Thank you very much for fixing this.