Community
Participate
Working Groups
Custom server encodings are not included in the project set and there is no way to set the encoding when a project set is imported. This may cause problems for user's whose repository encoding differs from their client encoding (i.e. pathnames could be mangled on chackout). One solution is to allw the user to set the encoding when they are prompted for the authentication information when improting a project set. Another possibility is to include the encoding in the project set. It may be benefitial to have the concept of variables or settings in the project set itself. Clients (i.e. repository providers) could save and retrieve settings in the project set through the serialization context.
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.
