Re: [Maxima-discuss] ***SPAM*** Recent CSS changes

[Raymond T. <toy...@gm...>]

On 7/25/25 12:52 AM, Jaime Villate wrote:

> On 25/07/25 04:52, Raymond Toy wrote:
>>
>> First, it seems that you've changed the background for the nav bar to 
>> be a fairly light gray. I find that really hard to distinguish from 
>> the current white background. This is a matter of taste, I guess, but 
>> I liked the blue from the Emacs manual because it stands out more.
>>
> I didn't like that blue because it got confused with the blue example 
> boxes. Adding an extra color, different from the blue of the examples 
> and the yellow of the category boxes seemed ugly, so I opted for gray. 
> As a compromise, I will try a darker, more bluish, gray.
>
Yeah, I noticed that the color was similar to the example boxes, but 
thought it was pretty clear that it's not an example. Something darker 
would be fine. The emacs manual uses a light yellowish background so 
there's no confusion between examples and the nav bar. I didn't want to 
change Maxima's existing blue for examples.
>
>
>> Second, you are using div.header for the CSS for the nav bar. That's 
>> fine for texinfo 6.8, but for 7.2, that doesn't exist. I guess that's 
>> why I chose .nav-panel originally. I guess we need to handle both 
>> cases. I have texinfo 7.1 and 7.1.1 around; I'll try those out soon 
>> to see what CSS property is used.
>>
> Okay, I will copy the same style for both div.header and div.nav-panel.
Checked with 7.1. It uses nav-panel too. I think nav-panel will take 
care of all of the versions. (There's a typo in the current manual.css. 
I'll fix it in a bit.)
>>
>> Third, you're using FreeSans for the font (with a fallback to sans 
>> serif) and Courier New with a fallback to monospace. Based on 
>> https://stackoverflow.com/questions/10277002/where-can-i-find-list-with-web-safe-fonts, 
>> maybe we should try to use some web-safe fonts instead. No font is 
>> universally available, but the links there do suggest some of the 
>> most common fonts available on Windows and Mac. (The list is 
>> outdated, I think.) I suspect Windows (presumably the most common 
>> users of the manual?) don't have FreeSans.
>>
> I hadn't paid much attention to the fonts because my intention was to 
> add DejaVu fonts provided by us for all users. But after some testing 
> I think the extra trouble of providing WOFF fonts is not worth it. The 
> page already looks good with Web safe fonts. "FreeSans" was already 
> there in manual.css; I didn't add it. It seems like a relic that is 
> not used anymore. I think a good list of fonts that will work fine for 
> the manual (and be consistent with Maxima's website) is the following:
>
>    text:   Arial, Helvetica, sans-serif
>
>    code: "Courier New", monospace
>
> They work fine in Ubuntu and Windows 10. You can check in Mac and add 
> something else to the list (preferably at the end but before 
> sans-serif or monospace)
>
That list matches one of the suggested font stacks so I think we're set. 
I only have a really old version of macos around. It might not be too 
relevant. I'll check soon though.
​