We’re setting up our translation infrastructure for Coupa eProcurement. As we’ve been deep in design discussions I’ve been reflecting on the technical differences between National Language Support, or NLS, and Multiple Language Support, or MLS. They both start with externalized strings for prompts and field titles. But MLS adds the complexity of worrying about entered data, not just prompts. A typical rule is to take all the content that could be sent to a supplier - from Item Description to UOM to the Supplier name itself - and including an optional placeholder for typing in multiple values, one for each language.. But doing that and keeping the application simple for single-language customers is really tough. So we’ve yet to decide whether Coupa will offer MLS or just stick to NLS.
Download Coupa Express
Latest Blog Posts
- Coupa Exhibits at ISM’s 93rd Annual Conference
- Recession-Proofing Your Business Through Disciplined Purchasing
- The Battle Over Efficiency vs. Quality vs. Cost In Hospitals and Clinics
- Open Source and On Demand Working For e-Procurement
- Price Change for Coupa e-Procurement Hosted Service
- Coupa e-Procurement Express Surpasses 11K Downloads
Recent Forum Activity
Coupa Mascot
Meet Mia, Coupa's office dog!

MLS vs. NLS
Published by Dave Stephens on November 19th, 2006.
This entry was posted on Sunday, November 19th, 2006 at 12:00 am and is filed under Uncategorized. You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site.
