Dear Anthony,
Back to the discussion of "bullets".
Now in grammar files saved by the PHP interface, bullets are replaced by
"•" which makes no difference to the display on a web page.
An example is the attached "-gr.acceleration"
Nonetheless, its compilation produces an error telling the "bull;" is
not a licit variable or whatever. So, the solution would be to identify
"•" properly and map it to the same token as "•"
Unfortunately we have no 7-bit equivalent in BP, unlike "…" which now
gets automatically converted as "_rest" rather than "…". Indeed,
if you program the conversion of "•" you may be able to convert
"…" as well!
Bernard
Bernard Bel wrote on 13/07/2020 16:22:
> The high-ascii encoding problem concerns only two signs:
>
> ‘•’ = ascii #149 = •
> ‘…’ = ascii #133 = …
>
> (Source: https://assiste.com/SEO_Webmaster/Tables_ascii_unicode_utf_8.html)
>
> The first one is the period used in “period notation”. It is an
> alternate glyph for a plain period ‘.’ and both work identically in the
> old BP. Therefore it wouldn't be a problem to get periods instead of
> bullets in console or file outputs. I switched to bullets when my
> eyesight started declining. ;-)
>
> I am attaching a copy of “-gr.acceleration” in clean UTF8 format
> containing a bullet on line gram#[2]. You may use it to check that the
> grammar is read and processed correctly with respect to the bullet and
> to end of lines (see below).
>
> The second is an undetermined rest. It also has a low-ascii equivalent:
> “_rest”. Many users are not familiar with typing ‘…’ so they have a
> tendency to type ‘...’ which is equivalent in publications but not in BP
> since it represents 3 periods, that is ‘•••’.
|