msapsard

When you created the Google Maps links, you looked them up from Google. You need to change each link to an OpenStreetMap link.

I’m sad to see the end of C-O-M. Thanks for providing it.

Mike S

Hi Tobias,

I hope you took some time off over Christmas. The code that we import has typically between about 80 and 120 cells, all similarly formatted. We have a spreadsheet that contains the data, and depending on various Y/N permissions to reveal some items like name or phone, the content for each cell is created. This is then read into another sheet that has three columns.

Originally, we simply selected the cells we required and copied them into TablePress. They went in as text, without the formulae.

With TablePress 2, every line ending generates a new cell, unless it is pasted as a csv file.

If you would like a copy of our spreadsheet, with just a few lines of data, I would be happy to send it to you, so that you can experiment.

Someone suggested the expand short code several years ago. I could have picked it up from anywhere.

I adopted it because I asked a blind person to check out the website. He had his screen reader set to such a high speed that I could not follow what was being read. The screen reader that he used, read a row at a time, all expanded cells. It was convenient for him, and I decided it was not so inconvenient for sighted users, because I thought they rarely compare the contents of two cells in our application. I’ll now have a look at css collapse.

Thanks, I can now create a child theme for 2021 that does what I need.

Thanks for your reply. Unfortunately the U3A adopted the flat topped 3 which is a special character that is not available in many word processors.

I have now gone back to the original Poppins font and moved the special characters up to the european latin language part of the font file. It seems to work well.

I was trying to match a branding requirement for the UK U3A movement. Unfortunately their branding consultants don’t understand the environment they are working in. I shan’t worry about it.

Thanks very much for your input, it helped me work through and rationalise what was happening. I had always assumed that UTF-8 contained all of the characters in a font.

There is a document showing the characters here: https://u3adacorum.org/wp-content/uploads/2020/11/Fonts-3.odt

I can copy and paste from LO to WP without the font coming with it.
The problem is trying to get particular characters from DM Sans into the Site Title,rather than a page title.
I have created a LO document that has the font embedded and which shows the special characters and how to use them in LO. The second page shows the as ‘unmapped’ glyphs in FontMatrix. They appear to be in the font, but not encoded as UTF-8 characters, except as a Special Set, which is recognized by one application but not the other.
It seems WP only recognizes the standard characters, unless there is a work around.

It looks as though the characters are in the font, but not necessarily in UTF-8. Using FontMatrix the ‘a’ appears as a.SS01 and I+639. There is no U+ representation.

Thanks. UTF-8 is in use. Cutting and pasting the required characters from LibreOffice was the first thing I tried, but it did not work. The characters that show in the Site Title are not in the Site Title font.

I have seen other posts suggesting methods of loading alternative characters, but they generally say that the techniques do not work in the Site Title.

It looks like I have to create and load a graphic.

I wish I had asked this question months ago! There are work-arounds, but they involve testing sequentially for many cases.

When you use ‘Custom’ events, you have to scroll through month by month and enter each day individually.

It occurred to me that if the tiles were only down loaded once and cached within wp-content, the limited use requirement would not be violated.

Are there plans to do this?

Set to load in footer, and turned off the two scripts load..,
Collapse-o-matic now shows in the web developer debug area, and it seems to be working properly. More testing, then I’ll report back.