Skip to main content

​
Checklist

Quetzal is designed to work with all stacks and all localization patterns. However, there are still some requirements.

​
Translatable Content

Quetzal is meant to be used to translate static strings defined in your codebase. For anything else, you can use our API. This means UI Strings, documents of pure text, and other strings defined in files of code. Images, user generated strings, or other strings encountered at runtime are not in the scope of these tools.

​
Supported Formats

At present, Quetzal works with the following stacks:
  • Javascript/Typescript
  • Next.js/React
  • Swift
  • Kotlin
  • Java
  • Python
  • HTML/XML
  • Text documents (.txt, .mdx, etc.)
At this time, we do NOT support:
  • Vue/Svelte
Quetzal is designed to handle all stacks gracefully. As such, if your framework is not listed, but you are interested, please reach out. We are excited to bring Quetzal to life for your stack.

​
Supported Translation Libraries

Quetzal should work with all translation libraries and patterns. However, Quetzal may struggle to navigate anti-patterns if your localization framework is poorly set up or poorly defined. If you are using a translation framework that has limited capabilities, Quetzal may struggle to localize properly given the constraints. Common blindspots of weak localization patterns include:
  • Pluralization
  • Dynamic content
  • Fragile string keying mechanism
  • Fragmented strings
Most reputable translation mechanisms will handle this fine. Check out our tips on choosing a framework. During initial setup, you can review and update a generated LOCALIZATION.md file to align Quetzal with the practices that work best for your team.

​
Raw Text files

Our support for translated content in raw text content is currently in beta. If you have documentation, blog posts, or other files written as text or markdown where multiple versions exist for each locale, Quetzal may struggle to hook into the required mechanisms. Monitor such an integration closely to ensure the initial behavior is correct.