Age | Commit message (Collapse) | Author | Files | Lines |
|
unicode bit set differently to capabilities
(This used to be commit 34a0821e087810381996f5ff6cf3b4d7b9bb53a0)
|
|
macros to STR_
(This used to be commit 95c9e4e0ba8f37f565aaf136f41eb76489441ff7)
|
|
it now handles -M LANMAN1 -f '.x' -m '?x' nicely
(This used to be commit e7ccb9be6da9b1426eb136b4a0a1171232471768)
|
|
(This used to be commit 339bcfd05d3260a123ccf3c06429da6bfe621f74)
|
|
the whole of libsmb should now do unicode where appropriate
(This used to be commit ac7529d2b69826f8214d5632c31778cc87216653)
|
|
enabled by default
you can disable it by setting the environment variable CLI_FORCE_ASCII
(This used to be commit 4d59c08c5e6f54c0d6ced7650750cb987e77b6c9)
|
|
interface for ascii-only fields
(This used to be commit cdf0316610803e6743936b29f232b32f9ec81422)
|
|
(This used to be commit 5b2ef8a1b914265c6072c968d2dad7d26c2aeffc)
|
|
(This used to be commit bdce09b77807c80281c1e169b7c4813c9238fbe3)
|
|
(This used to be commit ba3ce3404e1cd2e9da3ba1708f6fc8a12c085ef2)
|
|
I've currently got this code disabled by default as it is
incomplete. You enable it by setting a USE_UNICODE environment
variable. Once the support is complete this check will be removed and
the CAP_UNICODE capability bit will be the sole determination of
whether the client library code uses unicode
right now I have converted session_setup and tconx. I will do more fns
over the next few days.
see clistr.c for the new client side string interface. Luckily it
tends to make the code smaller and neater while adding unicode
support.
(This used to be commit e1a04e621f1c28d8e6e543d43741ca0272e2237f)
|