Lab 1.1: Workspace Setup & File Integrity

Objective

In this hands-on lab, you will configure your editing workspace, create and manage plain-text localization assets across a nested directory tree in Visual Studio Code, and verify that file extensions and relative paths remain intact without accidental OS corruption (.json.txt).

Required Setup & Prerequisites

• Editor: Visual Studio Code installed.

• OS Setting: Filename extensions toggled ON in your system settings.

• Working Directory: Create an empty folder on your desktop named loc_lab_1-1.

Step-by-Step Instructions

Step 1: Open the Working Directory in VS Code

1. Launch Visual Studio Code.

2. Open your newly created folder:

   • macOS: Press Cmd + O (or File > Open Folder...) and select loc_lab_1-1.

   • Windows: Press Ctrl + K then Ctrl + O (or File > Open Folder...) and select loc_lab_1-1.

3. Verify that the Explorer Panel on the left displays LOC_LAB_1-1 as the active root directory.

Step 2: Build the Directory Tree Structure

1. In the VS Code Explorer panel, hover over LOC_LAB_1-1 and click the New Folder icon.

2. Create the following folder structure:

Step 3: Create Plain-Text Localization Assets

1. Software UI Asset:

   • Right-click software folder New File.

   • Name: ui_en-US.json

   • Paste content:

     json
     {
       "btn_save": "Save Changes",
       "btn_cancel": "Cancel"
     }

2. Game Localization Asset:

   • Right-click games folder New File.

   • Name: dialogue_en.csv

   • Paste content:

     key,character,text
     dlg_001,Hero,"Welcome to the kingdom!"
     dlg_002,NPC,"Watch your step."

3. Linear Media Subtitle Asset:

   • Right-click media folder New File.

   • Name: captions_en.vtt

   • Paste content:

     WEBVTT
     
     00:00:01.000 --> 00:00:04.000
     Welcome to the global localization program.

Step 4: Safely Rename Assets Without Appending .txt

1. In the Explorer panel under assets/loc/software/, right-click ui_en-US.json and select Rename (or press F2).

2. Change the filename to ui_strings_en-US.json.

3. Ensure the .json extension is explicitly preserved and that no secondary extension (such as .json.txt) is appended.

Step 5: Verify File Extensions and Relative Pathways

1. Select ui_strings_en-US.json in the Explorer panel.

2. Open the Command Palette (Cmd + Shift + P on macOS / Ctrl + Shift + P on Windows).

3. Type Copy Relative Path and press Enter.

4. The relative path copied to your clipboard should match exactly: assets/loc/software/ui_strings_en-US.json.

Self-Verification Checklist

• Filename extensions are explicitly visible for every file in the VS Code Explorer.

• No files contain doubled extensions (e.g., ui_strings_en-US.json.txt).

• The relative folder hierarchy strictly follows assets/loc/[vertical]/[file].

• All three assets contain clean plain-text data without rich-text formatting.