<?xml version="1.0"?><!-- generator="bbPress" -->

<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
>

<channel>
<title>MachForm Community Forums Topic: Multi-language forms (suggestion for future version)</title>
<link>https://www.machform.com/forums/</link>
<description>MachForm Community Forums Topic: Multi-language forms (suggestion for future version)</description>
<language>en</language>
<pubDate>Mon, 04 May 2026 01:42:17 +0000</pubDate>

<item>
<title>Mogoch on "Multi-language forms (suggestion for future version)"</title>
<link>https://www.machform.com/forums/topic/multi-language-forms-suggestion-for-future-version#post-20115</link>
<pubDate>Mon, 10 Feb 2014 22:46:17 +0000</pubDate>
<dc:creator>Mogoch</dc:creator>
<guid isPermaLink="false">20115@https://www.machform.com/forums/</guid>
<description>&#60;p&#62;I can't be the only person who needs the same form in many different languages.&#60;/p&#62;
&#60;p&#62;Forms using a lot of conditional logic get quite complicated. At the moment I am duplicating the form and then getting each element translated. I then end up with a whole series of the same form, each storing user data in different places.&#60;/p&#62;
&#60;p&#62;The problems really start when some fields or information changes. I then have to duplicate the changes across the many forms. With some languages - especially Japanese and similar, it is meticulous work when you don't actually have a clue what you are reading!&#60;/p&#62;
&#60;p&#62;If each element were stored in a database or in a translation file to which we had access, it would be a much simpler task to change say the field title for field 56 in the Japanese version. In fact it would be a dream compared with what is necessary at the moment.&#60;/p&#62;
&#60;p&#62;Machform is brilliant, but I have to say that if I found the above in a different product of the same quality, I would have no choice but to switch tomorrow. And since I don't want to do that, I hope this suggestion might find support among other users who have the same problem.
&#60;/p&#62;</description>
</item>

</channel>
</rss>
