[Octave-bug-tracker] [bug #50422] doc browser: diamond sign and line breaks at random positions

[Torsten]

Follow-up Comment #6, bug #50422 (project octave):

It seems that the anchor position in octave.info, e.g. 295238 in


Ref: XREFisvarname295238


are calculated based assuming Latin1 coding (byte count) which is too large in
the case of multi-byte characters. I am going to prepare a patch that corrects
the text lengths while loading the text and before inserting the anchor-tag at
the position given by the info index. 

However, if my guess is correct, it would probably be better to fix the way
the index of the info files is computed. Where is that done and was there a
change recently?

    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?50422>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/