Does anyone have any thoughts on my message about wrapping from a couple of days ago?
As I mentioned, on my copy of OTRS, I made changes to remove the hard browser wrapping and have OTRS handle it internally using those nifty regexps that wrap at 75 characters or less (rather than 75 characters or more, as in the current scheme). So far, so good -- it has solved all my wrapping problems, especially with quoting a customer's reply. It has been tested on several hundred tickets, including some weird ones I created intentionally to try to break it. Again, I would like to submit a patch for this if it would be accepted. However, it involves modifying quite a few templates to remove browser hard wrapping (because the two wrapping methods conflict with each other). Does anyone know of a reason that the hard wrapping in the templates exists, other than the fact that OTRS couldn't handle the wrapping the itself? In other words, if OTRS correctly handled line wrapping, is there any reason to keep it? If nobody knows of a reason why the hard wrapping is needed, Martin, would a patch that replaces it be likely to be accepted? -- Robert L Mathews, Tiger Technologies http://www.tigertech.net/ "Ignorance more frequently begets confidence than does knowledge." -- Darwin _______________________________________________ OTRS mailing list: dev - Webpage: http://otrs.org/ Archive: http://lists.otrs.org/pipermail/dev To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/dev
