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 10239 - i18n - With Japanese PVCS, the vcs file status is not shown up correctly.
Summary: i18n - With Japanese PVCS, the vcs file status is not shown up correctly.
Status: CLOSED FIXED
Alias: None
Product: obsolete
Classification: Unclassified
Component: vcsgeneric (show other bugs)
Version: 3.x
Hardware: PC Windows ME/2000
: P3 blocker (vote)
Assignee: issues@obsolete
URL:
Keywords: I18N
Depends on:
Blocks:
 
Reported: 2001-03-13 15:20 UTC by Jiri Kovalsky
Modified: 2003-07-01 13:05 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Jiri Kovalsky 2001-03-13 15:20:03 UTC 
Description: 
When you use Japanese PVCS Version Manager, the file status in explorer is not 
shown up correctly. It is always [Local].
The reason is that Japanese PVCS outputs localized strings when IDE 
launch "vlog" command. IDE uses "Workfile" and "Locks" for pattern matching. 
These strings are translated in Japanese PVCS. I localized and changed "Data 
regexp" of LIST command in "Edit Command" dialog, but it does not works. "Data 
regexp" seems not to support multi byte characters.
This problem is only on Windows, because MERANT does not provide localized 
commands on Solaris.

X Evaluation:
Some localizable regular expressions would have to be created, it will need 
some tests to find out whether apache regexp utility will work with it.
Comment 1 Martin Entlicher 2001-04-19 17:37:52 UTC 
Fixed in the main trunk. All keys, that are used for parsing PVCS and VSS
commands output was put to resource bundles.
Comment 2 Martin Entlicher 2001-04-20 18:24:07 UTC 
Fixed in release32 build #34.
Comment 3 dmladek 2001-04-27 11:12:20 UTC 
I'm not able to verify (only from looking into sources maybe) and just believe
it will work.
I'm sending an email to keiichi.oono@japan.sun.com, the reporter of this
original bug in our internal bugtracking system, to ask him/her to verify it.
Comment 4 Jan Chalupa 2001-05-06 15:42:24 UTC 
Target milestone -> 3.2
Comment 5 Unknown 2001-07-27 10:42:37 UTC 
This problem has been fixed by workaround of issue #13748.
Comment 6 Jesse Glick 2002-12-23 16:37:03 UTC 
Consistent use of the I18N keyword.
Comment 7 Quality Engineering 2003-07-01 13:05:11 UTC 
Resolved for 3.4.x or earlier, no new info since then -> closing.