@Lupestro wrote:
So we have an application that does all kinds of neat stuff and we end up with help dialogs for a lot of it. Some of the help dialogs are small - a simple paragraph or two. Others are small tutorials the user can scroll through and read, mostly text with tables and pictures and links that go to
target=_blank
tabs. They live in a dialog over the top of the app, rather than navigating the user away from the current context, and are intended to be read and dismissed.Today, we populate them by supplying translated text for “title” and “message”. The “message”, of course, is a single large hunk of HTML. That’s a single really big ember-intl or ember-i18n string, full of newlines. As a stopgap, we might convert that to an array of strings and provide a helper to turn it into a big
htmlSafe(t(concatenated stuff, substitution_hash))
.Of course, it would be really nice if the translators could just edit the whole page body like it was a page body. Then they wouldn’t lack for context and it would be much easier to see what they’re doing. It would be even easier to work with if it were something like markdown rather than HTML. If it could be precompiled into the translation files, with maybe an @name in the authored intl file to tell which separate file to process, we could stack all of these up in our per-language subtrees and it could be done in broccoli ahead of the other application tooling.
What are other teams doing in this area?
Posts: 2
Participants: 1