You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@whimsical.apache.org by Daniel Gruno <hu...@apache.org> on 2022/11/15 01:52:44 UTC

Whitespace comparison too strict for certain resolution checks in agenda tool

Hi folks,
I noticed that item 7B for November seems to fail the standard checks due to a whitespace irregularity that stems from word-wrapping in the resolution. A word with a dash in it (real-time) has been broken into two lines, which the agenda then reconstitutes as "real- time", thus failing the comparison. Not sure what the ideal fix is here, perhaps interpreting a newline as being able to be both a space and not a space at the same time?

Re: Whitespace comparison too strict for certain resolution checks in agenda tool

Posted by Dave Fisher <wa...@comcast.net>.

Sent from my iPhone

> On Nov 15, 2022, at 4:46 AM, sebb <se...@gmail.com> wrote:
> 
> Given that the agenda tool is due to be replaced, is it worth spending
> any time on this?

Exactly. If it bothers anyone then they can ask for help to fix the agenda using svn!
> 
> It would be a good idea to check that the replacement tool can cope
> better with wrapping of hyphenated words.

Exactly - there are hundreds of PMC chairs.

Best,
Dave
> 
>> On Tue, 15 Nov 2022 at 09:04, sebb <se...@gmail.com> wrote:
>> 
>> Another solution would be to adjust word-wrapping so it treats hyphen
>> as a normal letter.
>> 
>>> On Tue, 15 Nov 2022 at 01:52, Daniel Gruno <hu...@apache.org> wrote:
>>> 
>>> Hi folks,
>>> I noticed that item 7B for November seems to fail the standard checks due to a whitespace irregularity that stems from word-wrapping in the resolution. A word with a dash in it (real-time) has been broken into two lines, which the agenda then reconstitutes as "real- time", thus failing the comparison. Not sure what the ideal fix is here, perhaps interpreting a newline as being able to be both a space and not a space at the same time?


Re: Whitespace comparison too strict for certain resolution checks in agenda tool

Posted by sebb <se...@gmail.com>.
Given that the agenda tool is due to be replaced, is it worth spending
any time on this?

It would be a good idea to check that the replacement tool can cope
better with wrapping of hyphenated words.

On Tue, 15 Nov 2022 at 09:04, sebb <se...@gmail.com> wrote:
>
> Another solution would be to adjust word-wrapping so it treats hyphen
> as a normal letter.
>
> On Tue, 15 Nov 2022 at 01:52, Daniel Gruno <hu...@apache.org> wrote:
> >
> > Hi folks,
> > I noticed that item 7B for November seems to fail the standard checks due to a whitespace irregularity that stems from word-wrapping in the resolution. A word with a dash in it (real-time) has been broken into two lines, which the agenda then reconstitutes as "real- time", thus failing the comparison. Not sure what the ideal fix is here, perhaps interpreting a newline as being able to be both a space and not a space at the same time?

Re: Whitespace comparison too strict for certain resolution checks in agenda tool

Posted by sebb <se...@gmail.com>.
Another solution would be to adjust word-wrapping so it treats hyphen
as a normal letter.

On Tue, 15 Nov 2022 at 01:52, Daniel Gruno <hu...@apache.org> wrote:
>
> Hi folks,
> I noticed that item 7B for November seems to fail the standard checks due to a whitespace irregularity that stems from word-wrapping in the resolution. A word with a dash in it (real-time) has been broken into two lines, which the agenda then reconstitutes as "real- time", thus failing the comparison. Not sure what the ideal fix is here, perhaps interpreting a newline as being able to be both a space and not a space at the same time?

Re: Whitespace comparison too strict for certain resolution checks in agenda tool

Posted by Matt Sicker <ma...@musigma.org>.
Try https://en.wikipedia.org/wiki/Wikipedia:Non-breaking_hyphen as a workaround?
—
Matt Sicker

> On Nov 14, 2022, at 19:52, Daniel Gruno <hu...@apache.org> wrote:
> 
> Hi folks,
> I noticed that item 7B for November seems to fail the standard checks due to a whitespace irregularity that stems from word-wrapping in the resolution. A word with a dash in it (real-time) has been broken into two lines, which the agenda then reconstitutes as "real- time", thus failing the comparison. Not sure what the ideal fix is here, perhaps interpreting a newline as being able to be both a space and not a space at the same time?