• Replies 35 replies
  • Subscribers 101 subscribers
  • Views 11335 views
  • Users 0 members are here
Options
Related

Another "Is this expected behaviour?"

Chris Leggett

CSS XPP 9.4.1

I have an interesting issue - the XML I have been supplied with has "xxx</close><open>Zzz". The requirement (apart from changing typeface etc) is to add a period and a space so I end up with:

xxx</close>. <open>Zzz

I am generating the period and space in the close::after pseudo-element selector and most of the time it is working perfectly. However if the last word before the </close> is a very long word (and its in 2 columns to a short measure) then the last word will not hyphenate. If I only generate the period and add space manually, either before or after the <open> element then the long word hyphenates perfectly and as expected. However is does act as you would expect if the justification means finishing a line! Interestingly if I remove the space altogether the word xxx.Zzz will hyphenate.

One option would be to transform and add the space but I am very nervous about that is this could cause issues if the XML is inconsistent.

Interested to hear if anyone else has encountered a similar issue.

Chris
Rate translation
×
Suggest better translation
×
Parents

  • Just to jump in here, but are you sure that you put the -xpp-word property in the "open" tag and not in the before/after?

    For CSS, the '-xpp-word" is supposed to act exactly like the "!" at the start of the macro except do the same thing with a tag. Prior to processing, it should "end" the word prior to the <open> and keep the ".<sp>" away from the previous word. It is then free to hyphenate the long previous word. If it is not doing that (and you did put it in tag definition itself) you should open a support call, because that is the exact solution is was supposed to "fix'.
Reply

  • Just to jump in here, but are you sure that you put the -xpp-word property in the "open" tag and not in the before/after?

    For CSS, the '-xpp-word" is supposed to act exactly like the "!" at the start of the macro except do the same thing with a tag. Prior to processing, it should "end" the word prior to the <open> and keep the ".<sp>" away from the previous word. It is then free to hyphenate the long previous word. If it is not doing that (and you did put it in tag definition itself) you should open a support call, because that is the exact solution is was supposed to "fix'.
Children