small "grammatical" problems with field separators

Hi,

I come with a request about the non-breaking spaces in the multiple fields separators.

If you use non-breaking spaces there is no way to have inline displayed fields not broken in a normal space within the field. If you use a normal space (after the comma or alone or after the pipe) the field can split at the separator.

and if you don't want to split your field set the css to display: block.

Is it a nice suggestion?

By the way, the class label is defined in the flexicontent.css to "bold" and can't be modified by the template item.css. This is also a templating problem.

grabit wrote: Hi,
By the way, the class label is defined in the flexicontent.css to "bold" and can't be modified by the template item.css. This is also a templating problem.

you can use a CSS rule of higher priority to override it

OK for that but what about the non-breaking spaces in separators?

I think we need a new parameter,
please remind remind me after weekend

Ok I will do.

But not a new parameter because a comma is always breakable after.

Or add the ability to use a space at the end of the custom one. I tried but did not succeed.

Small reminder as asked.

Another reason to modify that:

In the module, on the right column, I display a list of languages separated by the coma. Every value is one word. If I have more than 3 languages, the other are hidden because there is no text wrapping and the line continues outside the module.

please remind we were talking of of a new parameter to define field separator in the module ?

also i am thinking that another parameter is also needed one that will contain HTML AND field names:

e.g.
<p class="my class1">{{flexifieldname}</p>
<p class="my class2">{{flexifieldname}</p>
<p class="my class3">{{flexifieldname}</p>

thus customizing output will be a lot easier

the above is easy to add

I don't think we need a new parameter.

The only thing to do is modify in all fields plugins in
because I don't know why it MUST be non breakable.

Ok, agreed about separator parameter,

but also the custom HTML mixed with fields will allow easy management of the output without need for changing the module template