![]() ![]() > In SmartCVS 7 under project->Settings on the Text File Encoding tab there are some options you can try. > TortoiseCVS handles the Unicode mode fine though. > it's a matter of incorrect UTF-8 handling). > replaced by two completely incorrect characters, so you can tell that > filenames with non-ASCII characters (all instances of 'å', > the server to Unicode mode and then doing a CVS update corrupted all > I don't think any automagic conversion takes place with clients that Least until someone releases a usable C-to-JVM compiler) Libraries or binaries in a cross-platform java app (it breaks the wholeĬoncept of Java), so in this particular case it's inevitable. it inevitably causes these compatibility problems.Īs stated above, it's not possible to simply replace some binary.Ībout reinventing the wheel. I've no idea why so many programmers think it's a good idea to re-invent the wheel. In fact I've just had a quick look and this does appear to be the case. If SmartCVS is using some embedded Java client then you'll need to contact SmartCVS for a fix, though we may be able to 'workaround' the bug if we can identify the client from the connection string on the server. > If possible just replace the CVS version on the Mac client with the latest CVSNT and you should be able to run the CVSNT server in Unicode mode, this would be a good 'workaround' for your fileattr problem. Library is included with the distribution. I can't tell which particular version is being used. With NetBeans (so I would expect NetBeans to behave badly with UTF-8ĬVSNT servers as well, but I have not tested that). SmartCVS seems to be using the Java based CVS client library that comes app directory for SmartCVS (eg: SmartCVS.app). The CVS client verion will either be some embeded java thing, the 'standard' one in /usr/bin or embedded in the. WinCVS, TortoiseCVS and MacCvsX all include CVSNT - I imagine that SmartCVS is including some very very broken version of CVS that is claiming to support UTF8 filenames but isn't. > SmartCVS is a GUI - what I need is the CVS version. Vendor should address, and problem 1 to be the server's issue. I would expect problem 2 to be something that the particular CVS client > 2) some CVS clients get corrupt filenames when server running in UTF8 mode > 1) fileattr filenames are not UTF8 when CVSNT Server is not running in UTF8 mode > There are two parts to the 'problem' you have reported, and they both need investigating: > I don't think the clients are the problem here though. > I have used two different clients while getting this error, SmartCVS My apologies.Īll the previous attachments along with two new ones (trace logs) have Thunderbird was playing tricks on me, not sorting that mail in theĬorrect folder, so it appeared to be a private mail. > Try and keep the thread on the newsgroup - just send the attachments only to support at since the newsgroup will reject them. For assistance please contact: Pre-sales Technical support via email to Arthur,
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |