On Tuesday 16 January 2007 00:02, DA Shetland wrote:
> Sorry - I am using 0.93 - will try the trunk and get back.
> -d-
>
SHY support in fop-trunk is a very new addition and any testing and 
feedback would be much appreciated. It should work as you described, 
that is SHY being suppressed everywhere and only used to indicate a 
hyphenated line break possibility. If chosen as a line break a proper 
hyphen character is put in its place.

Manuel
> Jeremias Maerki wrote:
> > You should start by saying which FOP version you are using. For the
> > recent SHY stuff to work you need the latest code from the
> > Subversion repository (FOP Trunk). It is not available in 0.93.
> >
> > On 15.01.2007 15:47:53 DA Shetland wrote:
> >> To fop folks interested in hyphens - or not.
> >>
> >> I have been following with interest the development of ideas in
> >> fop-dev for hyphenation implementation, and have started several
> >> times to post this to that list, but my immediate issue is at the
> >> user level.
> >>
> >> In a data set for which I have recently been working on an XML to
> >> PDF process using XSL-FOP, I just recently was reminded of the SHY
> >> character when I noticed the word "rec-ords" right in the middle
> >> of a sentence in the PDF output.  It turns out to be a SHY.
> >>
> >> I am not using hyphenation at this time.
> >>
> >>  From my 20+ years of working with documentation systems, it seems
> >> to me the behavior to be expected here is simple (although I
> >> realize the implementation issues can be very troublesome).  The
> >> SHY character should disappear from the containing string -
> >> always.  In fact SHY is the character that is not a character - it
> >> is a one character size processing instruction that happens to
> >> enjoy a code point in character tables, but strictly speaking, it
> >> doesn't even need a glyph (we have a code point for the hyphen). 
> >> In every case, hyphenation available on or not, turned on or not,
> >> the SHY needs to disappear from the string - of course, if
> >> hyphenation is available, the location needs to be remembered for
> >> later use.
> >>
> >> So my question is--
> >> Is there some way to explicitly suppress the SHY?
> >> Is there something wrong with my installation?
> >>
> >> Thanks for any thoughts.
> >>
> >> Dave Shetland
> >> Programmer/Analyst
> >> Legal Information Institute
> >> Cornell Law School
> >
> > Jeremias Maerki
> >
> >
> > -------------------------------------------------------------------
> >-- To unsubscribe, e-mail:
> > [EMAIL PROTECTED] For additional
> > commands, e-mail: [EMAIL PROTECTED]
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail:
> [EMAIL PROTECTED]

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to