- Sort Score
- Num 10 results
- Language All
Results 1 - 10 of 389 for LANGUAGE (0.04 seconds)
-
.github/workflows/translate.yml
- name: Export Language Codes id: show-langs run: | echo "langs=$(python ./scripts/translate.py llm-translatable-json)" >> $GITHUB_OUTPUT echo "commands=$(python ./scripts/translate.py commands-json)" >> $GITHUB_OUTPUT env: LANGUAGE: ${{ github.event.inputs.language }} COMMAND: ${{ github.event.inputs.command }} translate:Created: Sun Dec 28 07:19:09 GMT 2025 - Last Modified: Sat Dec 27 18:48:45 GMT 2025 - 3.6K bytes - Click Count (0) -
pyproject.toml
"Intended Audience :: Developers", "Programming Language :: Python :: 3 :: Only", "Programming Language :: Python :: 3.9", "Programming Language :: Python :: 3.10", "Programming Language :: Python :: 3.11", "Programming Language :: Python :: 3.12", "Programming Language :: Python :: 3.13", "Programming Language :: Python :: 3.14", "Topic :: Internet :: WWW/HTTP :: HTTP Servers",
Created: Sun Dec 28 07:19:09 GMT 2025 - Last Modified: Sat Dec 27 12:54:56 GMT 2025 - 9.3K bytes - Click Count (0) -
docs/pt/llm-prompt.md
### Target language Translate to Portuguese (Português). Language code: pt. For instructions or titles in imperative, keep them in imperative, for example "Import FastAPI" to "Importe o FastAPI". Keep existing translations as they are if the term is already translated.
Created: Sun Dec 28 07:19:09 GMT 2025 - Last Modified: Wed Dec 17 20:41:43 GMT 2025 - 3.1K bytes - Click Count (0) -
docs/uk/llm-prompt.md
### Target language Translate to Ukrainian (українська). Language code: uk. ### Grammar and tone 1) Use polite/formal address consistent with existing Ukrainian docs (use “ви/ваш”). 2) Keep the tone concise and technical. ### Headings 1) Follow existing Ukrainian heading style; keep headings short and instructional. 2) Do not add trailing punctuation to headings. ### Quotes
Created: Sun Dec 28 07:19:09 GMT 2025 - Last Modified: Fri Dec 19 12:51:53 GMT 2025 - 1.4K bytes - Click Count (0) -
docs/zh/llm-prompt.md
### Target language Translate to Simplified Chinese (简体中文). Language code: zh. ### Grammar and tone 1) Use clear, concise technical Chinese consistent with existing docs. 2) Address the reader naturally (commonly using “你/你的”). ### Headings 1) Follow existing Simplified Chinese heading style (short and descriptive). 2) Do not add trailing punctuation to headings.
Created: Sun Dec 28 07:19:09 GMT 2025 - Last Modified: Sat Dec 27 18:49:08 GMT 2025 - 1.4K bytes - Click Count (0) -
.github/workflows/codeql-analysis.yml
matrix: # Override automatic language detection by changing the below list # Supported options are ['csharp', 'cpp', 'go', 'java', 'javascript', 'python'] language: ['java', 'javascript'] # Learn more... # https://docs.github.com/en/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning#overriding-automatic-language-detection steps:Created: Wed Dec 31 11:36:14 GMT 2025 - Last Modified: Thu Dec 11 22:12:03 GMT 2025 - 4K bytes - Click Count (0) -
src/main/java/org/codelibs/fess/helper/LanguageHelper.java
if (doc.containsKey(f)) { language = detectLanguage(DocumentUtil.getValue(doc, f, String.class)); if (language != null) { if (logger.isDebugEnabled()) { logger.debug("set {} to lang field", language); } doc.put(fessConfig.getIndexFieldLang(), language); break; }
Created: Sat Dec 20 09:19:18 GMT 2025 - Last Modified: Fri Nov 28 16:29:12 GMT 2025 - 6.9K bytes - Click Count (0) -
scripts/translate.py
print(f"Updating outdated translations for {language}") update_outdated(language=language) print(f"Adding missing translations for {language}") add_missing(language=language) print(f"Done updating and adding for {language}") @app.command() def make_pr( *, language: Annotated[str | None, typer.Option(envvar="LANGUAGE")] = None,
Created: Sun Dec 28 07:19:09 GMT 2025 - Last Modified: Sat Dec 27 19:05:53 GMT 2025 - 34.1K bytes - Click Count (0) -
tests/test_tutorial/test_response_headers/test_tutorial001.py
Created: Sun Dec 28 07:19:09 GMT 2025 - Last Modified: Wed Dec 17 20:41:43 GMT 2025 - 431 bytes - Click Count (0) -
architecture/standards/0009-use-american-english.md
* **Harder for non-native speakers**: Contributors and users for whom English is a second language benefit from a single, consistent convention While both American and British English are valid, establishing a single standard improves consistency, readability, and maintainability of the codebase. ## Decision
Created: Wed Dec 31 11:36:14 GMT 2025 - Last Modified: Tue Nov 25 07:01:54 GMT 2025 - 3.9K bytes - Click Count (0)