Last modified: 2012-03-09 10:27:55 UTC
Text properties with a lot of text return mangled duplicated text e,g: I spoke to Marcus. He is keen to meet. I h … I spoke to Marcus. He is keen to meet. I have teed up the conversation as very explanatory. He is also happy to do an evening session at their office in Eastcheap. So availability. This week is difficult for me. Next week though is better. Mon or Tues evening? Sent from my BlackBerry wireless device g? Sent from my BlackBerry wireless device When the property contains I spoke to Marcus. He is keen to meet. I have teed up the conversation as very explanatory. He is also happy to do an evening session at their office in Eastcheap. So availability. This week is difficult for me. Next week though is better. Mon or Tues evening? Sent from my BlackBerry wireless device It needs to handle this more elegantly. It should certainly not duplicate.
In which format does this happen? Do you have an online example somewhere?
Hi. Format is default tile. Can be easily replicated with a text property. Just paste the text in as above: "I spoke to Marcus. He is keen to meet. I have teed up the conversation as very explanatory. He is also happy to do an evening session at their office in Eastcheap. So availability. This week is difficult for me. Next week though is better. Mon or Tues evening? Sent from my BlackBerry wireless device" The Exhibit report will show: "I spoke to Marcus. He is keen to meet. I h … I spoke to Marcus. He is keen to meet. I have teed up the conversation as very explanatory. He is also happy to do an evening session at their office in Eastcheap. So availability. This week is difficult for me. Next week though is better. Mon or Tues evening? Sent from my BlackBerry wireless device g? Sent from my BlackBerry wireless device " Example query {{ #ask: [[Category:Documents]] [[ Title::+]] | ?Title | ?Notes | ?Start Date=Date Uploaded | format=exhibit | views=tiles | limit=250 }} In this case the Notes field is the text field.
Any news on this? This makes exhibit reports pretty much unusable if large text fields are present. Thanks Neill.
If this hasn't been fixed in the past two years, it is probaly not a high priority.
I'm currently sponsoring Stephan to develop an exhibit replacement, so this can be closed :)
