- Updated `ResourceQuota` to count device class requests within a `ResourceClaim` as two additional quotas when the `DRAExtendedResource` feature is enabled:
  - `requests.deviceclass.resource.k8s.io/<deviceclass>` is charged based on the worst-case number of devices requested.

            if (c == '"') {
                if (inQuotes && i + 1 < line.length() && line.charAt(i + 1) == '"') {
                    // Escaped quote
                    currentField.append('"');
                    i++; // Skip next quote
                } else {
                    // Toggle quote state
                    inQuotes = !inQuotes;
                }
            } else if (c == delimiter && !inQuotes) {

### Headings

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

### Quotes

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

### Ellipsis

1) Keep ellipsis style consistent with existing Ukrainian docs.

* **Proper nouns and quotes**: Names of organizations, products, or quoted text that use different conventions

## Status

ACCEPTED

## Consequences

### Positive Consequences

* **Improved consistency**: The codebase has a uniform language standard

 * 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 {

### Headings

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

### Quotes

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

### Ellipsis

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

Por causa disso, o próprio **FastAPI** fornece uma documentação alternativa da API (usando ReDoc), que você pode acessar em <a href="http://127.0.0.1:8000/redoc" class="external-link" target="_blank">http://127.0.0.1:8000/redoc</a>:

<img src="/img/tutorial/path-params/image02.png">

La persona que diseña el prompt puede elegir si quiere convertir comillas neutras a comillas tipográficas. También está bien dejarlas como están.

Consulta por ejemplo la sección `### Quotes` en `docs/de/llm-prompt.md`.

////

## Comillas en fragmentos de código { #quotes-in-code-snippets }

//// tab | Prueba

`pip install "foo[bar]"`

Ejemplos de literales de string en fragmentos de código: `"this"`, `'that'`.

* terminal: terminal (femenine, as in "la terminal")
* terminals: terminales (plural femenine, as in "las terminales")
* lifespan: lifespan (do not translate to "vida útil" or "tiempo de vida")
* unload: quitar de memoria (do not translate to "descargar")
* mount (noun): mount (do not translate to "montura")
* mount (verb): montar
* statement (as in code statement): statement (do not translate to "declaración" or "sentencia")

    A single backtick – «`»

"triple backticks"

    Three backticks in a row – «```»

"neutral double quote"

    The character «"»
    Unicode U+0022 (QUOTATION MARK)

"neutral single quote"

    The character «'»
    Unicode U+0027 (APOSTROPHE)

"English double typographic quotes"

    The characters «“» and «”»