On Thu, 18 Nov 2021 10:25:29 +0000 (GMT), Jim Lesurf
<noise@audiomisc.co.uk> wrote:
In article <sn3vqu$9hs$1@dont-email.me>, NY <me@privacy.invalid> wrote:
http://www.macfh.co.uk/Macfarlane/FamilyHistory/FamilyHistory.shtml
Thanks again to all who have contributed their advice.
Thanks. Interesting. :-)
That said, I'm afraid I find your choice of BG/FG/Text colours quite hard
to read. Since you posted about your 'history' I'll be cheeky and post a
link to my own
http://jcgl.orpheusweb.co.uk/history/ups_and_downs.html
which uses a simpler layout and colours that I find much easier. And may
also interest some here given the xposting. Apologies to anyone who
objects to xposting so many groups. Not something I'd usually do.
As I run a website for my rambling group, I was interested what
triggered your criticism above so clicked on the first link.
It seems rather cramped with small print. Who the hell is McFarlane
and why should I be interested in his history?
The second photo on the
top row took some time to be drawn - I saved it to investigate and
found the photo is 6.5MB - ridiculous for a website.
I navigated to
the home .co.uk page to find that McFarlane is Java Jive, but I could
not find a link to the McFarlane history on the home page.
On the other hand Jim LeSurf's link seems much better to me, but
there's nothing on that page that says who it's about. I navigated to
the home page to see that it's about Jim, but again, there is no link
to the history page on the home page.
My own website is http://midsurreyramblers.co.uk
Neither of you may like it but you can't please all of the people all
of the time, although that's a good thing to aim for at all times.
In article <MzAT7C54tqlhFwUw@255soft.uk>, J. P. Gilliver (John) ><G6JPG@255soft.uk> wrote:
A big difference is between frame rate and flicker rate, though it's
less so with static material such as text. It used to be thought that
refresh rate had to be at least not much less than 50, as otherwise the
flicker was indeed noticeable (and in many cases headache-inducing):
that's why (both) TV systems used interlace (OK, there were bandwidth
reasons too; it was quite a clever invention), and most film projectors
had a shutter that interrupted the light _twice_ a frame.
With the old CRT monitors I tended not to see visible flicker, but the
image somehow got more 'solid' or 'real' when the frame rate was above 60Hz >even when nothing on-screen was being moved or changed.
Jim
That at least is fair criticism, but ICBA to make special copies of the photos in the archive just for the download page, and that photo of The Prince of Wales, later Edward VIII who abdicated, with Brig Gen
Macfarlane happens to be that size in the archive. The photos and
documents were scanned as portable network graphics (PNG) which is a
lossless compression format, so as not to lose detail in the originals,
hence they tend to be bigger than the near universal JP(E)Gs.
It seems rather cramped with small print. Who the hell is McFarlane
and why should I be interested in his history? The second photo on the
top row took some time to be drawn - I saved it to investigate and
found the photo is 6.5MB - ridiculous for a website. I navigated to
the home .co.uk page to find that McFarlane is Java Jive, but I could
not find a link to the McFarlane history on the home page.
On the other hand Jim LeSurf's link seems much better to me, but
there's nothing on that page that says who it's about. I navigated to
the home page to see that it's about Jim, but again, there is no link
to the history page on the home page.
My own website is http://midsurreyramblers.co.uk Neither of you may like
it but you can't please all of the people all of the time, although
that's a good thing to aim for at all times.
On 19/11/2021 19:29, Dave W wrote:[...]
http://www.macfh.co.uk/Macfarlane/FamilyHistory/FamilyHistory.shtml
The second photo on the
top row took some time to be drawn - I saved it to investigate and
found the photo is 6.5MB - ridiculous for a website.
That at least is fair criticism, but ICBA to make special copies of the photos in the archive just for the download page,
The photos and documents were scanned as portable network graphics
(PNG) which is a lossless compression format, so as not to lose detail
in the originals, hence they tend to be bigger than the near universal JP(E)Gs.
"Java Jive" wrote:
On 19/11/2021 19:29, Dave W wrote:
[...]
http://www.macfh.co.uk/Macfarlane/FamilyHistory/FamilyHistory.shtml
The second photo on the
top row took some time to be drawn - I saved it to investigate and
found the photo is 6.5MB - ridiculous for a website.
That at least is fair criticism, but ICBA to make special copies of the
photos in the archive just for the download page,
With the other photos generally being between 0.5 & 1MB, the whole
page weighs in at 18MB. That's excessive and I noticed the slow page
loading.
The photos and documents were scanned as portable network graphics
(PNG) which is a lossless compression format, so as not to lose detail
in the originals, hence they tend to be bigger than the near universal
JP(E)Gs.
That's great for your archive but not so much for people like me who
might be more interested in reading the text. If I were to download
your smaller archive it would take about 1.5 hours on this slow ADSL connection. What would be good is to have smaller sets available and
with thumbnail/smaller/lossy images with ability to download the full
size images individually if required. However, I appreciate the CBA
factor in this.
BTW, that page "absolutely must support Javascript" is not the case.
The danger is that if I use lossy rather than lossless compression, the
text won't be readable. Only a minority of the papers that could be
readily OCR-ed, typed and printed material, was converted into text
files alongside the scanned image, by far the majority of it is either cursive text, handwriting, or photos/sketches. I'd like very much to
convert the handwriting into text, but no cheap and freely available
program is able to do it.
The danger is that if I use lossy rather than lossless compression, the
text won't be readable. Only a minority of the papers that could be
readily OCR-ed, typed and printed material, was converted into text
files alongside the scanned image, by far the majority of it is either cursive text, handwriting, or photos/sketches.
On 20/11/2021 13:25, Apd wrote:
With the other photos generally being between 0.5 & 1MB, the whole
page weighs in at 18MB. That's excessive and I noticed the slow page
loading.
I've taken the half dozen or so worst offenders in the two pages
concerned, those that were over 2MB, and turned them into *.jpg, but
that was the only one on that page.
That's great for your archive but not so much for people like me who
might be more interested in reading the text. If I were to download
your smaller archive it would take about 1.5 hours on this slow ADSL
connection. What would be good is to have smaller sets available and
with thumbnail/smaller/lossy images with ability to download the full
size images individually if required. However, I appreciate the CBA
factor in this.
The danger is that if I use lossy rather than lossless compression, the
text won't be readable. Only a minority of the papers that could be
readily OCR-ed, typed and printed material, was converted into text
files alongside the scanned image, by far the majority of it is either cursive text, handwriting, or photos/sketches. I'd like very much to
convert the handwriting into text, but no cheap and freely available
program is able to do it.
If you want to shrink your large pictures into smaller lossy ones and
still keep the originals for anyone who wants to see them, I have found
the batch process facility in Irfanview (Freeware available from www.irfanview.com) is useful, and it runs on any flavour of Windows from
XP to Win10.
In article<snc011$ju4$1@dont-email.me>, Indy Jess John <bathwatchdog@OMITTHISgooglemail.com> wrote:
If you want to shrink your large pictures into smaller lossy ones and
still keep the originals for anyone who wants to see them, I have found
the batch process facility in Irfanview (Freeware available from
www.irfanview.com) is useful, and it runs on any flavour of Windows from
XP to Win10.
IIRC image magik runs on Linux/Macs/Doze and is also free. Works nicely.
https://imagemagick.org/index.php
I think it is easily available from most distros. I've used it to
automate generating things like sets of 'thumbnails' of related
images by a single command.
Jim
I knew that you had mentioned image magik before, but I hadn't bothered
to look at which OSs it was available for.
I looked at JJ's headers and saw "Windows NT 6.1; Win64; x64; rv:68.0"
so I offered the most popular free Windoze software. It is one I use
myself so I know it is reasonably intuitive for a new user.
In article <sndf35$evf$1@dont-email.me>, Indy Jess John <bathwatchdog@OMITTHISgooglemail.com> wrote:
I knew that you had mentioned image magik before, but I hadn't
bothered to look at which OSs it was available for.
I looked at JJ's headers and saw "Windows NT 6.1; Win64; x64;
rv:68.0" so I offered the most popular free Windoze software. It is
one I use myself so I know it is reasonably intuitive for a new
user.
My memory is unreliable, but IIRC JJ is like myself and uses more
than one OS. Admittedly, for some time now I've only bothered with
two - Linux and RO. Stopped using other OS when ceased having to use
them for the sake of other people.
I started off with ICL 1900s and FORTRAN FWIW. Long time ago, now!
8-]
Jim
On 15:46 21 Nov 2021, Jim Lesurf said:
In article <sndf35$evf$1@dont-email.me>, Indy Jess John
<bathwatchdog@OMITTHISgooglemail.com> wrote:
I knew that you had mentioned image magik before, but I hadn't
bothered to look at which OSs it was available for.
I looked at JJ's headers and saw "Windows NT 6.1; Win64; x64;
rv:68.0" so I offered the most popular free Windoze software. It is
one I use myself so I know it is reasonably intuitive for a new
user.
My memory is unreliable, but IIRC JJ is like myself and uses more
than one OS. Admittedly, for some time now I've only bothered with
two - Linux and RO. Stopped using other OS when ceased having to use
them for the sake of other people.
I started off with ICL 1900s and FORTRAN FWIW. Long time ago, now!
8-]
Jim
I started the same, using McCracken's Guide to Fortan with punched
cards on an ICL 1906. Took a week just to see if the syntax was right.
DEC PDP-11s belonged to another world.
On Sun 21/11/2021 19:12, Pamela wrote:
On 15:46 21 Nov 2021, Jim Lesurf said:
In article <sndf35$evf$1@dont-email.me>, Indy Jess John
<bathwatchdog@OMITTHISgooglemail.com> wrote:
I knew that you had mentioned image magik before, but I hadn't
bothered to look at which OSs it was available for.
I looked at JJ's headers and saw "Windows NT 6.1; Win64; x64;
rv:68.0" so I offered the most popular free Windoze software. It
is one I use myself so I know it is reasonably intuitive for a
new user.
My memory is unreliable, but IIRC JJ is like myself and uses more
than one OS. Admittedly, for some time now I've only bothered with
two - Linux and RO. Stopped using other OS when ceased having to
use them for the sake of other people.
I started off with ICL 1900s and FORTRAN FWIW. Long time ago, now!
8-]
Jim
I started the same, using McCracken's Guide to Fortan with punched
cards on an ICL 1906. Took a week just to see if the syntax was
right.
DEC PDP-11s belonged to another world.
Yes, but they stood up to it.
We had a security organisation using mobile data in the early days.
Their aerial took a lightning strike. The charge went through the
radio links, the radio control system, and the teleprinter and took
out various parts, but the PDP11 just kept on ticking over.
Mind you another system also took a lightning strike and the only
thing that got hurt was the christmas tree memory in the PDP11.
You can't win 'em all I suppose!
I started off with ICL 1900s and FORTRAN FWIW. Long time ago, now! 8-]
Jim
I didn't get on with Cobol which required a different type of mind-set
to Assembler, so I moved from programming to systems analysis for
mainframe stuff. I later went back to programming (in CORAL) on another project that was minicomputer based. Operating system support for real
time systems was enjoyable.
I started the same, using McCracken's Guide to Fortan with punched
cards on an ICL 1906. Took a week just to see if the syntax was right.
DEC PDP-11s belonged to another world.
In article <snei9i$3t1$1@dont-email.me>, Indy Jess John <bathwatchdog@OMITTHISgooglemail.com> wrote:
I didn't get on with Cobol which required a different type of mind-set
to Assembler, so I moved from programming to systems analysis for
mainframe stuff. I later went back to programming (in CORAL) on another
project that was minicomputer based. Operating system support for real
time systems was enjoyable.
For me it was FORTRAN plus NAG routines and ones for the graph plotters. Eventually for those Tektronix 'persistent phospher' terminals that let
you
draw vector graphics onto the green screen. TTYs with cylinder heads,
before the 'golf ball' ones, and line printers.
In article <XnsADE9C356F2BAD37B93@144.76.35.252>, Pamela <pamela.private.mailbox@gmail.com> wrote:
I started the same, using McCracken's Guide to Fortan with punched
cards on an ICL 1906. Took a week just to see if the syntax was
right.
Have a feeling that I've lost my McCracken! I'd forgotten the name
until I read the above! However I still have a small stack of virgin punch-cards!
Used them for years as mm-wave attenuators. We discovered that the
thickness of 1 punc-card attenuated a 95GHz beam by about 0.1dB. So
were able to tweak beam power levels by inserting a given number in
the beam path. :-) (Used black dusbin liner to filter off near IR,
etc.)
I had access to one of the mainframe computers (the OS was Multics)
which could plot to various A4 HP pen-plotters
On 10:35 22 Nov 2021, Jim Lesurf said:
In article <XnsADE9C356F2BAD37B93@144.76.35.252>, Pamela
<pamela.private.mailbox@gmail.com> wrote:
I started the same, using McCracken's Guide to Fortan with punched
cards on an ICL 1906. Took a week just to see if the syntax was
right.
Have a feeling that I've lost my McCracken! I'd forgotten the name
until I read the above! However I still have a small stack of virgin
punch-cards!
Used them for years as mm-wave attenuators. We discovered that the
thickness of 1 punc-card attenuated a 95GHz beam by about 0.1dB. So
were able to tweak beam power levels by inserting a given number in
the beam path. :-) (Used black dusbin liner to filter off near IR,
etc.)
There was almost an entire punched-card economy in those days. They were >useful in so many unintended ways!
On 20/11/2021 16:43, Java Jive wrote:
The danger is that if I use lossy rather than lossless compression, the
text won't be readable. Only a minority of the papers that could be
readily OCR-ed, typed and printed material, was converted into text
files alongside the scanned image, by far the majority of it is either
cursive text, handwriting, or photos/sketches.
There is a historical website I refer to occasionally where they face
the same problem. Their solution is to provide a lossy picture good
enough to show what the original looks like, which allows pages to load
quite quickly, and anybody who then wants to actually read the finer
detail (handwriting on a census page, for instance) just clicks on the
lossy image and a full, detailed image opens in a new tab.
I have just checked one at random, and a 250K lossy picture expands to a
140 megabyte detailed image.
You might find a technique like that solves your readability problem
without a huge overhead on initial display.
If you want to shrink your large pictures into smaller lossy ones and
still keep the originals for anyone who wants to see them, I have found
the batch process facility in Irfanview (Freeware available from www.irfanview.com) is useful, and it runs on any flavour of Windows from
XP to Win10.
I made no concessions to smartphones as I
don't have one
On Sat, 20 Nov 2021 10:20:52 +0000 (GMT), Jim Lesurf
<noise@audiomisc.co.uk> wrote:
FWIW I find the text overlaid the image very hard to read. Took some
time to notice a 'hidden' link was then embedded in part of it. However
I only looked with a light browser with scripting off as that tends to
give a base-rendering view and dodges a lot of cruft, snooping, etc
from some of the more commercial sites.
Jim
Thanks for the feedback. What screen size are you using? PC or phone?
What is a light browser? I made no concessions to smartphones as I don't
have one, except making tables squeezable to fit any screen width.
That said, I'm afraid I find your choice of BG/FG/Text colours quite hard
to read. Since you posted about your 'history' I'll be cheeky and post a
link to my own
On Thursday, 18 November 2021 at 10:28:54 UTC, Jim Lesurf wrote:
That said, I'm afraid I find your choice of BG/FG/Text colours quite
hard to read. Since you posted about your 'history' I'll be cheeky
and post a link to my own
Jim, your capitalisation is a bit strange. For instance 'Dad' and 'University'. Neither word, when used alone and not as part of a name,
are proper nouns.
Bill Aerial rigger, left school at 16...)
On Thursday, 18 November 2021 at 10:28:54 UTC, Jim Lesurf wrote:
That said, I'm afraid I find your choice of BG/FG/Text colours quite hard
to read. Since you posted about your 'history' I'll be cheeky and post a
link to my own
Jim, your capitalisation is a bit strange. For instance 'Dad' and 'University'. Neither word, when used alone and not as part of a name, are proper nouns.
Bill
Aerial rigger, left school at 16...)
There is a campaign to capitalise Braille, as its the name of the inventor of the code in the same way to Morse for Morse code.
I was wondering what brought this thread back to life after all this time.
There is a campaign to capitalise Braille, as its the name of the inventor of the code in the same way to Morse for Morse code.
I was wondering what brought this thread back to life after all this time.
On 13/04/2023 09:46, Brian Gaff wrote:
There is a campaign to capitalise Braille, as its the name of the
inventor
of the code in the same way to Morse for Morse code.
I was wondering what brought this thread back to life after all this
time.
My spellchecker insists on capitalising Negro and derivatives which I
suppose it all right. Christian too. But not unchristian. The Grauniad
likes to capitalise Black but keep white uncapitalised.
On 13/04/2023 15:00, Max Demian wrote:
On 13/04/2023 09:46, Brian Gaff wrote:
There is a campaign to capitalise Braille, as its the name of the
inventor
of the code in the same way to Morse for Morse code.
I was wondering what brought this thread back to life after all
this time.
My spellchecker insists on capitalising Negro and derivatives which I
suppose it all right. Christian too. But not unchristian. The Grauniad
likes to capitalise Black but keep white uncapitalised.
FALSE!
https://www.theguardian.com/world/2023/mar/02/race-today-archive-chronicling-black-britons-lives-launches-online
Headline reads: "Race Today archive chronicling lives of black Britons
to launch online" and in the 15 examples on one page, the only
capitalised 'black' is part of a title of a Day-of-Action.
On 13/04/2023 17:18, Java Jive wrote:
On 13/04/2023 15:00, Max Demian wrote:
The
Grauniad likes to capitalise Black but keep white uncapitalised.
FALSE!
https://www.theguardian.com/world/2023/mar/02/race-today-archive-chronicling-black-britons-lives-launches-online
Headline reads: "Race Today archive chronicling lives of black Britons
to launch online" and in the 15 examples on one page, the only
capitalised 'black' is part of a title of a Day-of-Action.
They're not very consistent. I think it's up to the subeditors to
"correct" the capitalisation.
On 13/04/2023 15:00, Max Demian wrote:
On 13/04/2023 09:46, Brian Gaff wrote:
There is a campaign to capitalise Braille, as its the name of the
inventor
of the code in the same way to Morse for Morse code.
I was wondering what brought this thread back to life after all this
time.
My spellchecker insists on capitalising Negro and derivatives which I
suppose it all right. Christian too. But not unchristian. The Grauniad
likes to capitalise Black but keep white uncapitalised.
FALSE!
https://www.theguardian.com/world/2023/mar/02/race-today-archive-chronicling-black-britons-lives-launches-online
Headline reads: "Race Today archive chronicling lives of black Britons
to launch online" and in the 15 examples on one page, the only
capitalised 'black' is part of a title of a Day-of-Action.
On 13/04/2023 09:46, Brian Gaff wrote:
There is a campaign to capitalise Braille, as its the name of the inventor >> of the code in the same way to Morse for Morse code.
I was wondering what brought this thread back to life after all this time.
My spellchecker insists on capitalising Negro and derivatives which I
suppose it all right. Christian too. But not unchristian. The Grauniad
likes to capitalise Black but keep white uncapitalised.
On 13/04/2023 17:53, Max Demian wrote:
On 13/04/2023 17:18, Java Jive wrote:
On 13/04/2023 15:00, Max Demian wrote:
The Grauniad likes to capitalise Black but keep white uncapitalised.
FALSE!
https://www.theguardian.com/world/2023/mar/02/race-today-archive-chronicling-black-britons-lives-launches-online
Headline reads: "Race Today archive chronicling lives of black
Britons to launch online" and in the 15 examples on one page, the
only capitalised 'black' is part of a title of a Day-of-Action.
They're not very consistent. I think it's up to the subeditors to
"correct" the capitalisation.
You'll have to do better than that. You used the word 'likes', but have given zero evidence in support of your claim, meanwhile I have given contradictory evidence against it. So in the absence of any evidence in support of your claim, we'll just assume that it's another piece of
bigotry.
On 13/04/2023 18:19, Java Jive wrote:
On 13/04/2023 17:53, Max Demian wrote:
On 13/04/2023 17:18, Java Jive wrote:
On 13/04/2023 15:00, Max Demian wrote:
The Grauniad likes to capitalise Black but keep white uncapitalised.
FALSE!
https://www.theguardian.com/world/2023/mar/02/race-today-archive-chronicling-black-britons-lives-launches-online
Headline reads: "Race Today archive chronicling lives of black
Britons to launch online" and in the 15 examples on one page, the
only capitalised 'black' is part of a title of a Day-of-Action.
They're not very consistent. I think it's up to the subeditors to
"correct" the capitalisation.
You'll have to do better than that. You used the word 'likes', but
have given zero evidence in support of your claim, meanwhile I have
given contradictory evidence against it. So in the absence of any
evidence in support of your claim, we'll just assume that it's another
piece of bigotry.
Maybe you don't read the online Guardian much. (I only read it for the spot-the-ball contest (Kenneth Horne joke).)
Examples: https://www.theguardian.com/us-news/2023/apr/12/tennessee-three-justin-pearson-justin-jones
https://www.theguardian.com/commentisfree/2022/jun/02/blackout-tuesday-tv-boardrooms-still-very-white
https://www.theguardian.com/commentisfree/2022/may/23/black-history-diverse-curriculum-football-teacher
https://www.theguardian.com/business/2023/feb/23/buying-black-affirmation-tower-minority-real-estate-development
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 297 |
Nodes: | 16 (2 / 14) |
Uptime: | 09:29:11 |
Calls: | 6,666 |
Files: | 12,213 |
Messages: | 5,336,272 |