summaryrefslogtreecommitdiff
path: root/website/src/docs/features/japanese-conversion.md
diff options
context:
space:
mode:
Diffstat (limited to 'website/src/docs/features/japanese-conversion.md')
-rw-r--r--website/src/docs/features/japanese-conversion.md12
1 files changed, 10 insertions, 2 deletions
diff --git a/website/src/docs/features/japanese-conversion.md b/website/src/docs/features/japanese-conversion.md
index ec1df1b..d98ac87 100644
--- a/website/src/docs/features/japanese-conversion.md
+++ b/website/src/docs/features/japanese-conversion.md
@@ -19,8 +19,11 @@ Conversion is performed in two stages.
Input: konnichiha sekai
Stage 1: こんにちは せかい
Stage 2: こんにちは 世界
+Sent: konnichiha sekai §e(こんにちは 世界)
```
+The original text is **not** replaced. What you typed is kept, and the conversion result is appended in parentheses, so both are visible to everyone who receives the message.
+
## Conversion Targets
- Normal chat
@@ -48,7 +51,7 @@ Conversion results are cached per word. When the same word is converted again, t
| `cache.saveIntervalSeconds` | `300` | Interval for saving to disk (seconds) |
| `cache.filePath` | `"conversion_cache.json"` | Path to the cache file |
-When the cache reaches its limit, the oldest 10% of entries are automatically removed.
+When the cache reaches its limit, 10% of the entries are removed. Which entries are dropped is not defined: the in-memory cache is unordered, so eviction is effectively arbitrary rather than oldest-first.
## API Settings
@@ -56,6 +59,11 @@ Settings related to the connection to the Google IME API.
| Setting Key | Default | Description |
|-------------|---------|-------------|
-| `api.timeout` | `3000` | Request timeout (milliseconds) |
+| `api.timeout` | `3000` | Timeout for a single API request (milliseconds) |
If the API times out or fails, the message is sent in hiragana as-is.
+
+> [!WARNING]
+> Independently of `api.timeout`, converting one message is given an overall budget of **1000 ms**. When that budget runs out the conversion is abandoned and the message is sent exactly as typed, with nothing appended.
+>
+> Because the overall budget is shorter than the default `api.timeout`, raising `api.timeout` above `1000` has no practical effect.