Loading ...
Sorry, an error occurred while loading the content.

Re: [NTB] NTB/RegEx FormFeed Bug

Expand Messages
  • Sheri
    Sorry, meant x85, not 85. Sent from my Nook Color device
    Message 1 of 8 , Aug 6, 2012
    • 0 Attachment
      Sorry, meant \x85, not \85.

      Sent from my Nook Color device

      Sheri <silvermoonwoman@...> wrote:

      >You could use (*BSR_UNICODE) at the start of your pattern to invoke the alternative setting. Can be slightly problematic since \85 is an ellipsis in Windows ANSI for most or all Western languages, but the rest of the Unicode line ends are ok even in non-UTF-8 mode.
      >
      >Hi all...!
      >
      >Regards,
      >Sheri
      >
      >Sent from my Nook Color device
    • flo.gehrke
      ... Here is a small test: ^!InsertText Peter^PPaul^PMary^%PAGE% ^!Jump -3 ^!Find (*BSR_UNICODE)Mary R RS You will see NT matching Mary plus FF now. If
      Message 2 of 8 , Aug 6, 2012
      • 0 Attachment
        --- In notetab@yahoogroups.com, "John Shotsky" <jshotsky@...> wrote:
        >
        > According to the PCRE help, there is a compile switch that
        > forces only CR and LF to be recognized in the \R sequence.
        > There is a command to override that switch, but I don't
        > know how to use it.

        --- corrigendum ---

        Here is a small test:

        ^!InsertText Peter^PPaul^PMary^%PAGE%
        ^!Jump -3
        ^!Find "(*BSR_UNICODE)Mary\R" RS

        You will see NT matching 'Mary' plus FF now.

        If (*BSR_ANYCRLF) is active, the alternatives for matching FF are.

        \f
        \cl
        \x0C
        \014
        etc

        Regards,
        Flo
      Your message has been successfully submitted and would be delivered to recipients shortly.