How add i18n support for tal:content string:?

Hi Plonistas

How add i18n support for tal:content string: ?

<h1 class="documentFirstHeading" tal:content="string:${context/pretty_title_or_id} Participants">Participants</h1>

I resolved previously a "tal:content string:" sentence like the following:


Position: TBD


My problem is not how to handle the dynamic value? Any ideas?

<h1 class="documentFirstHeading" i18n:translate="heading_participants"><span i18n:name="placeholder_participants" tal:replace="context/pretty_title_or_id" />Participants</h1>

1 Like

@jensens it work for me! thanks :beer:

@macagua you have a full reference on i18n matters in our docs:

I'am not sure if I would call this "full". There used to be a full documentation, I wonder where it is gone.

these are the two resources I use:

those are well written and are focused on solving real world problems.

now, repeat after me: "doctests are not good documentation… doctests are not good documentation… doctests are not good documentation…"

Hi @gforcada

You're right, this docs was useful for me, especially the section called "Translation string substitution".


Hi @jensens

Well now that you say so, that statement is so! I think that missing documentation is available from for versions Plone 3, which is still valid for Plone versions 4 and 5.

Even necessary documentation on how to implement i18n javascript, for example, i18n for Angular.js applications clients with Plone as backend, for now I'm trying to understand the operation of the library jarn.jsi18n.

@hvelarde +1 the Maurits reference is the main reference for me, is like the Plone i18n cookbook. I think, that these articles should be merged both.

May you create a ticket at ?

1 Like

I also found to be useful - covering some points to a level of detail which I didn't find elsewhere.

@jensens yes, but now I am forking the repo, for update the i18n article cause have some errors like urls thats don't exist!

Hi @djowett

That time had not seen the article written by this company, I remember that I was very useful for Plone 2.5 and 3 versions. I'm sure this article can be very inspiring for good content structure, more practical.

Something I like about this article is that it describes common problem-solving cases such as the @mauritsvanrees article

Thanks for sharing!

Plone Foundation Code of Conduct