M1 Diagnostic: Workspace & File Integrity Pre-Flight Check

Overview & Objective

Before advancing to Module 2: Respecting Global Alphabets & Accents, you must pass this Module 1 Diagnostic Pre-Flight Check.

This multi-part exercise tests your ability to setup an environment, recover from file-system corruptions, sanitize rich-text errors in VS Code, and ensure relative path integrity across all three core localization verticals (Software, Video Games, and Linear Media).

Scenario Briefing

You have received an urgent localization drop from an external client team containing localized assets for a global product launch. The project manager reports multiple build failures:

1. The automated pipeline cannot locate the software UI string file.

2. The game localization string table causes syntax parsing crashes on launch.

3. The linear media subtitle track exhibits improper line breaks and hidden file extensions.

Your task is to open the project folder in VS Code, diagnose every technical fault, repair the files, and verify them against the pre-flight requirements.

Part 1: Hands-On Diagnostic Execution

Step 1: Environment Setup

1. Download or create a root working folder named module_1_diagnostic.

2. Open module_1_diagnostic in Visual Studio Code (Cmd + O on macOS / Ctrl + K Ctrl + O on Windows).

3. Ensure system file extensions are explicitly visible in your operating system.

Step 2: Diagnosing & Repairing Asset #1 (Software UI)

• File Location: assets/loc/software/ui_strings_fr.json.txt

• Issues Present: Secret .txt appended extension; typographical "smart" quotes (“ ”) breaking JSON syntax.

1. Inspect the filename in the VS Code Explorer panel.

2. Rename the file to remove .txt, preserving strictly ui_strings_fr.json.

3. Open ui_strings_fr.json in VS Code and inspect the contents:

   JSON

   ui_strings_fr.jsonjson
   {
     “title_main”: “Bienvenue dans l'application”,
     “btn_continue”: “Continuer”
   }

4. Use VS Code Replace (Cmd + Option + F on macOS / Ctrl + H on Windows) to globally replace all curly quotes (“ and ”) with standard straight quotes (").

5. Verify that VS Code displays zero red syntax warnings and that the status bar shows UTF-8 encoding and JSON language mode.

Step 3: Diagnosing & Repairing Asset #2 (Game UI String Table)

• File Location: assets/loc/games/quest_dialogue_de.json

• Issues Present: Unescaped inner quotes in dialogue text causing JSON string boundary breaks.

1. Open quest_dialogue_de.json in VS Code:

   JSON

   quest_dialogue_de.jsonjson
   {
     "quest_01": "Er sagte: "Willkommen!" und ging weiter.",
     "btn_accept": "Akzeptieren"
   }

2. Locate the unescaped inner quotes around "Willkommen!" on line 2.

3. Insert backslash escape characters (\) before each inner quotation mark:

   JSON

   quest_dialogue_de.jsonjson
   {
     "quest_01": "Er sagte: \"Willkommen!\" und ging weiter.",
     "btn_accept": "Akzeptieren"
   }

4. Save the file (Cmd + S / Ctrl + S).

Step 4: Diagnosing & Repairing Asset #3 (Linear Media Subtitles)

• File Location: assets/loc/media/intro_subtitles_es.vtt

• Issues Present: Long caption lines stretching off-screen horizontally; unverified line breaks.

1. Open intro_subtitles_es.vtt in VS Code.

2. Enable Word Wrap (Option + Z on macOS / Alt + Z on Windows) to ensure long caption lines wrap visually within the active editor viewport without creating horizontal scrollbars.

3. Verify that the Status Bar displays UTF-8 encoding.

Part 2: Auto-Graded Diagnostic Quiz

Answer the following questions based on your completed diagnostic execution.

Diagnostic Verification Checklist

• [ ] ui_strings_fr.json has no appended .txt extension and contains standard straight quotes (").

• [ ] quest_dialogue_de.json contains escaped inner quotes (\"Willkommen!\") with zero syntax errors.

• [ ] intro_subtitles_es.vtt is saved in UTF-8 format with Word Wrap enabled (Option+Z / Alt+Z).

• [ ] All quiz questions answered correctly with 100% score threshold.