// Text with comma gets quoted, but parse preserves quotes
        input = "with,comma";
        escaped = KuromojiCSVUtil.quoteEscape(input); // "with,comma"
        parsed = KuromojiCSVUtil.parse(escaped);
        assertEquals(1, parsed.length);
        assertEquals("\"" + input + "\"", parsed[0]); // Quotes are preserved

        // Text with quotes gets escaped quotes, but escaped quotes don't get unquoted

func (qi *QuotedIdentifier) Capture(values []string) error {
	// Remove enclosing quotes
	n := len(values[0])
	r := values[0][1 : n-1]

	// Translate doubled quotes
	*qi = QuotedIdentifier(strings.ReplaceAll(r, `""`, `"`))
	return nil
}

// Types representing AST of SQL statement. Only SELECT is supported.

// Select is the top level AST node type
type Select struct {

        // Default constructor
    }

    /**
     * Quotes a string value if it contains spaces.
     * Multi-word values are wrapped in double quotes with internal quotes replaced by spaces.
     *
     * @param value the string value to quote
     * @return the quoted string if it contains spaces, otherwise the original value
     */
    protected String quote(final String value) {
        if (value.split("\\s").length > 1) {

			return r
		default:
			valid = false
			return -1
		}
	}, name)

	if valid {
		// check for simple name or quoted name
		// - letter/underscore followed by one or more letter/digit/underscore
		// - any text between quotes (text cannot contain a quote itself)
		if match, err := regexp.MatchString("^[a_][a0_$]*$", cleaned); err != nil {
			return err
		} else if match {
			return nil
		}
	}

### Headings

- Follow existing Ukrainian heading style; keep headings short and instructional.
- Do not add trailing punctuation to headings.

### Quotes

- Prefer Ukrainian guillemets «…» for quoted terms in prose, matching existing Ukrainian docs.
- Never change quotes inside inline code, code blocks, URLs, or file paths.

### Ellipsis

- Keep ellipsis style consistent with existing Ukrainian docs.

### Headings

- Follow existing Turkish heading style (Title Case where used; no trailing period).

### Quotes

- Keep quote style consistent with existing Turkish docs (typically ASCII quotes in text).
- Never modify quotes inside inline code, code blocks, URLs, or file paths.

### Ellipsis

- Keep ellipsis style (`...`) consistent with existing Turkish docs.

	}
	return s
}

// quoteChar formats c as a quoted character literal
func quoteChar(c byte) string {
	// special cases - different from quoted strings
	if c == '\'' {
		return `'\''`
	}
	if c == '"' {
		return `'"'`
	}

	// use quoted string with different quotation marks
	s := strconv.Quote(string(c))
	return "'" + s[1:len(s)-1] + "'"

 * This avoids the complexity of parsing special characters (pipes, quotes, etc.) in scripts.
 *
 * Usage: java JvmConfigParser.java <jvm.config-path> <maven-project-basedir> [output-file]
 *
 * If output-file is provided, writes result to that file (avoids Windows file locking issues).
 * Otherwise, outputs to stdout.
 *
 * Outputs: Single line with space-separated quoted arguments (safe for batch scripts)
 */
public class JvmConfigParser {

            token == null -> {
              // Value is "double-quoted". That's valid and our regex group already strips the quotes.
              parameter.groups[3]!!.value
            }

            token.startsWith('\'') && token.endsWith('\'') && token.length > 2 -> {
              // If the token is 'single-quoted' it's invalid! But we're lenient and strip the quotes.
              token.substring(1, token.length - 1)
            }

### Headings

- Follow existing Korean heading style (short, action-oriented headings like “확인하기”).
- Do not add trailing punctuation to headings.

### Quotes

- Keep quote style consistent with the existing Korean docs.
- Never change quotes inside inline code, code blocks, URLs, or file paths.

### Ellipsis

- Keep ellipsis style consistent with existing Korean docs (often `...`).