Calendar spam

I'm not sure how common this is, but over the last month or so I've noticed the phenomenon of calendar spam. I first came across it about six weeks ago while I was in Sri Lanka ( the two events are not related) and since then I've had two or three other incidents.

This is how it works:

Someone sends a meeting request (I use google calendar, I'm not sure if it's a gcal only phenomenon). It usually has a fairly obvious subject line like please review by 0830 or Urgent meeting request, ie subject lines that sound vaguely plausible, but not ones that anyone actually uses - not where I work anyway.

Go to your calendar and there it is, that fictional 0830 meeting. Open it up and the meeting details contain one of these scam sob stories about how someone needs help to get some infeasible amount of money out of a bank in Guinea or Nigeria.

Just another irritation of life ...

Written with StackEdit.

Chromebook - first week

It's a week since I first acquired my Chromebook and it's been good so far.
We'll gloss over the embarrassing moments when I tried to click on a button on a web page by touching the screen, or indeed when I tried to swipe between windows.
In fact it's proved pretty good for writing and for web based research - we use dit at the weekend to check out background information for what might possibly be our next trip and write up notes.
While it's not instant on, it's no slower to start than my no name tablet and certainly a lot faster than either of my windows based machines, even from hibernate.
Typing is good, and while there's a couple of oddities with the mousepad I havn't quite mastered yet, switching between windows and opening new windows is pretty good.
To my relief the system appears to cope quite well with our erratic ADSL connection and happily switches to offline editing, which is fine for writing.
I've also been using InoReader, my web based RSS reader of choice these days, on it without any problems.
While I've had it on the kitchen bench I still prefer my tablet for breakfast time email checking, and flicking through a couple of news apps - while we still get a print newspaper delivered, the delivery people appear to have been taking lessons from our ISP, with a very liberal interpretation of before 0700 recently.
And I think that's part of the clue to replacing the Eee linux netbook as a travel computer - the Chromebook does all the work stuff, the writing, the banking and so on, and take a tablet to do Skype and basic surfing, and the stuff that works better in a hand held environment, ie the Chromebook is good, better than a windows netbook, but not a complete replacement ...

Written with StackEdit.

page numbers on ereaders

It's a common complaint that ereaders do no do page numbers.
Actually it isn't tue - it's Kindles that don't do page page numbers. Others do. My venerable Cool-er, which I still use for Gutenberg epubs does page numbers. And the way it does it is mindnumbing simple.
It effectively does a

 linecount=$(cat file | wc -l)
    number_of_pages=$((linecount/40))
    echo $number_of_pages

on the epub document to come up with the number of pages. This is of course entirely arbitrary. The original published edition could have had 42, 50, 54 lines to a page all dependent on the font used and the whim of the original typesetter. It's important to realise that the job of the ereader is to display text in a meaningful fashion, so what they have done is decide that a page is 40 lines long.
That this is an arbitrary decision doesn't matter. We're not trying to reproduce a printed edition here - we are most definitely not talking TEI-C.
Having made the arbitrary decision that there's 40 lines to the page, the Cool-er sticks with it - boost the font size and the page numbers will stay the same, it just means that one 'page' flows over more than one screen and that the 'page number' will increment part way down the second screen.
Why does this matter?
Well, if you are reading for pleasure it doesn't. But J has been teaching nineteenth century novels again. Five or so years ago, you could be fairly confident the kids would all have the Penguin edition, and they would all have more or less the same page numbers, so you could get them to do a critical analysis on the second and third paragraphs of page 96.
Now you can't. Some have kindles, some have other book reading apps on iPads and android tablets and all the devices/applications do something different in the page number space ...

[update - after a conversation with @fatrat this weekend we've managed to establish that some more recent members of the kindle family can display pseudo page numbers for some e-books where page numbers are enabled via the inclusion of an APNX file in the file bundle- however the basic problem still remains]

Written with StackEdit.

So what do you actually use -Q2 update

Following on from my post back in April tracking what I actually use here's my quarter 2 update:

• Dropbox – used mainly to sync files across computers irrespective of file format
• Libre Office – platform agnostic document editor for off line writing. Often used in conjunction with Dropbox
• Evernote – used as a notes and document management system (Nixnote is used on Linux to access my evernote files)
• Wunderlist for 'to do' list management
• Chrome – browser extraordinaire
• Gmail – email solution
• Postbox - lightweight email client for windows to cope with slow connections
• Evolution - linux email client principly used in conjunction with Libre Office
• Google docs – fast means to create quick and dirty documents irrespective of platform
• Windows Live writer – offline blog post creation TextEdit – android text editor for note taking and integrates nicely with evernote and Gmail
• Kate - my favourite editor
• TextWrangler - my secondmost favourite editor
• Stackedit - Google chrome markdown editor
• Pandoc - converts markdown to a range of other formats
• Microsoft Skydrive – used for document backup
• Excel Web App – for these occasions when Google Spreadsheets or Libre Office Calc will not do
• GanntProject for gannt chart generation
• InoReader for RSS feed tracking
• Twitter for tracking interesting things – rarely for messaging
• Hosted Wordpress and blogger for blogging, and wikidot for creating structured web pages
• Hojoki for tracking documents and tasks (Gives unified visibility of GoogleDocs, Skydrive, GitHub, Dropbox and Evernote)

Obviously my Chromebook is too new to have much of an impact. I was finishing off projects and doing documentation most of the last quarter so a lot of my workflows were like this

create meeting notes on seven inch tablet with Textedit as markdown document
  export note to dropbox
    finesse with Kate or TextWrangler
       feed through pandoc to create odt
          Libre Office to apply standard template and generate pdf
             export to evernote/circulate via email using evolution

I came late to Stackedit - a chrome based markdown editor - it has the advantage that one can post directly to a blog or project website and might have speeded up some of the above.

Almost all the initial note taking was on my seven inch tablet, serious report writing was either on my official work macbook or my personal windows laptop, and some of the text conversion and formatting stuff was done with my Ubuntu laptop.

Task and deadline reminders were managed with Wunderlist. At the end of it all I had three and a half weeks in Sri Lanka for which I took my Windows netbook, whiche meant the basic requirements of email and web access for things like flight confirmations.

Written with StackEdit.

Shiny new Chromebook

Well my refurbished Chromebook has arrived - and rather nice it is too.

Connecting to the campus network was fun - connecting to the standard slow network just worked, but our more secure network that uses Radius authentication was rather more of a puzzle.
Being me I of course tried entering all the settings by hand - after all I was the guy who worked out the settings for linux connections.
After trying to do all the clever stuff, with I might add zero success, the answer turned out to be mindbogglingly simple - select the network type (PEAP) enter your username and password and leave everything else as default.

ChromeOS obviously worked it out from the settings and came up with a working configuration.

Other than that initial little snafu it's sleek, it's light and it works - however I'm yet to test it on our flaky home connection and see how it copes with our on again/off again network.

Even though it's a basic model the screen is reasonably sharp and gives the impression of a decent product and it's pretty good weightwise at 1.4kg and thin enough not to squat in your bag like a fat oversized hardback.

The keyboard is a standard chiclet style keyboard and good enough to type on and the trackpad is responsive and generously sized - using it is certainly more of a quality experience than my windows netbook which lumbers when it gets out of bed. Even offline it should make a pleasant writing machine.

As always it's experience that will show just how useful it turns out to be long term ..

Written with StackEdit.

Cosmas Indicopleustes

Long term readers will remember my obsession of a few years ago with Sighelm and his possible travels to India and Ceylon.

(This also ties in with my more recent interest in African contacts with Sri Lanka)

There's not a great deal of information about Byzantine contacts with Sri Lanka, however I've just recently come across Cosmas Indicopleustes made a well documented journey to India in the mid 550's visiting Christian communities in South India and Ceylon.

Cosmas specifically mentions a community of Persian Christians in Ceylon, and extensive trade with Ethiopia - which in this context probably means the ports of the present day Somalia and the Swahili coast, which correlates with the appearance of murals of black women among the so-called concubines at Sigiriya which are possibly roughly from the same period as Cosmas ..

Written with StackEdit.

OCR and Percy B Molesworth

I recently tweeted a link to an article on using OCR from the command line. The article reminded me of my previous experiments with OCR.

In between then and now I'd played with both Zamzar and Adobe File Conversion services trying to convert Florence Caddy's account of her time in Sri Lanka to editable text. Both failed for various reasons, as did the Calibre e-book management application.

So I thought I would try OCR out on Florence Caddy's book - in the end I didn't have to as I found a version in epub format that met my requirements. I was probably being a little ambitious as one of the problems with OCR is font recognition and artefacts caused either by blobbiness in the print, or dirt picked up in the scanning process and I suspect the original scanned PDF I had would have had a reasonable number of these.

However I did try and baseline how much work it would be by OCR'ing the obituary of Percy B Molesworth provided by the NASA Astrophysics data system. In this the pages have been scanned as images with headers and footers added. (Percy Molesworth was a late nineteenth century British astronomer who worked in Sri Lanka.)

The actual text of the article is about one A4 page but spread across two pages. To process it I used OCRfeeder running on my Linux laptop and inside of OCRfeeder selected the tesseract OCR engine and the initial results were not too bad - good enough to play with without needing to try an alternative engine.

OCRfeeder by default exports in ODT format making Libre Office an obvious choice as document fixup and editing tool.

Using Libre Office I cut and pasted the relevant chunk of text into a new document, and fixed the formatting so that the paragraph structure reflected that of the original document (While I was doing this I found it incredibly useful to have the original pdf open on a second laptop while I worked on the Libre Office document.

I then ran the Libre Office spell checker which fixed up most of the minor errors such as aud for and. This basically left a few complete bits of garbage to be fixed manually - dates for some reason were bizarre, and the fact that Percy had a twelve and a half inch instrument produced a string of garbage.
However, at the end of the exercise I had a usable document which I could save and export from Libre Office as required.

The key thing is the time it took - 30 minutes to do a page of A4 text, meaning that your average five to six hundred page nineteenth century travel book would take a little over eight weeks assuming the same amount of work per page, and a standard working week. The major time consumer was not the initial OCR process - that took me around five minutes, and most of the time was due to my reminding myself how the application worked, the majority of the time went into the fix up and edit process.
With that sort of time, retyping the text is probably a viable option ...

Written with StackEdit.