// Test special characters in message
        String message = "Special chars: \n\t\r\"'<>&{}[]()!@#$%^&*";

        SearchQueryException exception = new SearchQueryException(message);

        assertEquals(message, exception.getMessage());
    }

    @Test
    public void test_unicodeInMessage() {
        // Test unicode characters in message

	// ErrInvalidEncryptionKeyID returns error when KMS key id contains invalid characters
	ErrInvalidEncryptionKeyID = Errorf("KMS KeyID contains unsupported characters")
)

var (
	errMissingInternalIV            = Errorf("The object metadata is missing the internal encryption IV")

        assertEquals(mockNotifyInfo2, response2.getNotifyInformation().get(0));
    }

    @Test
    @DisplayName("Test NotifyResponse with special characters in filenames")
    void testNotifyResponseWithSpecialCharactersInFilenames() {
        // Create notifications with special characters
        FileNotifyInformation unicodeFile = mock(FileNotifyInformation.class);

        assertEquals("value3", param.getValues()[2]);
        assertNull(param.getValues()[3]);
    }

    @Test
    public void test_constructor_withSpecialCharacters() {
        // Test with special characters in name and values
        String name = "param-name_123!@#";
        String[] values = { "value with spaces", "value@special#chars", "日本語" };
        RequestParameter param = new RequestParameter(name, values);

import org.dbflute.optional.OptionalEntity;

/**
 * Character mapping file handler for managing character mapping dictionaries.
 * This class provides functionality to load, parse, and manage character mapping
 * rules that define how input characters should be transformed to output characters
 * during text analysis and search processing.
 *
 * Character mapping files contain mapping rules in the format:
 * input1,input2,... => output

JSON can only contain UTF-8 encoded strings, so it can't contain raw bytes.

Base64 can encode binary data in strings, but to do it, it needs to use more characters than the original binary data, so it would normally be less efficient than regular files.

Use base64 only if you definitely need to include binary data in JSON, and you can't use files for that.

    fi
  done
  echo "$basedir"
)
}

# concatenates all lines of a file and replaces variables
# Uses Java-based parser to handle all special characters correctly
# This avoids shell parsing issues with pipes, quotes, @, and other special characters
# and ensures POSIX compliance (no xargs -0, awk, or complex sed needed)
# Set MAVEN_DEBUG_SCRIPT=1 to enable debug logging
concat_lines() {
  if [ -f "$1" ]; then

     </dependency>
     ```


## Version 3.3.1

_2016-05-28_

 *  Fix: The plaintext check in HttpLoggingInterceptor incorrectly classified
    newline characters as control characters. This is fixed.
 *  Fix: Don't crash reading non-ASCII characters in HTTP/2 headers or in cached
    HTTP headers.
 *  Fix: Retain the response body when an attempt to open a web socket returns a
    non-101 response code.

		bugLogIf(GlobalContext, err)
		return nil
	}
	return buf.Bytes()
}

// Use this encodeResponseList() to support control characters
// this function must be used by only ListObjects() for objects
// with control characters, this is a specialized extension
// to support AWS S3 compatible behavior.
//
// Do not use this function for anything other than ListObjects()

                    "Should throw IllegalArgumentException for non-hex character in UUID string");
        }

        @Test
        @DisplayName("Constructor with too short UUID string should parse available data")
        void testConstructorWithStringTooShort() {
            // Arrange - UUID string missing last two characters
            String shortUuid = "00112233-4455-6677-8899-AABBCCDDEE";

            // Act