When you create a project in LingoHub, you select a primary platform type (e.g., iOS Strings, Android XML, or Ruby on Rails). LingoHub relies on these platform rules to automatically identify, highlight, and validate placeholders inside the Editor and during automated Quality checks.
If your placeholders are not highlighted or flagged during QA checks, this guide explains why and what you can do.
Why placeholders might not be detected
Custom or non-standard placeholder syntax: If your development team uses custom dynamic placeholders (e.g.,
{custom_variable}) that differ from the standard format expected by the chosen platform, LingoHub will not automatically recognize them.Format-agnostic or loose file conventions: Certain file formats do not have an official, standardized placeholder specification. While LingoHub covers the most common industry best practices, non-standard variations might be skipped.
Mismatched project platform: If the project platform selected during setup does not match the actual syntax used inside your resource files, the detection parser will look for the wrong formatting patterns.
What you can do
Verify your project platform: Ensure your project settings accurately reflect the file format and framework you are uploading.
Contact support for custom syntax rules: If you rely on custom placeholder patterns across your organization, reach out to our team at [email protected]. We can help adjust or configure custom detection patterns for your workspace.
Need more help?
Couldn't find what you were looking for? Reach out to our team at [email protected], and we will gladly assist you.