Incorrect display of chapter symbol (§)

[Michael A. Lowry]

In my discussion thread AE Limits, the chapter symbol (§) is displayed incorrectly. It appears as an at symbol (@).

If I edit the post, the character is displayed correctly.

[Diane Craddock]

Hi Michael,

I see what you are talking about.  Let me review and bring this up with the vendor and see if we can get it fixed.

Thanks

------------------------------
Diane Craddock
Community Manager, Broadcom Enterprise Software Division
Broadcom Inc.
------------------------------

[Carsten Schmitz]

​Michael,

Was it a typo in your post, or is this very, very meta? ;)

[Carsten Schmitz]

​Oh wow. When I reply to any of this, the accompanying brief message popup says:

The message popups in this forum software are of really high quality entropy :D

[Michael A. Lowry]

My post reporting the problem exhibits the problem.

[Jason McClellan]

@Michael A. Lowry  - a defect case has been opened for the character issue.    ​​@Christopher Hackett , @Diane Craddock, @Lenn Thompson​​​​

------------------------------
Thank you
Jason
Community Platform Owner, IT
------------------------------

[Michael A. Lowry]

Any idea when this will be fixed?

[Jason McClellan]

The case was escalated to the vendor's engineering team and is still open pending a resolution.  As of today, I do not have a time frame.  ~jm

------------------------------
Thank you
Jason
Community Platform Owner, IT
------------------------------

[Michael A. Lowry]

Any update on this bug?

[Michael A. Lowry]

It has been more than six months since I reported this bug. Has there been any progress?

[Jason McClellan]

@Michael A. Lowry  -  You are correct, the vendor Engineering team is working on it.  Every bug has a priority, this one, in my opinion, is a p5 - not the highest priority, not affecting a wide audience, with low impact.    ​I'll check if the JIRA ticket has been updated with a patch.

------------------------------
Thank you
Jason
Broadcom Community Platform Admin, IT
------------------------------

[Jason McClellan]

Note from vendor support:

Mar 30, 12:39 PM EDT

Hi Jason, I've reached back out to Development to get an update on this one. As soon as I get a reply from them, I'll forward it over to you so you're up to date on it.

------------------------------
Thank you
Jason
Broadcom Community Platform Admin, IT
------------------------------

[Michael A. Lowry]

Thanks. I want to give you an idea of how this feels from the perspective of your customers.

With Jive, we were at an 8 out of 10 with regard to functionality and usability.
With Higher Logic, we're struggling for months just to get from 4 to 5.

[Michael A. Lowry]

This bug in the Higher Logic platform is still present 10 months after I reported it. Is there any chance it will be fixed?

[Jason McClellan]

@Michael A. Lowry  - the ticket is still open with the vendor - as you can see it is escalated and a bug in the system that is in engineering.   Their cycles and updates are mapped so this is not a quick fix.   The vendor usually clears tickets quickly.  This one must have deeper roots.

 ​

------------------------------
Thank you
Jason
Broadcom Community Platform Admin, IT
------------------------------

[Michael A. Lowry]

Thanks, @Jason McClellan. It's clear from the surprisingly candid transcript you provided that this is not a priority at all. It is not my intention to ask you for something you are simply unable to deliver. I will stop asking about the fix.

[Carsten Schmitz]

I was about to ask about another bug I reported that Broadcom acknowledged months ago, but then I found this thread.

stickler for responses

"very important" community member

Appreciate the honesty. I think we can finally drop the pretext that it's all "customer first", and our input valuable.

Think I'm done here.

[Jason McClellan]

All,  I can control what I can control - or what I perceive I can control.  (Need a little humor today) but vendors have their own roadmap.   I've actually raised the ticket I shared with the community into another security fix I am working on which is a P1.    When I can, I try to be as transparent as possible.    ~jm

------------------------------
Thank you
Jason
Broadcom Community Platform Admin, IT
------------------------------

[Jason McClellan]

@Michael A. Lowry  - I just received this note this morning from vendor support.  It looks to be rendering correctly on the post you shared in the above thread https://community.broadcom.com/communities/community-home/digestviewer/viewthread?MID=791473.     Backlog p4 items take a while to resolve.   ~jm

<start post>

Hi Jason,

I wanted to let you know that we released the code that resolves this issue. If you notice it still occurring on your end, please let me know and I'll send the case back over to our Development team.

Thank you for your patience while we worked on the issue for you.

Support Rep

​​<end post>

------------------------------
Thank you
Jason
Broadcom Community Platform Admin, IT
------------------------------