Extra ... in map-comment result
Not sure I've noticed this problem before, and I have done this sort of thing regularly in the past. Using 5.3.8 why is it that in a layout, this entry. map-comment "Developed Elevation Projection\ <br><br>TBA featured prominently on the 2011 NSG trip list, meaning \ <br>'to be advised' - month after month it appeared trips were \ <br>going to 'TBA '. So when this cave was discovered, it was so \ <br>named to retrospectively make the trip list look good." produces text like the below in my output map? Developed Elevation Projection TBA featured prominently on the 2011 NSG trip list, meaning ... 'to be advised' - month after month it appeared trips were ... going to 'TBA '. So when this cave was discovered, it was so ... named to retrospectively make the trip list look good. The odd things are the . at the end of the middle three lines. What makes it especially odd is that there is no . after the first line. How can I prevent the . from being produced? Bruce
This is really strange, I have tried to reproduce your error, but without success. Could you please provide me some dataset, where it happens? Thanks a lot, S. On 8 November 2011 19:43, Bruce <bruce@tomo.co.nz> wrote:
Not sure I’ve noticed this problem before, and I have done this sort of thing regularly in the past.
Using 5.3.8 why is it that in a layout, this entry…
map-comment "Developed Elevation Projection\
<br><br>TBA featured prominently on the 2011 NSG trip list, meaning \
<br>'to be advised' - month after month it appeared trips were \
<br>going to 'TBA '. So when this cave was discovered, it was so \
<br>named to retrospectively make the trip list look good."
produces text like the below in my output map?
Developed Elevation Projection
TBA featured prominently on the 2011 NSG trip list, meaning ...
’to be advised’ - month after month it appeared trips were ...
going to ’TBA ’. So when this cave was discovered, it was so ...
named to retrospectively make the trip list look good.
The odd things are the … at the end of the middle three lines.
What makes it especially odd is that there is no … after the first line.
How can I prevent the … from being produced?
Bruce
_______________________________________________ Therion mailing list Therion@speleo.sk http://mailman.speleo.sk/mailman/listinfo/therion
Hi Stacho
This is really strange, I have tried to reproduce your error, but without success. Could you please provide me some dataset, where it happens? Thanks a lot, S.
I had an inkling of the cause before I posted, but I have only just verified it now. I have checked back with old datasets, and it is a new 'feature' I think. The cause of each . is the presence of a <tab> character in the string that I used to format the data file. If I pad out the gap with space characters instead of tab characters it is fine. It is somewhat predictable that placing spurious characters within the string wrapped around lines will be a bit unpredictable I suppose. map-comment "Developed Elevation Projection\ <br>TBA featured prominently on the 2011 NSG trip" produces a perfect result. map-comment "Developed Elevation Projection\ <br>TBA featured prominently on the 2011 NSG trip" (padded with spaces) produces a perfect result. map-comment "Developed Elevation Projection\ <br>TBA featured prominently on the 2011 NSG trip" (padded with tabs) produces a dot for each tab after the line. I can send you a small example file if you would like. Bruce
participants (2)
-
Bruce -
Stacho Mudrak