Added i18n component and related scripts

[yihao03]

run yarn trans to start translation

[yihao03]

breaking changes are made: xml repositories are divided into folders, currently consisting of en and cn folders to store translated content. The same applies to the json folder after running "yarn json". Frontend needs to be changed accordingly to fetch json files from the corresponding url

[arnav-goel10]

You’re casting your OpenAI client to any when calling createAssistant. Remove the as any cast and unify your imports so you only pull in OpenAI from the main package entrypoint. For example:

// i18n/initializers/initialize.ts
import OpenAI from 'openai';

// instead of importing from internal paths:
// import OpenAI from 'openai/index.mjs';

Then simply call:

assistant = await createAssistant(langCode, language, ai);

By using a single import OpenAI from 'openai' everywhere, TypeScript will recognize the same class, eliminating the need for any.

[arnav-goel10]

As mentioned in the previous comment about dropping the ai as any cast, you should also update the import in your initialize.ts to:

import OpenAI from 'openai';

[arnav-goel10]

You should attach an error handler to each stream so file I/O issues (like missing or unreadable files) are caught immediately:

const fileStreams = [path.join(__dirname, '../ai_files', langCode, 'dictionary.txt')].map(
    filePath => {
      const stream = fs.createReadStream(filePath);

      stream.on('error', err => {
          throw new Error(`Failed to read dictionary file at ${filePath}: ${err.message}`);  
      });
      return stream;
  });

This ensures your process fails fast with a clear error instead of silently hanging or emitting later failures.

[arnav-goel10]

openai, sax, and dotenv are not declared in your package.json dependencies, and you also need the Node.js types for TypeScript. You can add them like:

{
  "dependencies": {
    "sicp": "^1.1.4",
    "openai": "^x.y.z",
    "sax": "^x.y.z",
    "dotenv": "^x.y.z"
  },
  "devDependencies": {
    "@types/node": "^x.y.z"
  }
}

That way, running yarn install will automatically pull in those packages and the Node types.

[arnav-goel10]

There is a mismatch between the log filename you write (json-summary-...) and the one you log to the console (translation-summary-...).

[arnav-goel10]

The parameter source is implicitly typed as any. You should add an explicit type annotation.

[arnav-goel10]

There are several magic literals in this file, for example:

• Batch size fallback: max_trans_num = Number(process.env.MAX_TRANSLATION_NO) || 5
• API list limit: await ai.beta.assistants.list({ limit: 100 })
• Filename prefix in logs: translation-summary-
• Timestamp hack: .toISOString().replace(/[:.]/g, "-")

There are more magic values throughout consider extracting them into named constants or a configuration object for better maintainability.

[arnav-goel10]

Catching all errors and returning true can mask real file‑system issues. You should be logging or re‑throwing unexpected errors so you don’t skip translations silently.

[arnav-goel10]

The failureCount variable is declared globally and reused here, so resetting it in the summary section overwrites the failures accumulated during the batch loop rather than keeping them separate. This makes the initial accumulation effectively redundant.

[arnav-goel10]

This file handles a lot of logic and, for example, embeds several magic literals directly:

• MAXLEN = Number(process.env.MAX_LEN) || 3000
• max_trans_num = Number(process.env.MAX_TRANSLATION_NO) || 5
• { limit: 100 } in the API calls
• Log prefixes like "translation-summary-", "json-summary-", "emergency-log-"
• The ignoredTags array

Embedding these values makes configuration harder and ties defaults to code changes.

Proposed changes:

1. Extract config constants

   • Move environment fallbacks, numeric limits, prefixes, and tag arrays into config.ts.
   • This lets you validate required vars and override settings (via .env, CI, etc.) without modifying application code.

2. Modularize by responsibility

   • config.ts: all constants and environment setup
   • logger.ts: error‑logging and summary helpers
   • parser.ts: SAX parser instantiation and XML escaping utilities
   • translator.ts: core translation flow and CLI handling
   • io.ts: file system utilities (directory traversal, stream management)

Breaking the file into focused modules and centralizing configuration will improve readability, testability, and ease of maintenance.