From: SourceForge.net <no...@so...> - 2005-10-04 21:22:26
|
Feature Requests item #1313263, was opened at 2005-10-04 15:51 Message generated for change (Comment added) made by chuckpint You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=384722&aid=1313263&group_id=25576 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Eddy Anthony (eddyanthony) Assigned to: Nobody/Anonymous (nobody) Summary: Carriage Return support in OS Initial Comment: This is code/OS(PDF) change to support carriage return in spell descriptions. Some data tags (I do not remember which) support " &cr;" as instruction to put line break when outputted. I just extended that support to spell descriptions so I could put there actual spell text with paragraph breaks. I tested only with PDF sheets so html sheets may need some modifications as well. Also those changes were made around 5.8 release so to see actual changes you'll need to compare them to that code. It's up to you to see if the way I did it agrees with you standards but at least I hope it eventually makes in in one way or another. It would also be nice if someone would find it worth the time to put some support for tables there as well (or maybe I eventually get myself to see how hard is to do it). Andriy a_p_sen <ap...@op...> ---------------------------------------------------------------------- Comment By: Chuck Pint (chuckpint) Date: 2005-10-04 16:22 Message: Logged In: YES user_id=901169 This is something that you have to be very careful with. &cr; is thrown away as whitespace in both the PDF and HTML OS. It turns out that tag itself has to deal with this. See the BIO tag for some ideas. Also, on HTML sheets in particular, the "size" of the sheet can be different depending on the browser, screen resolution, and other factors. So any hard-coded line breaks may occur in the wrong places. It would better to describe the problem you are trying to fix, rather that just putting in a fix. Could you try and describe the problem for us? My preference would be on one of the Yahoo discussion groups rather than via tracker comments. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=384722&aid=1313263&group_id=25576 |