A good example of my problem is shown in the differences between these two pages generated by v2.2.10 and v3.0.0 respectively:
Both are generated from the same note, where I enclosed the text of the will in <pre></pre> tags to maintain the spacing of the text.  I have done basically the same thing in hundreds of notes scattered throughout my database...
You will notice that v2 translated the line breaks within <pre> tags as <br>, and v3 translated the same line breaks as hard <p></p> (not a CSS thing), resulting in very large, ugly spacing that looks nothing like intended...
Brian, Benny (et al), thanks for leaving this open and for looking into it!

On 4/7/08, Benny Malengier <benny.malengier@gmail.com> wrote:

2008/4/7, David Martin <martin.d.r@gmail.com>:
Ouch!  So because you don't condone it, those of us who have naively used  HTML in notes should be punished?  I don't mean to be flippant, but that's the way I read your reply... please let me know if I misinterpreted you.

I'll let Brian answer about what he means.

I would love to hear your advice on how to better structure a narrative web report without using HTML tags in notes, but as I said before, it will take weeks to "undo" them all... and I only used the <pre> tag because that is precisely what GRAMPS 2 used when I did as you suggested and checked the "preformatted" checkbox.  The trouble with that checkbox is that it isn't selective... it affects either the entire note or none of it at all.

Yes, but in 3.0.0 you have multiple notes, so you could split this up. Mixing preformatted and not preformatted by using tags yourself in the notes was apparently possible in 2.2.x, but not something that was not actually supported or meant to happen by the developers. So the <pre> was not intentionally broken in 3.0.0, it just didn't occur to us it should be possible at all.

Let's take a step back, and go to the use case you have. What do you want to achieve, and how can it be made possible in GRAMPS without unintended use of certain code. If gramps writes out the note in a web report as it should, what is preventing the webbrowser to interpret the <pre> correctly? Is it something in the css?


So should I take away from this that GRAMPS 3 interpreting linebreaks inside <pre> tags as paragraphs rather than <br> is permanent behavior? ...not open to discussion?

As I say above, why is this happening. Personally I program python, html is not my thing, so why are it paragraphs now? Is it not just a css thing you could change? Can you point us to an example website?



On 4/5/08, Brian Matherly <brian@gramps-project.org> wrote:

> I thought I remembered seeing this discussed while
> you were developing 3.0,
> so I hesitated to post it to the bugs forum... but I
> can't find the posts (I
> think) I remember now.
> Was the <pre> tag intentionally crippled in 3.0?  I
> thought there was
> mention of something like that while you were
> working on formatted notes...
> but since that was removed, shouldn't <pre> still
> work as it did before?
> I have been using piecemeal HTML tags in my notes
> since day one, so I have
> quite a huge number of them now.  It would take
> weeks to go back now and
> remove all of the line breaks that I *intentionally*
> put in my
> <pre>-formatted notes because 2.x supported
> them--something I may be faced
> with again when you do add note formatting, and
> certainly don't want to do
> twice!
> The problem is that line breaks within the <pre>
> section were translated as
> <br> before, but now are <p></p>.  I only used <pre>
> because it was very
> simple and effective at the time...

Sorry, but I don't know the answer to your question. I
know a lot of people think putting HTML tags in notes
is clever. But personally, I do not condone the use of
HTML in notes under any circumstance.

If you want to use line breaks in your notes, I
recommend that you check the "preformatted" checkbox,
and then format the notes in the manor you see fit.



This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
Register now and save $200. Hurry, offer ends at 11:59 p.m.,
Monday, April 7! Use priority code J8TLD2.
Gramps-bugs mailing list