i18ntk 1.4.0 → 1.4.2

package/docs/release-notes/v1.3.1.md

@@ -1,136 +0,0 @@
-# Release Notes - i18n Management Toolkit v1.3.1
-
-**Release Date:** December 2024  
-**Version:** 1.3.1  
-**Previous Version:** 1.3.0
-
-## 🆕 New Features
-
-### Reset to Default Values Option
-- **New Menu Option**: Added `r) Reset to Default Values` to the settings CLI menu
-- **One-Click Reset**: Reset all directory configurations to their system defaults
-- **Confirmation Prompt**: Includes safety confirmation before proceeding with reset
-- **Safe Operation**: Preserves toolkit functionality while clearing custom configurations
-
-## 🎯 Use Cases for Reset Functionality
-
-The new reset option is particularly useful for:
-
-- **Testing Configurations**: Start fresh when testing different directory setups
-- **Migration Scenarios**: Reset configurations when moving between project structures
-- **Troubleshooting**: Clear potentially problematic custom settings
-- **New Projects**: Quick setup for new projects without manual configuration cleanup
-
-## 🔧 Additional Improvements
-
-### Enhanced Script Output
-- **Source Directory Display**: Added clear display of source directory, source language, and strict mode status at the beginning of analyze and sizing script runs
-- **Absolute Path Display**: Scripts now show resolved absolute paths for better debugging and verification
-- **Configuration Transparency**: Users can immediately see what configuration is being used
-
-### Improved Sizing Analysis
-- **Better Recommendations**: Enhanced translation length difference warnings with more actionable guidance
-- **Clear Guidance**: Sizing recommendations now provide specific, helpful advice instead of generic warnings
-- **User-Friendly Output**: Improved formatting and messaging for better user experience
-
-## 📋 Menu Enhancement
-
-The settings CLI now includes:
-
-```
-Enter new value (or press Enter to keep current): 
-  1) Analyze Script Directories 
-     Current: /src/i18n/locales/test/ 
-  2) Complete Setup Directories 
-     Current: (not set) 
-  3) Initialize Script Directories 
-     Current: (not set) 
-  4) Manage Script Directories 
-     Current: (not set) 
-  5) Sizing Script Directories 
-     Current: (not set) 
-  6) Summary Report Directories 
-     Current: (not set) 
-  7) Usage Report Directories 
-     Current: (not set) 
-  8) Validate Script Directories 
-     Current: (not set) 
-
-  b) Back to main menu
-  r) Reset to Default Values
-
-Select setting to edit (or b for back, r for reset): 
-```
-
-### Enhanced Default Value Handling
-
-**Improved UX**: Instead of leaving fields empty (which isn't possible after changes), users can now:
-
-- **Type "default"**: Restore individual directory settings to system defaults
-- **User-specific defaults**: Defaults adapt to your project directory structure
-- **Granular control**: Reset individual settings without affecting others
-- **Clear guidance**: Explicit "default" keyword instead of ambiguous empty inputs
-
-This enhancement provides:
-- **Better user experience**: Clear, unambiguous way to restore defaults
-- **Flexibility**: Mix custom paths with default values as needed
-- **Project-specific**: Defaults respect your actual project structure
-
-## 🔧 Technical Details
-
-### Reset Behavior
-- **Scope**: Resets all 8 script directory configurations
-- **Defaults**: Restores to system default directory paths
-- **Safety**: Requires explicit user confirmation
-- **Logging**: Logs reset operation for audit purposes
-
-### Compatibility
-- **Backward Compatible**: All v1.3.0 features remain unchanged
-- **No Breaking Changes**: Existing configurations are preserved
-- **Safe Upgrade**: Users can upgrade without configuration loss
-
-## 📚 Documentation Updates
-
-- Updated [Script Directory Guide](../SCRIPT_DIRECTORY_GUIDE.md) with reset functionality
-- Added reset option examples and use cases
-- Updated version references across all documentation
-- Added troubleshooting section for reset scenarios
-
-## 🧪 Testing Recommendations
-
-Before using in production:
-
-1. **Test Reset Function**: Verify reset works correctly with custom configurations
-2. **Backup Configurations**: Consider backing up current settings before reset
-3. **Verify Defaults**: Ensure default directory paths are appropriate for your environment
-4. **Integration Testing**: Test with existing project workflows
-
-## 🔄 Migration from v1.3.0
-
-- **No Migration Required**: v1.3.1 is a minor enhancement
-- **Configuration Preserved**: All existing settings remain intact
-- **New Feature Only**: Reset functionality is additive, not replacement
-
-## 📊 Version History
-
-- **v1.3.1**: Reset to default values option (current)
-- **v1.3.0**: Per-script directory configuration, path resolution fixes
-- **v1.2.x**: Previous stable releases with basic directory support
-
-## 🚀 Getting Started
-
-To use the new reset functionality:
-
-1. Run the settings CLI: `npm run i18ntk:settings`
-2. Navigate to directory configuration
-3. Select `r) Reset to Default Values`
-4. Confirm the reset operation
-5. Verify restored default paths
-
-## ❓ Support
-
-For questions about the reset functionality or any issues:
-
-- Check the [Script Directory Guide](../SCRIPT_DIRECTORY_GUIDE.md)
-- Review [troubleshooting section](../SCRIPT_DIRECTORY_GUIDE.md#troubleshooting)
-- Open an issue on GitHub for technical problems

package/docs/reports/ANALYSIS_README.md

@@ -1,17 +0,0 @@
-# Translation Analysis Reports
-
-This folder contains translation analysis reports generated by the i18nTK analysis tools.
-
-## Report Types
-
-- **translation-analysis-*.json** - Detailed translation completeness analysis
-- **language-comparison-*.json** - Language-to-language comparison reports
-- **missing-keys-*.txt** - Lists of missing translation keys
-
-## File Naming Convention
-
-```
-{report-type}-{timestamp}.{extension}
-```
-
-Example: `translation-analysis-2025-01-24T10-30-00-000Z.json`

package/docs/reports/CONSOLE_MISMATCH_BUG_REPORT_v1.5.0.md

@@ -1,181 +0,0 @@
-# 🐛 Console Language Mismatch Bug Report - v1.5.0
-
-**Date**: January 26, 2025  
-**Version**: 1.5.0  
-**Reporter**: AI Agent  
-**Priority**: High  
-**Status**: Open  
-**Related**: TRANSLATION_BUG_REPORT_v1.5.0.md
-
-## 📋 Summary
-
-Mixed English text detected in foreign language JSON files, causing console output language inconsistencies and poor user experience for non-English users.
-
-## 🔍 Issue Details
-
-### Affected Languages and Files
-
-#### 🇫🇷 French (FR) - `ui-locales/fr.json`
-**Mixed Language Entries Found:**
-- Line 879: `"prompt": "Select Débogage option (0-4): "` (English "Select" + French "Débogage")
-- Line 897: `"prompt": "Souhaitez-vous to set up an admin PIN? (y/N): "` (French + English mix)
-- Line 898: `"enterPin": "Entrer le PIN administrateur (4-8 digits): "` (French + English "digits")
-- Line 899: `"confirmPin": "Confirmerer admin PIN: "` (Broken French + English "admin PIN")
-- Line 900: `"invalidPin": "PIN must be 4-8 digits only. Veuillez réessayer."` (English + French mix)
-- Line 902: `"success": "Admin PIN has been set up Succèsfully!"` (English + broken French)
-- Line 903: `"enabled": "Admin protection is now enable..."` (English text)
-- Line 904: `"error": "Erreur setting up admin PIN:"` (French + English mix)
-- Line 905: `"continuing": "Continuing without admin PIN protection."` (Full English)
-- Line 906: `"skipped": "Skipping Configuration du PIN administrateur. You ..."` (English + French mix)
-- Line 909: `"authenticated": "You are now authenticated for this session."` (Full English)
-- Line 910: `"ended": "Admin session ended. Goodbye!"` (Full English)
-- Line 911: `"failed": "Authentication Échec. Accès refusé."` (English + French mix)
-
-#### 🇪🇸 Spanish (ES) - `ui-locales/es.json`
-**Mixed Language Entries Found:**
-- Line 166: `"sizing": "Analyze translation Archivo sizes and character counts"` (English + Spanish mix)
-- Line 167: `"debug": "Ejecutar Herramientas de depuración for system Análisis"` (Spanish + English mix)
-- Line 208: `"prompt": "Seleccione un idioma (1-7) o 0 para Cancelararar: "` (Broken Spanish)
-- Line 876: `"prompt": "Select Depurar opción (0-4): "` (English "Select" + Spanish)
-- Line 888: `"description": "Admin PIN protection Agregars secu..."` (English + broken Spanish)
-- Line 895: `"enterPin": "Ingrese PIN de administrador (4-8 digits): "` (Spanish + English "digits")
-- Line 896: `"confirmPin": "Confirmarar admin PIN: "` (Broken Spanish + English)
-- Line 897: `"invalidPin": "PIN must be 4-8 digits only. Por favor intente de nuevo."` (English + Spanish mix)
-- Line 899: `"success": "Admin PIN has been set up Éxitofully!"` (English + broken Spanish)
-- Line 900: `"enabled": "Admin protection is now enable..."` (English text)
-- Line 902: `"continuing": "Continuing without admin PIN protection."` (Full English)
-- Line 903: `"skipped": "Skipping Configuración de PIN de administrador. You ..."` (English + Spanish mix)
-- Line 906: `"authenticated": "You are now authenticated for this session."` (Full English)
-- Line 907: `"ended": "Admin session ended. Goodbye!"` (Full English)
-- Line 908: `"failed": "Authentication Falló. Acceso denegado."` (English + Spanish mix)
-
-#### 🇩🇪 German (DE) - `ui-locales/de.json`
-**Mixed Language Entries Found:**
-- Line 155: `"description": "Dieses Tool hilft Ihnen bei der Verwaltung der InternationalisieAusführeng (i18n) für Ihr Projekt."` (Broken German word)
-- Line 167: `"sizing": "Analyze translation Datei sizes and character counts"` (English + German mix)
-- Line 168: `"debug": "Ausführen Debug-Werkzeuge for system Analyse"` (German + English mix)
-- Line 170: `"options": "OptionEN:"` (Broken German)
-- Line 424: `"excludedFiles": "Ausgeschlossene Dateien: {Dateis}"` (Broken German variable)
-- Line 782: `"errors": "Fehler: {{Fehlers}}"` (Broken German variable)
-- Line 906: `"skipped": "Admin-PIN-Einrichtung überspAusführengen. Sie..."` (Broken German)
-- Line 911: `"failed": "AuthentifizieAusführeng fehlgeschlagen. Zugriff verweigert."` (Broken German)
-
-## 🚨 Impact Assessment
-
-### User Experience Impact
-- **Critical**: Users see mixed language console output
-- **Confusing**: Inconsistent terminology and broken translations
-- **Professional**: Reduces perceived quality and professionalism
-- **Accessibility**: Poor experience for non-English speakers
-
-### Technical Impact
-- **Console Output**: Mixed language messages in admin PIN setup
-- **Debug Mode**: Inconsistent language in debug prompts
-- **Error Messages**: Mixed language error reporting
-- **Authentication**: Confusing authentication messages
-
-## 🔧 Root Cause Analysis
-
-### Primary Causes
-1. **Incomplete Translation**: Many strings were partially translated
-2. **Copy-Paste Errors**: English text copied without translation
-3. **Template Issues**: Translation templates contained mixed content
-4. **Quality Control**: Insufficient review of translated content
-5. **Automated Processing**: Some automated translations were incomplete
-
-### Secondary Issues
-1. **Broken Words**: German compound words incorrectly split
-2. **Grammar Errors**: Incorrect verb conjugations and word forms
-3. **Variable Naming**: Inconsistent variable name translations
-4. **Punctuation**: Missing or incorrect punctuation in translations
-
-## 🎯 Immediate Actions Required
-
-### High Priority (Fix Immediately)
-1. **Admin PIN Messages**: Fix all admin PIN setup and authentication messages
-2. **Debug Prompts**: Correct all debug mode prompts and options
-3. **Error Messages**: Ensure all error messages are properly translated
-4. **Core UI Elements**: Fix main menu and navigation prompts
-
-### Medium Priority (Fix Soon)
-1. **Help Text**: Review and correct all help and description text
-2. **Status Messages**: Fix progress and status reporting messages
-3. **Configuration Text**: Correct settings and configuration messages
-
-### Low Priority (Fix Later)
-1. **Variable Names**: Standardize variable name translations
-2. **Formatting**: Improve text formatting and punctuation
-3. **Consistency**: Ensure terminology consistency across files
-
-## 🛠️ Recommended Solutions
-
-### Immediate Fixes
-```bash
-# 1. Create clean translation templates
-node dev/debug/console-key-checker.js
-
-# 2. Manual review and correction of critical messages
-# Focus on admin PIN, debug, and error messages
-
-# 3. Run validation after fixes
-node main/i18ntk-validate.js
-```
-
-### Quality Assurance Process
-1. **Native Speaker Review**: Have native speakers review translations
-2. **Context Testing**: Test translations in actual console output
-3. **Consistency Checks**: Ensure terminology consistency
-4. **Grammar Validation**: Verify proper grammar and syntax
-
-### Prevention Measures
-1. **Translation Guidelines**: Create detailed translation guidelines
-2. **Review Process**: Implement mandatory review for all translations
-3. **Testing Protocol**: Test console output in all languages
-4. **Automated Checks**: Add automated checks for mixed language content
-
-## 📁 Files Requiring Immediate Attention
-
-### Critical Files
-- `ui-locales/fr.json` - 13+ mixed language entries
-- `ui-locales/es.json` - 15+ mixed language entries  
-- `ui-locales/de.json` - 8+ broken/mixed entries
-
-### Backup Files (Also Affected)
-- `ui-locales/fr.backup.json`
-- `ui-locales/es.backup.json`
-- `ui-locales/de.backup.json`
-
-## 🔍 Detection Commands
-
-### Find Mixed Language Content
-```bash
-# Search for English words in foreign language files
-grep -r "[a-zA-Z]" ui-locales/fr.json | grep -E "(Select|Admin|PIN|Error|Success|Authentication)"
-grep -r "[a-zA-Z]" ui-locales/es.json | grep -E "(Select|Admin|PIN|Error|Success|Authentication)"
-grep -r "[a-zA-Z]" ui-locales/de.json | grep -E "(Select|Admin|PIN|Error|Success|Authentication)"
-
-# Find broken words or formatting
-grep -E "[A-Z][a-z]+[A-Z]" ui-locales/*.json
-```
-
-## 📞 Next Steps
-
-1. **Assign Language Experts**: Assign native speakers for each affected language
-2. **Create Fix Schedule**: Prioritize fixes based on user impact
-3. **Implement Review Process**: Establish translation review workflow
-4. **Test Console Output**: Verify fixes in actual console environment
-5. **Update Documentation**: Update translation guidelines and processes
-
-## 🔗 Related Issues
-
-- **TRANSLATION_BUG_REPORT_v1.5.0.md**: Missing translation keys
-- **Console Translation Support**: Part of v1.5.0 console internationalization
-- **Admin PIN Security**: Related to enhanced security features
-
----
-
-**Note**: This bug report identifies critical language consistency issues that significantly impact user experience. These issues should be prioritized for immediate resolution to maintain the professional quality of the v1.5.0 release.
-
-**Generated**: January 26, 2025 at 03:00 UTC  
-**Report ID**: CONSOLE-MISMATCH-2025-002  
-**Severity**: High - User Experience Impact

package/docs/reports/SIZING_README.md

@@ -1,18 +0,0 @@
-# Sizing Analysis Reports
-
-This folder contains sizing analysis reports generated by the i18nTK sizing analysis tools.
-
-## Report Types
-
-- **sizing-analysis-*.json** - Detailed file size analysis
-- **sizing-analysis-*.csv** - CSV format for spreadsheet analysis
-- **size-comparison-*.json** - Language size comparison reports
-- **optimization-suggestions-*.txt** - Size optimization recommendations
-
-## File Naming Convention
-
-```
-{report-type}-{timestamp}.{extension}
-```
-
-Example: `sizing-analysis-2025-01-24T10-30-00-000Z.json`

package/docs/reports/SUMMARY_README.md

@@ -1,18 +0,0 @@
-# Summary Reports
-
-This folder contains comprehensive summary reports generated by the i18nTK summary tools.
-
-## Report Types
-
-- **summary-report-*.json** - Complete project summary
-- **language-overview-*.json** - Language-specific overviews
-- **project-health-*.json** - Overall project health reports
-- **completion-status-*.json** - Translation completion status
-
-## File Naming Convention
-
-```
-{report-type}-{timestamp}.{extension}
-```
-
-Example: `summary-report-2025-01-24T10-30-00-000Z.json`

package/docs/reports/TRANSLATION_BUG_REPORT_v1.5.0.md

@@ -1,129 +0,0 @@
-# 🐛 Translation Bug Report - v1.5.0
-
-**Date**: January 26, 2025  
-**Version**: 1.5.0  
-**Reporter**: AI Agent  
-**Priority**: Medium  
-**Status**: Open  
-
-## 📋 Summary
-
-Missing translations detected in Spanish (ES) and Japanese (JA) language files during v1.5.0 documentation update and validation process.
-
-## 🔍 Issue Details
-
-### Missing Translation Keys
-
-- **Spanish (ES)**: 484 missing translation keys
-- **Japanese (JA)**: 408 missing translation keys
-- **Total Impact**: 892 missing translations across 2 languages
-
-### Affected Languages
-
-✅ **Complete Translations**:
-- German (DE) - ✅ 523/523 keys
-- French (FR) - ✅ 523/523 keys  
-- Russian (RU) - ✅ 523/523 keys
-- Chinese (ZH) - ✅ 523/523 keys
-
-❌ **Incomplete Translations**:
-- Spanish (ES) - ❌ 39/523 keys (484 missing)
-- Japanese (JA) - ❌ 115/523 keys (408 missing)
-
-## 🛠️ Actions Taken
-
-1. ✅ **Detection**: Ran `node dev/debug/console-key-checker.js`
-2. ✅ **Backup Creation**: Automatic backups created for all affected files
-3. ✅ **Key Addition**: Missing keys added with `[NOT TRANSLATED]` placeholders
-4. ✅ **Partial Translation**: Ran `node utils/native-translations.js`
-   - ES: 15 translations replaced
-   - JA: 1 translation replaced
-   - Total: 16 automatic replacements
-
-## 📊 Current Status
-
-### Remaining Work Required
-
-- **Spanish (ES)**: ~469 keys still need manual translation
-- **Japanese (JA)**: ~407 keys still need manual translation
-- **Total**: ~876 keys requiring human translation
-
-## 🎯 Recommended Actions
-
-### Immediate (High Priority)
-1. **Review Critical UI Elements**: Focus on main menu, error messages, and core functionality
-2. **Validate Existing Translations**: Ensure current translations are contextually appropriate
-3. **Update Translation Guidelines**: Enhance language-specific guidelines for ES and JA
-
-### Short Term (Medium Priority)
-1. **Complete ES Translations**: Prioritize Spanish due to higher missing count
-2. **Complete JA Translations**: Focus on Japanese technical terminology
-3. **Quality Assurance**: Review automated translations for accuracy
-
-### Long Term (Low Priority)
-1. **Automated Translation Pipeline**: Implement better automation for future updates
-2. **Translation Memory**: Build translation memory for consistency
-3. **Community Contributions**: Consider community translation contributions
-
-## 📁 Files Affected
-
-### Spanish (ES)
-- `ui-locales/es.json` - 484 missing keys added
-- Backup: `ui-locales/es.backup.json`
-
-### Japanese (JA)
-- `ui-locales/ja.json` - 408 missing keys added  
-- Backup: `ui-locales/ja.backup.json`
-
-## 🔧 Technical Details
-
-### Detection Method
-```bash
-node dev/debug/console-key-checker.js
-```
-
-### Translation Processing
-```bash
-node utils/native-translations.js
-```
-
-### Validation Commands
-```bash
-node main/i18ntk-validate.js
-node main/i18ntk-analyze.js
-```
-
-## 📈 Impact Assessment
-
-### User Experience Impact
-- **Spanish Users**: May see `[NOT TRANSLATED]` placeholders in console output
-- **Japanese Users**: May see `[NOT TRANSLATED]` placeholders in console output
-- **Functionality**: Core functionality remains unaffected
-- **Severity**: Medium (cosmetic/UX issue, not functional)
-
-### Development Impact
-- **Console Output**: Non-English console messages may display placeholders
-- **Documentation**: All documentation remains in English (unaffected)
-- **Core Features**: All core i18n toolkit features work correctly
-
-## 🚀 Next Steps
-
-1. **Assign Translation Tasks**: Assign ES and JA translation tasks to appropriate team members
-2. **Create Translation Schedule**: Establish timeline for completion
-3. **Quality Review Process**: Implement review process for new translations
-4. **Testing Protocol**: Test translated console output in target languages
-5. **Documentation Update**: Update AGENTS.md with new translation patterns
-
-## 📞 Contact Information
-
-- **Bug Reporter**: AI Agent (Automated Detection)
-- **Technical Lead**: [To be assigned]
-- **Translation Coordinator**: [To be assigned]
-
----
-
-**Note**: This bug report was automatically generated during the v1.5.0 documentation update process. The missing translations do not affect core functionality but impact user experience for Spanish and Japanese users.
-
-**Generated**: January 26, 2025 at 02:57 UTC  
-**Report ID**: TRANS-BUG-2025-001  
-**Export File**: `missing-keys-2025-07-26T02-57-47-103Z.json`

package/docs/reports/USAGE_README.md

@@ -1,18 +0,0 @@
-# Usage Analysis Reports
-
-This folder contains usage analysis reports generated by the i18nTK usage analysis tools.
-
-## Report Types
-
-- **usage-analysis-*.txt** - Detailed usage analysis reports
-- **unused-keys-*.json** - Lists of unused translation keys
-- **missing-keys-*.json** - Lists of missing translation keys
-- **dynamic-keys-*.json** - Dynamic key detection reports
-
-## File Naming Convention
-
-```
-{report-type}-{timestamp}.{extension}
-```
-
-Example: `usage-analysis-2025-01-24T10-30-00-000Z.txt`

package/docs/reports/VALIDATION_README.md

@@ -1,18 +0,0 @@
-# Translation Validation Reports
-
-This folder contains validation reports generated by the i18nTK validation tools.
-
-## Report Types
-
-- **validation-report-*.json** - Detailed validation results
-- **validation-errors-*.txt** - Lists of validation errors
-- **validation-warnings-*.txt** - Lists of validation warnings
-- **structural-issues-*.json** - Structural inconsistency reports
-
-## File Naming Convention
-
-```
-{report-type}-{timestamp}.{extension}
-```
-
-Example: `validation-report-2025-01-24T10-30-00-000Z.json`