Skip to content

[Translation] French (FR) & Spanish (ES) - Translate English body content (~69 FR / ~53 ES files) #1095

@pethers

Description

@pethers

🎯 Objective

Translate body content in ~69 French (_fr) and ~53 Spanish (_es) HTML files that currently contain English text despite having localized infrastructure.

📋 Background

French and Spanish are key European market languages. French is particularly impacted with 71% of files containing English body content. Spanish has 55% untranslated content.

French (FR) breakdown:

Category Files with English body Total
Blog articles 20/27 74%
Discordian ISMS 25/43 58%
Product pages 9/10 90%
Industry + ISO 7/7 100%
Core pages 5/5 100%
Total 69/96 71%

Spanish (ES) breakdown:

Category Files with English body Total
Blog articles 20/27 74%
Discordian ISMS 12/43 28%
Product pages 9/10 90%
Industry + ISO 5/7 71%
Core pages 5/5 100%
Total 53/96 55%

French files with explicit "Translation In Progress" markers:

  • blog-automated-convergence_fr.html — contains "This page contains English content pending professional translation"
  • blog-public-isms-benefits_fr.html — contains "⚠️ Translation In Progress"

Note: Spanish discordian files are better translated (only 28% English), suggesting a previous translation batch was partially completed. Blog and product pages remain heavily untranslated in both languages.

✅ Acceptance Criteria

  • All core pages translated for both FR and ES (10 files total)
  • All product pages translated for both FR and ES (18 files total)
  • All industry/ISO pages translated for both FR and ES (~12 files total)
  • All blog articles translated for both FR and ES (~40 files total)
  • Remaining discordian ISMS files translated (25 FR + 12 ES = ~37 files)
  • French translations use proper accented characters (é, è, ê, ë, à, ç, etc.)
  • Spanish translations distinguish between Latin American and European Spanish conventions (prefer European/Castilian)
  • "Translation In Progress" markers removed from all completed files
  • HTML structure, links, images, and metadata remain intact
  • Translations are natural and professional, suitable for a B2B cybersecurity audience

🛠️ Implementation Guidance

Priority order:

  1. Core pages first — services, projects, why-hack23, accessibility-statement, security-assessment-checklist
  2. Product pages — cia-features, black-trigram-features, compliance-manager pages, etc.
  3. Industry + ISO — industries-betting-gaming, industries-cannabis-security, industries-investment-fintech, iso-27001-* pages
  4. Blog articles — blog-* articles (highest volume, 20 each)
  5. Discordian ISMS — discordian-* files (25 FR, 12 ES remaining)

Approach:

  1. Translate <article>/<main> body content from English to target language
  2. Remove any "Translation In Progress" or "pending translation" notices
  3. Keep HTML tags, attributes, links, images, Schema.org data intact
  4. Use existing well-translated files (index_fr.html, index_es.html) as terminology reference
  5. For cybersecurity terms, use standard French/Spanish equivalents (e.g., "cybersécurité"/"ciberseguridad")

🤖 Recommended Agent

Agent: @ui-enhancement-specialist
Rationale: Bulk HTML content translation requiring consistent terminology for European B2B cybersecurity market.

For implementation:

  • Translate body content from English to professional French and Spanish
  • Remove all "pending translation" markers
  • Preserve HTML structure, ARIA attributes, and semantic markup
  • Ensure proper character encoding for accented characters

Metadata

Metadata

Labels

enhancementEnhancement to existing functionality

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions