Skip to content

Instantly share code, notes, and snippets.

What would you like to do?
add position
<div class="guided-edit">
<form class="standard-form" id="{name}_id" name="{name}" method="{method}" action="{action}">
{#industryChooser choose=i18n__text_plain__choose}

This comment has been minimized.

Copy link

@danielstocks danielstocks commented Dec 15, 2011

Hey thanks for the interesting article over @ linkedin. Would be very interesting to see a future article on how you deal with I18n in your front-end stack. Cheers.


This comment has been minimized.

Copy link
Owner Author

@vybs vybs commented Dec 15, 2011

Our i18n solutions are built inhouse, we dont crowd source and it is extensive and rich. We would never rewrite all this on client.

We have a server-side solution to this that seamlessly works across different jvm stacks.

I would love to share more details here, but that will be the topic of next few posts. stay tuned.

Highly encourage you to read this


This comment has been minimized.

Copy link

@amlanc amlanc commented Nov 29, 2012

Very interesting article over @linked in. How do you take care of SEO issues if your presentation is assembled at the browser?


This comment has been minimized.

Copy link

@lucassaldanha lucassaldanha commented Jun 14, 2013

@amlanc - this can be achieved parsing dust.js template with Node.JS in the server-side. After that you can send to the client-side the result. I could user Rhino for parsing too.

Check the section: Leaving JSPs in the dust, the fifth topic, Server side support.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment