jobs/job000325

job000325

michael_mirman (Michael Mirman)
Michael Mirman created this job 10 years ago, modified by Perforce maintenance 6 years ago
Closed
In 2015.1, setting P4CHARSET=none should be treated just as not setting P4CHARSET.
This is how it's done at least in P4 and (fixed in January 2015) in P4V.
However, P4Perl still has this problem: if P4CHARSET=none, almost any P4 API will fail with the message
Unicode clients require a unicode enabled server
Unfortunately, there is no API to unset P4CHARSET.
SetCharset('') or SetCharset(undef) return an error (invalid value).
Status
Closed
Project
p4perl
Severity
B
Reported By
Michael Mirman
Reported Date
10 years ago
Modified By
Perforce maintenance
Modified Date
6 years ago
Owned By
paul_allen
Type
Bug
paul_allen (Paul Allen)
Paul Allen commented 9 years ago

Fixed in change @19372
Reply
michael_mirman (Michael Mirman)
Michael Mirman commented 9 years ago

Wonderful! Thank you, Paul!
Reply
paul_allen (Paul Allen)
Paul Allen commented 9 years ago

Thanks, do let me know how you get on with the new release.
Reply