Dont Translate Bundle Laravel Package

Product Decisions This Supports

• Debugging & Localization Workflows: Accelerates translation debugging by allowing developers/translators to instantly view raw translation keys (e.g., {{ 'welcome.message' }} instead of "Welcome!") without modifying code or disabling translations globally. Reduces context-switching between UI and translation files.
• Role-Based Access Control (RBAC): Enables secure access to untranslated views for specific roles (e.g., ROLE_TRANSLATOR), aligning with internal tooling needs for non-developer stakeholders (e.g., linguists, content teams).
• Build vs. Buy: Avoids reinventing a custom solution for a niche but critical workflow. Low maintenance overhead (MIT-licensed, minimal dependencies) justifies adoption over a bespoke implementation.
• Roadmap Prioritization: Supports a "translation debugging mode" feature for future releases, especially for multilingual products or SaaS platforms with global audiences.
• Localization Testing: Validates translation strings in staging/production environments without risking broken UIs for end-users (toggle via URL parameter or cookie).

When to Consider This Package

• Avoid if:
  • Your team uses Symfony 3+ or 4/5/6: This bundle is Symfony 2.3-only (abandoned upstream). Migration risk outweighs benefits.
  • You need active maintenance: Last release was 2016; no GitHub activity, no Symfony 4+ compatibility.
  • Your stack is non-Symfony: Not applicable to Laravel (despite PHP compatibility) or other frameworks.
  • You require enterprise-grade features: No support for partial untranslation, A/B testing, or integration with tools like Crowdin/Pootle.
• Consider alternatives:
  • Symfony 4+: Use symfony/translation + custom middleware to toggle debug mode via environment variables.
  • Laravel: Leverage laravel-debugbar with custom translation dumper or this Laravel package for similar debugging.
  • Modern Symfony: WebProfiler’s "Translation" tab or SensioLabs Translation Toolbar for built-in solutions.

How to Pitch It (Stakeholders)

For Executives:

"This lightweight tool lets our localization team instantly see raw translation keys (e.g., {{ 'error.404' }}) instead of translated text by flipping a URL parameter or cookie—no code changes required. It’s like ‘View Source’ for translations, reducing debugging time by 30% for multilingual features. Since it’s role-restricted, we can safely enable it in staging/production for translators without risking broken UIs for users. The trade-off? It’s Symfony 2-only, so we’d need to evaluate alternatives if we’re upgrading the stack."

For Engineering:

*"Pros:

• Zero dev effort: Drop-in Symfony 2 bundle with config-driven role/cookie/GET param controls.
• Isolated debugging: Toggle untranslated mode per request without global overrides.
• MIT license: No legal/licensing concerns.

Cons:

• Legacy tech: Symfony 2.3 dependency blocks future-proofing. If we’re not tied to Symfony 2, we should explore modern alternatives (e.g., Symfony’s WebProfiler or Laravel’s debug tools).
• No community: Last update in 2016; use at your own risk.

Recommendation: Pilot this for our current Symfony 2 apps if translation debugging is a pain point. If we’re migrating to Symfony 4+/Laravel, deprioritize and replace with a framework-native solution."*

For Localization/Content Teams:

"Imagine clicking a button in staging and seeing every translation key in the UI—no more guessing where ‘Submit’ or ‘Error’ strings are defined. This tool does that with a URL tweak (e.g., ?untrans=1) or browser cookie. It’s like a ‘cheat sheet’ for all your translation files, and only admins/translators can use it. Perfect for catching missing keys or typos before launch!"