Recent Nabble Update has deleted all text that is inside < and > (triangle brackets). Can we undo this change?

[veqryn]

Hi,
Sometime in the last 2 weeks or so Nabble must have updated their code.  Now it currently removes (does not display) all text that occurs between triangle brackets.  < and >.
Quick Example, I am going to write the next line inside triangle brackets.  There is only 1 blank line between this line and the one after that, however because the next line disappears you will see 2 blank lines:
<This is a line inside some triangle brackets>

Since they don't appear (when directly touching another character), for the purposes of this post I am going to use { and } to mean triangle brackets.  

Before this update, only certain things between triangle brackets would be hidden/removed/not-displayed.  
So for example {b} and {/b} would disappear and make any text between them bold.
However, {option name="trigger" value="conditionAttachment"/} would not disappear.  

Now, that last example, and anything else between triangle brackets, will disappear.

This may not matter to many forums, but this really matters to any forum that happens to be discussing such things as programming code, anything in xml, etc.

So for example, this entire block of stuff will disappear:
                <attatchment name="conditionAttachmentJapanese1b" attatchTo="Japanese" javaClass="games.strategy.triplea.attatchments.RulesAttachment" type="player">
                <option name="turns" value="3:4"/>
                </attatchment>
                               
                <attatchment name="conditionAttachmentJapanese2" attatchTo="Japanese" javaClass="games.strategy.triplea.attatchments.RulesAttachment" type="player">
                <option name="turns" value="3:4:5"/>
                <option name="alliedOwnershipTerritories" value="Australia:India:Sinkiang" count="3"/>
                </attatchment>

And so too will the constructors inside this block of Java code:
        private HashMap<Territory, Territory> amphibMap = new HashMap<Territory, Territory>();
        private HashMap<Territory, Collection<Unit>> shipsMovedMap = new HashMap<Territory, Collection<Unit>>();
        private Collection<Territory> m_seaTerrAttacked = new ArrayList<Territory>();
        private Collection<Territory> m_landTerrAttacked = new ArrayList<Territory>();
        private Collection<Territory> m_impassableTerrs = new ArrayList<Territory>();

as you can see the hashmaps for some reason have their {object, object}, BUT the collections are missing their {object}


Until 2 weeks ago, this post of mine contained very detailed information on xml syntax for a game engine's mods.  Now it just contains the headers and a lot of blanks spaces.
http://tripleadev.1671093.n2.nabble.com/New-features-to-latest-Unstable-since-1-2-5-5-tp5934498p5934498.html



Is there a workaround to this?  Or a way to roll back or undo this "upgrade" to nabble?
Is this bug / lost-feature acknowledged and are the nabble developers aware of this?
Is a fix being worked on?


Also, I already tried putting stuff inside "RAW" marks.  {raw}
However, it fills the text with lots of really really bad things, like html code.
Here is an example of some xml code:
                <attatchment name="conditionAttachmentJapanese1b" attatchTo="Japanese" javaClass="games.strategy.triplea.attatchments.RulesAttachment" type="player">
                <option name="turns" value="3:4"/>
                </attatchment>
                               
                <attatchment name="conditionAttachmentJapanese2" attatchTo="Japanese" javaClass="games.strategy.triplea.attatchments.RulesAttachment" type="player">
                <option name="turns" value="3:4:5"/>
                <option name="alliedOwnershipTerritories" value="Australia:India:Sinkiang" count="3"/>
                </attatchment>

Here is what it looks like in RAW:

                <attatchment name="conditionAttachmentJapanese1b" attatchTo="Japanese" javaClass="games.strategy.triplea.attatchments.RulesAttachment" type="player">
                	<option name="turns" value="3:4"/>
                </attatchment>
				
                <attatchment name="conditionAttachmentJapanese2" attatchTo="Japanese" javaClass="games.strategy.triplea.attatchments.RulesAttachment" type="player">
                	<option name="turns" value="3:4:5"/>
                	<option name="alliedOwnershipTerritories" value="Australia:India:Sinkiang" count="3"/>
                </attatchment>

And here is what a screenshot of what it SHOULD look like: (it is OK if it word wraps of course)



as you can see, RAW adds things like {br} and "nbsp" that are NOT in my text,
so RAW definitely doesn't work

thanks,
veqryn

[GregChapman]

This appears to be an unintended side effect of the recent change to what used to be the "Embed" button on the Message Edit Screen, now the "Tips" button.

I believe that the intention was to allow further HTML tags to be inserted in non HTML message code without the need to check the "Message in HTML Format" box and was a response to the request to allow headings in the Premium Support Forum.

However with the change as it is I have found difficulties too. In a recent post of mine I had to use [raw] tags to insert the HTML but this led to the lines breaks in my code being ignored and a change in font.

[veqryn]

So, do the devs know that this recent feature update has caused major problems?
I didn't see a bug tracker anywhere, ....

Is this going to be fixed?

[GregChapman]

They will when they read this thread, which they probably will within 24 hours.

If it's not picked up by then I have permission to post in the Premium Forum and will alert them to this thread.

[veqryn]

good to know,
thanks for the help,
i hope this issue/bug gets solved soon

[GregChapman]

It's on the developer's list:
http://nabble-support.1.n2.nabble.com/New-button-Subheader-tp5992711p6179549.html

[Hugo <Nabble>]

We fixed this issue. Please take a look at the root post and see how text between brackets are displayed without problems.

[veqryn]

Super big thank you!

looks like you also got "RAW" to work properly too, which is cool

thanks again,
veqryn