> On Sep 08, 2021, at 10:05, Howard wrote:
> I have multiple instances of this sample data (below) in which each
> observation has at least three lines and is separated by a blank line. In
> each observation, the first line contains a name, the second a time, and then
> there is one or more
Hi Greg,
Actually, the Modern Business template that underlies the Sample Website is
using Bootstrap 5. But I'm with you. If it works for your project,
there's little reason to upgrade.
I'm unfamiliar with your workflow. But Git has saved my ass many many
times in situations like you
Many years ago I had some problems with uncoded entities, so I got "stuck"
encoding them. I have noticed that recent browsers seem to figure things
out better, perhaps in part due to HTML5 becoming more the norm.
I understand about the different folders, but I always create a project
based on
Hello Greg,
Thanks for taking a look!
I haven't run across a problem that required special treatment to please
the validators, but the bbignore tip sounds like a good one.
On a UTF-8 website, why do you prefer the HTML entity to ©? I
haven't seen it rendered incorrectly in years.
This worked for me, for the first part.
[image: Screen Shot 2021-09-08 at 11.59.25 AM.png]
The second part I think would have to be scripted.
--Kerri
On Wed, Sep 8, 2021 at 11:05 AM Howard wrote:
> I have multiple instances of this sample data (below) in which each
> observation has at least
Hi Howard, here's a NodeJS version
Put the following in a file named "converter.js"
To run in Terminal: node path/to/converter.js path/to/source
fs = require("fs"); //Load two npm packages
path = require("path");
sourcePath = process.argv[2]; //Set filepaths
formattedPath =
I have multiple instances of this sample data (below) in which each
observation has at least three lines and is separated by a blank line. In
each observation, the first line contains a name, the second a time, and
then there is one or more lines of text*:*
*SAMPLE DATA*
Peter Frost
25:34
yes
I don't understand your issue described in the Other section about finding
where to make edits to include files. Each include statement incorporates
the name of the file and the path to that file, and you have these pretty
well separated into folders, so selecting the path to the include and
Wow, what a project! I'd never thought of extending bbincludes anywhere
near this far.
I won't pretend that I have anything but a cursory understanding of what
you've accomplished, but here are some trivial notes so far:
- Wrap the "social media" meta information in bbignore tags so when
