Wordwrap/break of Organisation Titles

[Aaron-M]

After upgrading we have found that on the Organisations page (e.g. https://datastore.landcareresearch.co.nz/organization) the headings of the organisations are not breaking correctly at word breaks, but rather cutting words into bits e.g. below. We have discovered that this is browser influenced – it displays correctly in Chrome, as below (Fig1) in Firefox, and partly OK in IE (the word breaks are correct, but it only displays 2 columns (Fig2).
Firefox:

IE:

The word break issue also occurs elsewhere Organisation names are displayed e.g. https://datastore.landcareresearch.co.nz/dataset/nzflora-fife-2014-anomodontaceae, not just the Organisation Page(s).

This issue has developed in the update path from CKAN 2.2.1 to 2.3, and continued into 2.4.1.

This problem is also evident on demo.ckan.org http://demo.ckan.org/organization?sort=&q=&page=2 (and e.g. http://demo.ckan.org/organization/department-of-agriculture).

Behaviour is not consistent e.g In IE this organisation displays OK on the Organisation page . http://demo.ckan.org/organization?sort=&q=&page=2

But, click into the organisation and the words break incorrectly (http://demo.ckan.org/organization/consumer-financial-protection-bureau).

In Firefox I get the split P rotection in both ‘views’. In Chrome is fine.

[k-nut]

This behavior was introduced by commit 50c3114 which was a part of PR #1667 which was supposed to fix #1538.

Unfortunately the original issue did not contain any screenshots so it is not easy to see what they were referring to with make a mess of the display.

[TkTech]

reallylongonewordorganizationtitlebecausesomelanguagesarelikethat Simply splitting on word boundaries as understood by the browser isn't sufficient for many languages that don't have distinctive word breaks.

[k-nut]

@TkTech yep, I also just realized that here are screenshots that display before and after behavior with a group called Groupwithatveryveryverylongnamethatprobablybreakthedisplay:

Before the change

After the change

It would probably be best if we could limit this to only break words that are much too long. Or use automatic hyphenation which unfortunately only has medium support: http://caniuse.com/#feat=css-hyphens

[TkTech]

Support for word breaks have historically been slowly and painful implemented. The only "portable" way I know of at the moment is to use a css rule to always break-on-character and use a bit of javascript to fix it live, which can cause redrawing and a visually jarring user experience when the page loads. Boundary analysis is a real pain when working with multiple languages.

[wardi]

burn all the grids!

[k-nut]

We could for example include the hyphenator polyfill to make this work on browsers that do not support hyphen: auto by default.
At first glance it seems like it weighs in at 134 KB
Whats the CKAN-policy on things like this?

[TkTech]

https://github.com/mnater/Hyphenator/blob/wiki/en_AddNewLanguage.md#what-we-have-now

It seems it has considerable multilanguage support, thus I'm in favour of it. 134kb of static content is irrelevant compared to the weight of existing uncached pages.

[wardi]

or we could use a list instead of a grid and just show the whole group name in a nice easy-to-scan way. Less space wasted on group images too.

[kmbn]

We decided to close old issues that are not actively worked on so that we can focus our effort and attention on issues affecting the current versions of CKAN.

If this issue is still affecting the version of CKAN you're working with now, please feel free to comment or reopen the issue.

If you do reopen this issue, please update it with new details. One reason it might not have been resolved in the past is that it wasn't clear how a contributor could address the issue.