http://home.chiemgau-net.de/ausserstorfer/TryDraw.html
In article <59bdb87215bavariasound@chiemgau-net.de>, Alexander
Ausserstorfer <bavariasound@chiemgau-net.de> wrote:
http://home.chiemgau-net.de/ausserstorfer/TryDraw.html
I know close to nothing about HTML, but I guess that draw files are too exotic for the global browsers to recognise them. Anyhow, even NetSurf
and Iris refuse to show anything from the link above - and that is RISC
OS speaking. What if you convert the draw file to SVG first?
I included a draw file to a HTML page by the line <IMG SRC="Ribing">.
From local harddisc, it is working here, but not from my web space:
http://home.chiemgau-net.de/ausserstorfer/TryDraw.html
May be that the missing extension is the problem? I have no idea what extension .???? draw files are using.
Any suggestions / ideas, please?
In article <59bdbccfe4Paul@sprie.nl>, Paul Sprangers <Paul@sprie.nl>
wrote:
In article <59bdb87215bavariasound@chiemgau-net.de>, Alexander
Ausserstorfer <bavariasound@chiemgau-net.de> wrote:
http://home.chiemgau-net.de/ausserstorfer/TryDraw.html
I know close to nothing about HTML, but I guess that draw files are too exotic for the global browsers to recognise them. Anyhow, even NetSurf
and Iris refuse to show anything from the link above - and that is RISC
OS speaking. What if you convert the draw file to SVG first?
I just tried converting that file "Ribing" to SVG using ArtWorks2 but it needs a little work as the roads are too thin.
http://w.tjrh.uk/temp/Ribing.svg
I find it better usually to use bitmaps to save having to re-edit things
like this. IIRC Fresco used to handle Draw files in web pages.
You would not have to re-edit them if they had a sensible width. The
SVG shows exactly what the creator of this file wanted you to see.
Those lines simply are very, very thin in the Draw file: 0.1pt, which
is way below the recommended minimum of 0.25pt for printed material. In
Draw, you do not notice, since the lines are shown without
anti-aliasing, so anything less than a pixel wide is still shown a full
pixel wide.
Tim Hill <tim@invalid.org.uk> wrote:
In article <59bdbccfe4Paul@sprie.nl>, Paul Sprangers <Paul@sprie.nl>
wrote:
In article <59bdb87215bavariasound@chiemgau-net.de>, Alexander
Ausserstorfer <bavariasound@chiemgau-net.de> wrote:
http://home.chiemgau-net.de/ausserstorfer/TryDraw.html
I know close to nothing about HTML, but I guess that draw files are too exotic for the global browsers to recognise them. Anyhow, even NetSurf and Iris refuse to show anything from the link above - and that is RISC OS speaking. What if you convert the draw file to SVG first?
I just tried converting that file "Ribing" to SVG using ArtWorks2 but it needs a little work as the roads are too thin.
http://w.tjrh.uk/temp/Ribing.svg
I find it better usually to use bitmaps to save having to re-edit things like this. IIRC Fresco used to handle Draw files in web pages.
You would not have to re-edit them if they had a sensible width. The SVG shows exactly what the creator of this file wanted you to see.
Those lines simply are very, very thin in the Draw file: 0.1pt, which is way below the recommended minimum of 0.25pt for printed material. In Draw, you
do not notice, since the lines are shown without anti-aliasing, so anything less than a pixel wide is still shown a full pixel wide.
In article <59bdbccfe4Paul@sprie.nl>, Paul Sprangers <Paul@sprie.nl>
wrote:
In article <59bdb87215bavariasound@chiemgau-net.de>, Alexander
Ausserstorfer <bavariasound@chiemgau-net.de> wrote:
http://home.chiemgau-net.de/ausserstorfer/TryDraw.html
I know close to nothing about HTML, but I guess that draw files are too
exotic for the global browsers to recognise them. Anyhow, even NetSurf
and Iris refuse to show anything from the link above - and that is RISC
OS speaking. What if you convert the draw file to SVG first?
I just tried converting that file "Ribing" to SVG using ArtWorks2 but it needs a little work as the roads are too thin.
Alexander Ausserstorfer <bavariasound@chiemgau-net.de> wrote:
Alternatively you could ask them to put the AddType line in the server's config for you.
Of course, that's only going to work on browsers that understand RISC OS
Draw files - just NetSurf at this point?
Is it possible to put StrHelp files to the Internet and to read it there (direct online) with StrongHelp without the need of first downloading
the files (with other tools)?
On 20 Feb 2022, tim@invalid.org.uk wrote:
In article <59bdbccfe4Paul@sprie.nl>, Paul Sprangers <Paul@sprie.nl>
wrote:
In article <59bdb87215bavariasound@chiemgau-net.de>, Alexander
Ausserstorfer <bavariasound@chiemgau-net.de> wrote:
http://home.chiemgau-net.de/ausserstorfer/TryDraw.html
I know close to nothing about HTML, but I guess that draw files are too
exotic for the global browsers to recognise them. Anyhow, even NetSurf
and Iris refuse to show anything from the link above - and that is RISC
OS speaking. What if you convert the draw file to SVG first?
I just tried converting that file "Ribing" to SVG using ArtWorks2 but it needs a little work as the roads are too thin.
I tried Clive Semmens' !XP1DrSVG on the Ribing Draw file and it output an
SVG file that displays:
-- blank in Netsurf
-- not at all in Iris: can't display either &AFF (DrawFile) or &AAD (SVG)
-- without text in Chrome and Edge, but with message "Error on line 720 at column 215: Encoding error. Below is a rendering of the page up to the
first error", which appears to be balking at any legend that includes a German sharp ess.
If I replace ß by ss (and also © by C in the OpenStreetMap legend) in
Clive's output, then, lo and behold, the map displays correctly in Windows browsers, and almost so in Netsurf where the street names are horizontal rather than following the road.
I will let Clive know.
In message <b6325bc059.boase@bernard>Yes, I just tested with !Iris browser, it works. The file opens slower
on 25 Feb 2022 Bernard Boase wrote:
On 20 Feb 2022, tim@invalid.org.uk wrote:
In article <59bdbccfe4Paul@sprie.nl>, Paul Sprangers <Paul@sprie.nl>
wrote:
In article <59bdb87215bavariasound@chiemgau-net.de>, Alexander
Ausserstorfer <bavariasound@chiemgau-net.de> wrote:
http://home.chiemgau-net.de/ausserstorfer/TryDraw.html
I know close to nothing about HTML, but I guess that draw files are too >>>> exotic for the global browsers to recognise them. Anyhow, even NetSurf >>>> and Iris refuse to show anything from the link above - and that is RISC >>>> OS speaking. What if you convert the draw file to SVG first?
I just tried converting that file "Ribing" to SVG using ArtWorks2 but it >>> needs a little work as the roads are too thin.
I tried Clive Semmens' !XP1DrSVG on the Ribing Draw file and it output an
SVG file that displays:
-- blank in Netsurf
-- not at all in Iris: can't display either &AFF (DrawFile) or &AAD (SVG)
-- without text in Chrome and Edge, but with message "Error on line 720 at >> column 215: Encoding error. Below is a rendering of the page up to the
first error", which appears to be balking at any legend that includes a
German sharp ess.
If I replace ß by ss (and also © by C in the OpenStreetMap legend) in
Clive's output, then, lo and behold, the map displays correctly in Windows >> browsers, and almost so in Netsurf where the street names are horizontal
rather than following the road.
I will let Clive know.
Thanks - he needs to make sure that any characters numbered greater than 127 are encided in UTF-8 in the SVG file.
There is an option in RiscOSM's general choices to use Unicode font encodings. As it says in the manual:
As OpenStreetMap is an international project, your map may contain data in characters other than Acorn Latin1 - especially if you go outside Western Europe. If you have RISC OS 5 or the Unicode font manager on your computer, you can take advantage of these Unicode characters in your map display. However, if you wish to export Draw files using Unicode characters be warned that not all RISC OS applications cope with them properly. The default setting will convert all characters to Acorn Latin1 for maximum compatability with other applications, but this will mean that some diacritics will be lost.
I think at the moment the setting affects both the display of the map on screen and the export as a Draw file. You might find that changing the setting to use Unicode font encodings, regenerating the Draw file, and then converting with Clive's utility, would result in a valid SVG file. Ideally Clive's tool needs to pay attention to the font encoding declared in the Draw file font table, and convert the text if needed.
We'd be happy to help with advice and code snippets if Clive wants to get in touch.
We're aware that NetSurf doesn't display the rotated road names correctly. When we viewed the ArtWorks generated file on NetSurf all the lines were the same thinkness and the dash patterns for footpaths etc. were not correct. These were fine on Firefox on a Linux machine, so the ArtWorks SVG output looks correct.
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 296 |
Nodes: | 16 (2 / 14) |
Uptime: | 71:57:15 |
Calls: | 6,657 |
Calls today: | 3 |
Files: | 12,203 |
Messages: | 5,332,297 |
Posted today: | 1 |