Skip to content

chore(l10n): Sync and Fix zh-TW translations#694

Open
YuevUwU wants to merge 9 commits intoTeamFlos:mainfrom
YuevUwU:zh-TW
Open

chore(l10n): Sync and Fix zh-TW translations#694
YuevUwU wants to merge 9 commits intoTeamFlos:mainfrom
YuevUwU:zh-TW

Conversation

@YuevUwU
Copy link
Contributor

@YuevUwU YuevUwU commented Mar 9, 2026

Glossary

id en-US zh-CN zh-TW Context
multi-export Export 批量导出 打包多個譜面 Export selected (maybe multiple) charts to zip, and able to batch import later [since ba28675]. See below for structure and explanation.
batch-import Batch Import 批量导入 批次匯入 Player can import multi-export-ed zip by regular chart importing, and import all charts in the zip. Phira will detect export.json to recognize it.

Add

Only difference will be listed

  • 请在导出前下载全部谱面。未下载:{ $charts }
    ->請在匯出前下載所有選中的譜面。未下載:{ $charts }
    • Not all, just all selected
  • 检测到批量导入数据,是否导入全部 { $count } 谱面?
    -> 偵測到批次匯入資訊,是否匯入全部 { $count } 譜面?
    • I prefer to describe the trait of exported zip, the metadata (export.json), instead of the data, and also in zh-CN, "批量导入" sounds like a verb.
    • Unify to 個,「多張」 is a little bit weird to me, so....
  • 已经下载过而跳过的谱面:
    -> 已下載而跳過的譜面
    • too long fr

Fix

multi-export:大量匯出 -> 打包多個譜面

Even if player is only select one chart, Phira may still create this structure.
The structure can't be directly imported by "import" (unzip and select is needed).
It's more like a backup feature for data/charts.
Use "打包" and "多個" to make sure players know it will be packed again

Sample Structure:

# even if only 1 chart, the structure is also created
# Player have to unzip if they wants only specific chart in exported zip
phira-export-20260310-203713.zip
├── export.json  # since ba28675, metadata for batch import, not backward-compatible
├── custom  # local charts
│   └── 9008d8f0-c7d6-4a62-931a-262fc06792d2.zip
└── download  # online charts
    └── 2789.zip

export.json

{"exported_at":"2026-03-10T12:37:17.181605200Z","version":"0.6.7"}

still-loadingstill-uploading:正在...… -> 仍在...,請稍候…

still-loading will be triggered if the chart info haven't loaded but you click the play button
Similarly, still-uploading if still uploading but player click retry or proceed button

cancel-not-saved:...確定要取消變更嗎? -> ...確定要還原變更嗎?

This dialog box contains "Confirm" and "Cancel".
If we still use "cancel"(取消) in description, which should player click?

YuevUwU added 4 commits March 9, 2026 22:57
still-loading will be triggered if the chart info haven't loaded but you click the play button
Similarly, still-uploading if still uploading but player click retry or proceed button
This dialog box contains "Confirm" and "Cancel".
If we still use "cancel" in description, which should player click?
Even if player is only select one chart, Phira may still create this structure.
The structure can't be directly imported by "import" (unzip and select is needed).
It's more like a backup feature for data/charts.
Use "打包" to make sure players know it will be packed again

Sample Structure:
phira-export-20260309202902.zip
├── custom
│   └── 9008d8f0-c7d6-4a62-931a-262fc06792d2.zip
└── download
    └── 2789.zip
@YuevUwU YuevUwU marked this pull request as draft March 9, 2026 15:32
@YuevUwU YuevUwU marked this pull request as ready for review March 9, 2026 15:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants