Where I would sniff first
Organized by what you are trying to buy. Each source tells you what to ask for.
DTP work is where translated text becomes a finished, print or screen ready document. These sources help you specify script support, layout, and print readiness, and spot where things commonly go wrong.
The neutral authority on PDF/X and print production specifications. Use this when your deliverable is print: ask the freelancer which PDF/X standard they output, and whether they handle bleed, crop marks, embedded fonts, and preflight. This is your reference for whether a file is actually press ready.
The authority on character encoding and script support, the foundation of all multilingual typesetting. Relevant when you need confidence that a freelancer can handle a specific script correctly: missing glyphs and encoding errors usually trace back here.
Explains why different scripts (Arabic and Hebrew RTL, CJK, Indic) need specific layout support. Use this to understand why RTL or Indic typesetting is a specialized skill, not a font swap, so you brief and budget it accordingly.
Engineering is the invisible layer that prepares files for translation and puts them back together correctly. These sources help you ask the right questions about formats and locale handling.
XLIFF is the core interchange format of localization engineering. Ask whether the freelancer can prepare and protect XLIFF, and protect tags, so content survives the round trip into translation tools and back without corruption.
The authoritative source of locale data: date, number, currency, and plural formatting per locale. Use this when your product must behave correctly in each market: ask whether the freelancer handles locale-sensitive formatting, not just text.
Foundational and technical. For software and web, the Techniques, Tutorials, and Tests material explains what properly internationalized software should do. Useful when you want to check whether software was built to be localizable in the first place.
Accessibility work is often legally required, so the standards matter and buyers should specify them explicitly. This is the clearest-standard area on LPN.
The global benchmark for digital accessibility. Use this when asking for web or digital accessibility conformance: ask the freelancer which WCAG version and conformance level they target, for example WCAG 2.2 AA.
The industry body behind PDF/UA (ISO 14289), the standard for accessible PDF. Use this when your deliverable is an accessible PDF: ask whether the freelancer produces PDF/UA conformant files and validates them, not just "tagged" PDFs.
The official US government resource on Section 508. Relevant if you sell to, or are, a US public-sector body, or a contractor to one. Its Create Accessible Documents guidance is something you can point a vendor to directly.
The key European accessibility standard for ICT products and services, central to EU public procurement. Most relevant for European buyers (including German public-sector work): specify EN 301 549 conformance when procuring in the EU.
Localizing a course means adapting text, audio, and interactions while keeping it deployable in a learning system. These standards govern packaging and tracking.
The originator and steward of SCORM and xAPI. Use this when your course must run in an LMS: ask which standard the freelancer packages to (SCORM 1.2, SCORM 2004, xAPI), and confirm it matches your LMS.
The modern standard for tracking learning, including activity outside a traditional LMS. Relevant when you need richer completion or interaction data than SCORM captures.
An xAPI profile for LMS-launched content, positioned as the SCORM successor. Useful to know when modernizing course delivery: ask whether the freelancer can deliver cmi5 if your platform supports it.
Media work covers subtitling, captioning, dubbing, and audio description. Two buyer concerns: legal accessibility, and platform-grade quality.
The W3C standard for subtitle and caption interchange, the streaming-industry technical profile. Use this to specify delivery format: ask which timed-text format and version the freelancer delivers.
Buyer-planning guidance on captions, subtitles, audio description, and transcripts, what each is and when you need it. Use this to decide which accessibility deliverables your project actually requires before briefing.
US-specific legal and regulatory guidance for television captioning. Relevant if you distribute broadcast content in the US.
Platform-specific, not a universal standard, but a widely used practical quality reference for subtitling and SDH (reading speed, line treatment, timing). Useful as a quality bar to point to, while remembering it is one platform's house style, not law.
QA on LPN is broader than translation accuracy. It spans linguistic QA, functional and UI testing, layout QA, subtitle QC, and deliverable checks. No single standard covers all of it, so specify what kind of QA you need.
The open, widely adopted framework for evaluating translation and localization quality through error types and severity. Use this when you want a structured quality score rather than a subjective verdict: ask whether the freelancer evaluates against an MQM-based typology.
Process and procurement guidance for translation services (roles, workflow, qualifications). It defines a service process, not a complete QA framework. Useful in procurement to specify a baseline process.
Production management is the coordination layer: scheduling multilingual production, managing handoffs between translators, engineers, DTP, QA, and clients, and checking the final delivery package. There is no single universal standard, so these are industry references, not a certification.
Process and procurement guidance that frames how translation and localization projects are run (roles, workflow, records). Useful as a baseline for what an organized production process looks like.
The leading neutral industry association. Its knowledge base covers localization processes, vendor coordination, and production workflow. Use it to understand how multi-discipline localization production is organized, beyond just translation.
Still stuck? Email contact@lpn.network and a human will help you find the right specialist.
