Why treating U+3000 as whitespace by default?

Having trouble installing <oXygen/>? Got a bug to report? Post it all here.
HomeGoods
Posts: 89
Joined: Wed Feb 09, 2005 8:57 am

Why treating U+3000 as whitespace by default?

Post by HomeGoods » Sat Aug 22, 2015 8:32 am

By default, Preferences - Editor - Format - XML - Whitespaces has U+3000 ticked.
This looks too radical to me; even destructive. U+3000 is used on purpose in many cases.
What's the specific reason to have it ticked by default?

Well, I can just untick it and forget about it. So I'm rather just curious.

Radu
Posts: 6395
Joined: Fri Jul 09, 2004 5:18 pm

Re: Why treating U+3000 as whitespace by default?

Post by Radu » Mon Aug 24, 2015 11:02 am

Hi,

I would also agree with you at a first glance. My colleague who added this character to the default list is not here right now but we'll discuss this when he gets back and update the forum thread with an answer.

Regards,
Radu
Radu Coravu
<oXygen/> XML Editor
http://www.oxygenxml.com

HomeGoods
Posts: 89
Joined: Wed Feb 09, 2005 8:57 am

Re: Why treating U+3000 as whitespace by default?

Post by HomeGoods » Thu Oct 08, 2015 1:07 pm

And the consequence is...?

Radu
Posts: 6395
Joined: Fri Jul 09, 2004 5:18 pm

Re: Why treating U+3000 as whitespace by default?

Post by Radu » Thu Oct 08, 2015 1:27 pm

Hi,

Oops, forgot to update this.

When the Format and Indent toolbar action is called on XML content and it encounters certain characters that it considers to be whitespaces (characters from that particular list) it will collapse them (consecutive whitespace characters become only one), replace them with a single regular space character and possibly replace them with a line break if the text line became too large.

In Oxygen 17.1 (which we plan to release in about one or two weeks) by default the U+3000 character will not be checked any more in that particular preferences page.

Regards,
Radu
Radu Coravu
<oXygen/> XML Editor
http://www.oxygenxml.com

HomeGoods
Posts: 89
Joined: Wed Feb 09, 2005 8:57 am

Re: Why treating U+3000 as whitespace by default?

Post by HomeGoods » Thu Oct 08, 2015 1:39 pm

Radu,
Thanks for the update. I confirmed that on the build 2015093018, U+3000 was not checked in the whitespace preference by default. I think that's the right decision.

Post Reply