freemarker-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jacques Le Roux <>
Subject Re: Opinions about the new ?truncate built-in?
Date Sat, 02 Mar 2019 11:13:09 GMT
Hi Daniel,

I tried to test this morning using OFBiz, but I have not much time and freemarker:2.3.29 is
not available in Maven (we use Jcenter in our Gradle 
build, but I have a local m2 repository too)

So I'll wait its release to test except if you can explain me how to circumvent this issue
using my local m2 repository too



Le 17/01/2019 à 20:13, Daniel Dekany a écrit :
> I have added the str?truncate(maxLength) built-in (and its other
> variations) to the 2.3-gae head. This is something that users have
> requested and implemented their own for who knows how many times, yet
> it wasn't added to FreeMarker till now, as there's no single correct
> way of text truncation. So what I did is making the algorithm
> pluggable, and giving a default that I think reflects a good practice.
> I guess most users will just go along (instead of quickly adding some
> simplistic #function their own), but those who have other ideas can
> still keep using ?truncate.
> Please tell your opinions, ideas, or even better, test it!
> >From
> Added new built-ins for truncating text. string?truncate(length)
> truncates the text to the given length, and by default adds [...] at
> the end if truncation has happened. Truncation happens at word
> boundaries, unless the result is too short that way, in which case it
> falls back to truncation mid word. There's also ?truncate_w to force
> Word Boundary truncation, and ?truncate_c (for Character Boundary)
> that doesn't care about word boundaries. The truncation algorithm is
> pluggable in the FreeMarker configuration. See the reference for more
> details.
> Built-in documentation:
> Related API-s:
> Commit:

View raw message