Identifying words in camel case phrases
Moderators: FourthWorld, heatherlaine, Klaus, kevinmiller, robinmiller
Re: Identifying words in camel case phrases
For "got subverted" read "legitimately expanded".
-
- Posts: 854
- Joined: Wed Nov 04, 2009 11:41 am
- Location: Gunthorpe, North Lincs, UK
Re: Identifying words in camel case phrases
and nothing wrong with that!For "got subverted" read "legitimately expanded".
I do so enjoy posting on this forum! (I don't get out much - but then who does at the moment?)
I think we were lucky to get 8 bit ascii which was a slight upgrade from five bit baudot code and I doubt my BBC Micro with its 6502 processor could have coped with UTF back in the days when 16 kbytes was a massive amount of memory. What I have never understood is why CSV typically uses commas and new lines to delimit data when lower value ascii offers unit separator and record separator just waiting to be used. Standard text editors would not be able to display data but spreadsheets could have used the characters as column and row delimiters on import and export and saved us a lot of pain over the years.UTF should have been implemented at the start, and been the de facto "ASCII"
I have to admitting that I don't really understand XML, its seems to me to be a solution looking for a problem although at least the xml based file formats adopted by Microsoft for Word and Excel may mean the data will be readable in the future.
best wishes
S
best wishes
Skids
Skids
-
- Livecode Opensource Backer
- Posts: 9416
- Joined: Fri Feb 19, 2010 10:17 am
- Location: Bulgaria
Re: Identifying words in camel case phrases
Talking (err; typing) about not getting out much, my 2 BBC Micros are rotting
in my school far away from my loving caresses . . . tough doing classes online from home.
Personally the Unicode "thang" could not have come too soon, as spent far, far too much time
developing Old Church Slavonic and Galgolitic font between 1993 and 1996 to a daft homemade standard
which, along with some bitmap 'horrors', now are causing me a pain-in-the-bum trying to read
as the original fonts are on a Macintosh LC 475 in the attic of my castle in Scotland . . .
- -
and I am 'here' in the mountains of Bulgaria with the Clarisworks documents and not the faintest
of the mapping I used for the glyphs.
Nor, for that matter, even if I did have the bitmapped ones, any idea about how to convert bitmaps to truetype without
having to 'dance' across 3 or 4 Macintoshes & Operating systems of varying vintages.
in my school far away from my loving caresses . . . tough doing classes online from home.
Personally the Unicode "thang" could not have come too soon, as spent far, far too much time
developing Old Church Slavonic and Galgolitic font between 1993 and 1996 to a daft homemade standard
which, along with some bitmap 'horrors', now are causing me a pain-in-the-bum trying to read
as the original fonts are on a Macintosh LC 475 in the attic of my castle in Scotland . . .
- -
and I am 'here' in the mountains of Bulgaria with the Clarisworks documents and not the faintest
of the mapping I used for the glyphs.
Nor, for that matter, even if I did have the bitmapped ones, any idea about how to convert bitmaps to truetype without
having to 'dance' across 3 or 4 Macintoshes & Operating systems of varying vintages.