[{"data":1,"prerenderedAt":312},["ShallowReactive",2],{"kc-/knowledge/multilingual-forms":3,"kc-clusters-/knowledge/multilingual-forms":116,"kc-related-/knowledge/multilingual-forms":117},{"id":4,"title":5,"author":6,"body":7,"date":80,"description":81,"draft":82,"extension":83,"faqs":84,"image":94,"isPillar":82,"meta":95,"navigation":96,"path":97,"pillar":98,"pillarName":99,"seo":100,"sources":101,"stem":109,"tags":110,"takeaways":114,"updated":80,"__hash__":115},"knowledge/knowledge/multilingual-forms.md","How to Build Multilingual Forms","RoundPushPin Team",{"type":8,"value":9,"toc":72},"minimark",[10,14,19,31,35,47,51,57,61],[11,12,13],"p",{},"A multilingual form presents the same questions to respondents in their own language while collecting every answer into one consistent dataset. Done well, it widens your reach without multiplying your maintenance — done badly, it becomes a pile of forks that drift apart.",[15,16,18],"h2",{"id":17},"whats-the-difference-between-translating-and-localizing-a-form","What's the difference between translating and localizing a form?",[11,20,21,25,26,30],{},[22,23,24],"strong",{},"Translation converts the text; localization adapts the experience."," The W3C distinguishes the two clearly: localization includes formats (dates, numbers), conventions, and structure appropriate to a locale — not just translated words. A genuinely multilingual form gets translated questions ",[27,28,29],"em",{},"and"," locale-appropriate formats and examples.",[15,32,34],{"id":33},"why-not-just-duplicate-the-form-per-language","Why not just duplicate the form per language?",[11,36,37,40,41,46],{},[22,38,39],{},"Because each language copy becomes a separate thing to maintain, and they drift."," Change a question in the English form and the other nine fall behind. The scalable pattern is a ",[42,43,45],"a",{"href":44},"/knowledge/one-template-many-versions","single master template"," with language layered on top, so the questions stay identical across languages and only the wording changes.",[15,48,50],{"id":49},"how-do-you-keep-multilingual-responses-comparable","How do you keep multilingual responses comparable?",[11,52,53,56],{},[22,54,55],{},"Map every language version to the same underlying question."," When the Spanish \"¿Cuál es tu rol?\" and the English \"What is your role?\" both write to the same typed column, responses from all languages land in one dataset you can analyze together — instead of separate spreadsheets per language that you later have to reconcile.",[15,58,60],{"id":59},"how-roundpushpin-handles-multilingual-forms","How RoundPushPin handles multilingual forms",[11,62,63,66,67,71],{},[22,64,65],{},"RoundPushPin translates your master template into 10+ languages automatically, so you don't rewrite questions per language or hire a translator to start."," Because all versions derive from one template and write to one relational store, every answer — in any language — flows into the same ",[42,68,70],{"href":69},"/knowledge/query-form-data-with-sql","queryable place",", already aligned by question.",{"title":73,"searchDepth":74,"depth":74,"links":75},"",2,[76,77,78,79],{"id":17,"depth":74,"text":18},{"id":33,"depth":74,"text":34},{"id":49,"depth":74,"text":50},{"id":59,"depth":74,"text":60},"2026-02-26","Reaching a global audience means more than translating questions. This guide covers multilingual forms — translation vs localization, keeping versions in sync, and how RoundPushPin translates one template into 10+ languages.",false,"md",[85,88,91],{"q":86,"a":87},"How do I create a form in multiple languages?","Use one master template and layer translations on top so the questions stay identical across languages and only the wording changes. RoundPushPin translates the master into 10+ languages automatically.",{"q":89,"a":90},"What's the difference between translation and localization?","Translation converts the words; localization adapts the whole experience — date and number formats, conventions, and examples — to a locale. A genuinely multilingual form does both.",{"q":92,"a":93},"How do I keep multilingual responses comparable?","Map every language version to the same underlying question so all answers write to one column. Then responses from every language land in one dataset you can analyze together, instead of separate spreadsheets per language.","/images/knowledge/multilingual-forms.png",{},true,"/knowledge/multilingual-forms","scaling-localizing-forms","Scaling & localizing forms",{"title":5,"description":81},[102,106],{"title":103,"url":104,"publisher":105},"Localization vs. Internationalization","https://www.w3.org/International/questions/qa-i18n","W3C",{"title":107,"url":108,"publisher":105},"Internationalization (i18n) Activity","https://www.w3.org/International/","knowledge/multilingual-forms",[111,112,113],"multilingual","localization","translation",[],"9fNPsN6WotaxguGaf-XW71wB69CVvJDxyuBcMAsmv_A",[],[118,216],{"id":119,"title":120,"author":6,"body":121,"date":185,"description":186,"draft":82,"extension":83,"faqs":187,"image":197,"isPillar":82,"meta":198,"navigation":96,"path":199,"pillar":98,"pillarName":99,"seo":200,"sources":201,"stem":210,"tags":211,"takeaways":214,"updated":185,"__hash__":215},"knowledge/knowledge/repeatable-contexts.md","Repeatable Contexts: Ask the Same Questions for Many Items",{"type":8,"value":122,"toc":179},[123,130,134,140,144,150,154,160,164],[11,124,125,126,129],{},"A repeatable context is a set of questions asked once ",[27,127,128],{},"per item"," in a list — once for each product, student, employee, or event — instead of being hard-coded into the form a fixed number of times. It lets one form scale to any number of items without rebuilding.",[15,131,133],{"id":132},"what-problem-do-repeatable-contexts-solve","What problem do repeatable contexts solve?",[11,135,136,139],{},[22,137,138],{},"The \"I don't know how many there will be\" problem."," If you need to ask the same five questions about each of a respondent's products, you can't know in advance whether that's two products or twenty. Hard-coding \"Product 1 / Product 2 / Product 3…\" fields is brittle and caps the count; a repeatable context asks the five questions as many times as there are items.",[15,141,143],{"id":142},"how-is-this-different-from-just-adding-more-fields","How is this different from just adding more fields?",[11,145,146,149],{},[22,147,148],{},"Duplicated fields bloat the form and still impose a fixed limit; a repeatable context is one definition applied N times."," You define the question set once and attach it to a list of items, so the form expands to fit the data instead of the data being forced to fit the form.",[15,151,153],{"id":152},"why-does-the-data-model-matter-here","Why does the data model matter here?",[11,155,156,159],{},[22,157,158],{},"Because repeating questions naively produces messy, wide data."," The clean representation is relational: a parent record for the response and a child row per item, linked by a foreign key — exactly the normalized structure the relational model was designed for (Codd, 1970), with PostgreSQL foreign keys keeping each item tied to its response. That way \"20 products\" is 20 tidy rows, not 100 sparse columns.",[15,161,163],{"id":162},"how-roundpushpin-models-repeatable-contexts","How RoundPushPin models repeatable contexts",[11,165,166,169,170,173,174,178],{},[22,167,168],{},"RoundPushPin lets you define a question set once and repeat it for every item in a context — products, people, events — and stores each item as its own related row rather than duplicated columns."," The result is a form that adapts to any number of items and a dataset that stays clean and ",[42,171,172],{"href":69},"queryable",", consistent with RoundPushPin's broader ",[42,175,177],{"href":176},"/knowledge/form-data-architecture","form data architecture",".",{"title":73,"searchDepth":74,"depth":74,"links":180},[181,182,183,184],{"id":132,"depth":74,"text":133},{"id":142,"depth":74,"text":143},{"id":152,"depth":74,"text":153},{"id":162,"depth":74,"text":163},"2026-02-28","Repeatable contexts let you ask one set of questions for each item in a list — products, students, events — without rebuilding the form. This guide explains the concept and how RoundPushPin models it relationally.",[188,191,194],{"q":189,"a":190},"How do I ask the same questions for multiple items?","Use a repeatable context: define the question set once and repeat it per item — per product, student, or event — instead of hard-coding fixed fields. The form then expands to fit any number of items.",{"q":192,"a":193},"How is a repeatable context different from adding more fields?","Duplicated fields impose a fixed limit and bloat the form; a repeatable context is one definition applied many times, so the form adapts to the data instead of the data being forced to fit the form.",{"q":195,"a":196},"How is repeated-question data stored cleanly?","Relationally: a parent record for the response and a child row per item, linked by a foreign key. That keeps '20 items' as 20 tidy rows rather than 100 sparse columns.","/images/knowledge/repeatable-contexts.png",{},"/knowledge/repeatable-contexts",{"title":120,"description":186},[202,206],{"title":203,"url":204,"publisher":205},"A Relational Model of Data for Large Shared Data Banks (E. F. Codd, 1970)","https://dl.acm.org/doi/10.1145/362384.362685","Communications of the ACM",{"title":207,"url":208,"publisher":209},"Foreign Keys","https://www.postgresql.org/docs/current/tutorial-fk.html","PostgreSQL Global Development Group","knowledge/repeatable-contexts",[212,213],"repeatable","data model",[],"yRHeUw1YyQO5dJRpVG3c28cpwt0oDwDMlM6OGft4FBQ",{"id":217,"title":218,"author":6,"body":219,"date":286,"description":287,"draft":82,"extension":83,"faqs":288,"image":298,"isPillar":82,"meta":299,"navigation":96,"path":44,"pillar":98,"pillarName":99,"seo":300,"sources":301,"stem":306,"tags":307,"takeaways":310,"updated":286,"__hash__":311},"knowledge/knowledge/one-template-many-versions.md","One Template, Many Versions: Build a Form Once",{"type":8,"value":220,"toc":280},[221,224,228,238,242,252,256,262,266],[11,222,223],{},"\"One template, many versions\" means you design a form a single time and generate every variant — per language, product, course, or campaign — from that one master. The master is the single source of truth, so the versions can never quietly drift apart.",[15,225,227],{"id":226},"what-problem-does-a-master-template-solve","What problem does a master template solve?",[11,229,230,233,234,237],{},[22,231,232],{},"It solves duplication drift."," The moment you clone a form, the copies start diverging: a fix here, an extra question there, a translation that lags. The ",[27,235,236],{},"Don't Repeat Yourself"," principle — that every piece of knowledge should have one authoritative representation — exists because duplicated knowledge is where inconsistencies and bugs breed. A form used ten ways should be defined once, not ten times.",[15,239,241],{"id":240},"how-is-this-different-from-duplicating-a-form","How is this different from duplicating a form?",[11,243,244,247,248,251],{},[22,245,246],{},"Duplicating creates independent copies that you maintain separately."," A master template creates ",[27,249,250],{},"derived"," versions that stay connected to their source: change the master question and every version updates, because the versions are projections of one definition rather than forks of it.",[15,253,255],{"id":254},"what-stays-in-sync-across-versions","What stays in sync across versions?",[11,257,258,261],{},[22,259,260],{},"Wording, structure, logic, and validation."," When the master changes, the change propagates — so all versions ask the same questions, branch the same way, and enforce the same rules. That consistency is what makes responses from different versions comparable in one dataset.",[15,263,265],{"id":264},"how-roundpushpin-does-it","How RoundPushPin does it",[11,267,268,271,272,275,276,279],{},[22,269,270],{},"RoundPushPin is built around the master template: create it once, replicate it in seconds for any audience, and keep editing the master to update every version at once."," Pair it with ",[42,273,274],{"href":97},"automatic translation"," for languages and ",[42,277,278],{"href":199},"repeatable contexts"," for per-item question sets — and every version still sends answers to a single, queryable store.",{"title":73,"searchDepth":74,"depth":74,"links":281},[282,283,284,285],{"id":226,"depth":74,"text":227},{"id":240,"depth":74,"text":241},{"id":254,"depth":74,"text":255},{"id":264,"depth":74,"text":265},"2026-02-24","Instead of cloning a form for every audience, build one master template and generate every version from it. This guide explains the single-source-of-truth approach and why it keeps forms consistent at scale.",[289,292,295],{"q":290,"a":291},"How do I reuse a form across products or campaigns?","Build one master template and generate each version from it, rather than cloning and editing. Versions stay connected to the source, so editing the master updates them all and they can't drift apart.",{"q":293,"a":294},"What is a master template?","A single authoritative definition of a form that every version derives from — the single source of truth. Wording, structure, logic, and validation all flow from it to the versions.",{"q":296,"a":297},"Why not just duplicate the form?","Because duplicates diverge: each copy is maintained separately, so fixes and translations fall out of sync. A master template avoids that by making versions projections of one definition.","/images/knowledge/one-template-many-versions.png",{},{"title":218,"description":287},[302],{"title":303,"url":304,"publisher":305},"The Pragmatic Programmer — DRY (Don't Repeat Yourself)","https://pragprog.com/titles/tpp20/the-pragmatic-programmer-20th-anniversary-edition/","Pragmatic Bookshelf","knowledge/one-template-many-versions",[308,309],"templates","scaling",[],"y8Bdebmx_wIL8kKUAECqH2IJ9uEI42rWPn9rz8D6z20",1780692425801]