0
Fork 0
mirror of https://github.com/blader/humanizer.git synced 2026-11-10 08:11:56 +00:00

Avoid redundant English glosses in multilingual replies #324

Closed
opened 2026-10-30 07:59:16 +00:00 by KurodaKayn · 0 comments
KurodaKayn commented 2026-10-30 07:59:16 +00:00 (Migrated from github.com)

Example

In Chinese technical writing:

推进虚机热迁移 (VMIM) 状态收敛。

When the reader already knows the term and the acronym is not used later, the parenthetical adds nothing.

The same pattern can appear in other languages. For example, in a Spanish reply about caching:

Actualizaré la caché (cache).

How a person would write it

推进虚机热迁移状态收敛。

Actualizaré la caché.

Keep the gloss when it clarifies the term or helps the reader follow a later reference.

Why no current pattern covers it

Pattern 26, “Re-explaining what the reader knows,” covers replies that repeat familiar background. It does not explicitly mention repeating a familiar term in another language or as an acronym within the same sentence.

A short addition to pattern 26 could cover this case when the conversation establishes that the reader knows the term. This would preserve useful terminology while removing unnecessary repetition.

### Example In Chinese technical writing: > 推进虚机热迁移 (VMIM) 状态收敛。 When the reader already knows the term and the acronym is not used later, the parenthetical adds nothing. The same pattern can appear in other languages. For example, in a Spanish reply about caching: > Actualizaré la caché (cache). ### How a person would write it > 推进虚机热迁移状态收敛。 > Actualizaré la caché. Keep the gloss when it clarifies the term or helps the reader follow a later reference. ### Why no current pattern covers it Pattern 26, “Re-explaining what the reader knows,” covers replies that repeat familiar background. It does not explicitly mention repeating a familiar term in another language or as an acronym within the same sentence. A short addition to pattern 26 could cover this case when the conversation establishes that the reader knows the term. This would preserve useful terminology while removing unnecessary repetition.
Sign in to join this conversation.
No milestone
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
skills/blader-humanizer#324
No description provided.