samba.git/lib/util/charset/tests, branch master

lib/util/tests: avoid some compiler warnings

2014-11-14T22:27:04+00:00

Signed-off-by: Stefan Metzmacher 
Reviewed-by: Jeremy Allison

s4: tests: Added local.charset test for Bug 10716 - smbd constantly crashes when filename contains non-ascii character

2014-08-05T23:05:14+00:00

https://bugzilla.samba.org/show_bug.cgi?id=10716

Signed-off-by: Jeremy Allison

lib/util/tests: add missing #include "torture/local/proto.h"

2014-04-02T07:03:44+00:00

Signed-off-by: Stefan Metzmacher 
Reviewed-by: Andrew Bartlett

charset/tests: Add prototypes for test functions.

2012-02-07T00:11:07+00:00

lib/util/charset: remove charset module loading

2011-09-20T04:27:06+00:00

Now that the 'table' modules are gone, there is no reason for there to
be charset modules at all.  This builds the macosxfs and weird modules
into the binary at the appropriate times, and changes the tests to
test instead the difference between the remaining internal handlers
and iconv().

Andrew Bartlett

Autobuild-User: Andrew Bartlett 
Autobuild-Date: Tue Sep 20 06:27:06 CEST 2011 on sn-devel-104

lib/util/charset: the comparsion must be against our charset modules

2011-09-10T13:45:42+00:00

There is little point testing this against the system iconv.

Andrew Bartlett

Autobuild-User: Andrew Bartlett 
Autobuild-Date: Sat Sep 10 15:45:42 CEST 2011 on sn-devel-104

lib/util/charset Use name of ISO-8859-1 that matches our internal implementation

2011-09-10T12:18:06+00:00

lib/util/charset: Improve toture assertions in iconv test

2011-09-10T12:18:06+00:00

lib/util/charset Run charset sets with and without the system iconv

2011-09-10T12:18:06+00:00

We need to know that we can load the samba-provided modules, and that
they are correct.  However, we must mark a number of tests as
knownfail due to errors in our internal iconv modules.

Andrew Bartlett

lib/util/charset: Remove 'display charset'

2011-06-23T11:47:27+00:00

As discussed in 'CH_DISPLAY and gettext' on the samba-technical list:
http://lists.samba.org/archive/samba-technical/2011-June/078190.html

Setting this to a value other than 'unix charset' does not make sense,
as any system where the filesytem charset does not equal the terminal
charset will already have problems with programs as simple as 'ls'.
It also means that our output could not be pasted as our input in
interactive programs or onto our command line, as we never did
translate in the DISPLAY -> UNIX direction.

The d_printf() calls are retained in case we need to revisit this, and
to support display_set_stderr().

Andrew Bartlett