Re: Problems with npm?
Robert Moskowitz via users <[email protected]>
| Newsgroups | gmane.linux.redhat.fedora.general |
|---|---|
| Message-ID | <[email protected]> |
On 5/27/26 1:45 AM, Samuel Sieb wrote: > On 5/26/26 10:19 PM, Tim via users wrote: >> On Tue, 2026-05-26 at 14:16 -0700, Samuel Sieb wrote: >>> The "not svg" is definitely SVG. Why do you think it isn't? The only >>> issue I see is that the top row of numbers isn't quite aligned like the >>> other image. >> >> I also noticed that it's missing the line drawings. They are in there, but for specific setups with the proper stuff. Thus the compatibility option Martin told me to use.. >> >> Eye of Mate tells me it's SVG, yet "file" says they're all ASCII text. >> Strictly speaking they are all text, but I would have thought that the >> file command recognised SVG *content*. It certainly recognises other >> content, such as HTML in a non ".html" named file. > > "file" tells me "SVG Scalable Vector Graphics image, ASCII text" for > both. > svg is basically XML with content to tell a graphics module how to make the graphic. Thus they ARE ascii text files. Which is "neat". In my IETF Internet Draft writing, I can have an image that in classic IETF ascii Draft mode, provides ascii art. But for the HTML of PDF versions of Drafts (supported in IETF for a number of years now), our XML2RFC python script will properly include the svg art. The Draft source file is all text, and xml at that (I don't use the MarkDown stuff). Geany makes it really easy to edit, as I can collapse any xml block (like these svg blocks!) that I am not editing and they get in the way of me "seeing" the text I want to edit. BTW, the first drafts I wrote were back in '94 and you all use the resultant RFC: 1918. Back then it was use Word or such (actually, I think I was still using WordPerfect then) and have it print out a text file. Or be a real UNIX person and use EMACS.... Along the way there were various advances in drafting tools. xml2rfc was a MAJOR improvement. -- _______________________________________________ users mailing list -- [email protected] To unsubscribe send an email to [email protected] Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/[email protected] Do not reply to spam, report it: https://forge.fedoraproject.org/infra/tickets/issues/new