A Vietnamese Filename and Folder Naming Specification for 14+ Document-Engineering Education: Diacritics, Unicode Normalization, and Cross-Platform Robustness

Document Engineering Volume 1 introduces 14+ Vietnamese learners to the file system as the first programmable substrate they encounter outside a programming language. The volume requires a naming convention that is operationally defensible: testable, teachable inside ten pages, and robust under the deployment conditions Vietnamese learners actually face — Windows-dominant school computers, increasing macOS share at home, Linux on cheap secondary hardware, OneDrive and Google Drive as the de-facto sync backplane, and ZIP as the dominant transport for capstone submissions. This paper synthesises the relevant standards (Unicode Standard Annex #15 on normalization forms; the POSIX portable filename character set in IEEE Std 1003.1-2017; RFC 8264 PRECIS; ISO 9660 / Joliet / UDF; Microsoft NTFS naming guidance; Apple HFS+ and APFS Unicode handling), the VietnameseIT context (TCVN 6909:2001 for Vietnamese characters in IT, Unicode Vietnamese precomposed-letter coverage in the Latin Extended-B / Additional blocks, and the historical TCVN3 / VNI / VPS / VIQR legacy), and the academic literature on filename and naming conventions in software engineering and CSCW. Empirical pain points are tested across the matrix Windows 11 × macOS 14 × Ubuntu 24.04 × OneDrive sync × Google Drive web upload × ZIP transport, with the canonical filename Báo cáo cuối kỳ ‐‐‐ Lê Quang Thật.docx and three further test strings exercising NFC versus NFD divergence, forbidden ASCII characters, and ZIP CP437 versus UTF-8 encoding. The contribution is a fourteen-rule naming specification — ASCII-safe core with diacritics permitted in display position, NFC mandatory, hyphenand-underscore separator hierarchy, ISO 8601 date prefix, semantic version suffix, archive-safe transliteration variant for transport — accompanied by a worked-examples set (capstone, science fair, Vietnamese-typography essay, code repository) and a discussion of the test matrix that a future validation script must cover. The specification is teachable in a single Vol 1 chapter, operationally testable, and aligned with the standards cited above. No empirical study with minors is conducted; the audit loop is the quality bar per program scope.