Localisation

[Previously posted on Goodreads 2018-07-26.] The chances are that you’re reading this in a web browser. Perhaps it has a menu bar along the top with words like ‘Bookmarks’ or ‘History’, or perhaps it has a hamburger style menu that appears when you click on a button with three horizontal lines. However you interact with an application, the instructions are provided in words or pictures (or a combination). Commonly known icons, such as a floppy disk or printer, are easy to understand for those familiar with computers, but more complex actions, prompts, and warning or error messages need to be written in words.

For example, if you want to check your email, there might be a message that says ‘1 unread email(s)’ or ‘2 unread email(s)’. If the software is sophisticated, it might be able to say ‘1 unread email’ or ‘2 unread emails’. Naturally, you’ll want this kind of information to be in a language you can understand. Another user may be using the same application in, say, France or Germany, in which case they’ll probably want the messages in French or German.

An application that supports localisation is one that is designed to allow such textual information to be displayed in different languages, and (where necessary) to format certain elements, such as dates or currency, according to a particular region. This support is typically provided in a file that contains a list of all possible messages, each identified by a unique key. Adding a new language is simply a matter of finding someone who can translate those messages and creating a new file with the appropriate name.

The recommended way of identifying a particular language or region is with an ISO code. The ISO 639-1 two-letter code is the most commonly used code to identify root languages, such as ‘en’ for English, ‘fr’ for French and ‘de’ for German. (Languages can also be identified by three-letter codes or numeric codes.) The language code can be combined with an ISO 3166 country code. For example, ‘en-GB’ indicates British English (so a printer dialogue box might ask if you want the ‘colour’ setting), ‘en-US’ indicates US English (‘color’) and ‘fr-CA’ indicates French Canadian (‘couleur’).

On Friday 20th July 2018, Paulo Cereda presented the newly released version 4.0 of his arara tool at the TeX User Group (TUG) 2018 conference in Rio de Janeiro. For those of you who have read my LaTeX books, I mentioned arara in Using LaTeX to Write a PhD Thesis and provided further information in LaTeX for Administrative Work. This very useful tool for automating document builds has localisation support for English, German, Italian, Dutch, Brazilian Portuguese, and — Broad Norfolk.

Wait! What was that?

Broad Norfolk is the dialect spoken in the county of Norfolk in East Anglia. There’s a video of Paulo’s talk available. If you find it a bit too technical but are interested in the language support, skip to around time-frame 18:50. Below are some screenshots of arara in action. (It’s a command line application, so there’s no fancy point and click graphical interface.)

Here’s arara reporting a successful job (converting the file test.tex to test.pdf) with the language set to Broad Norfolk:

Image of arara output (reproduced below).

For those who can’t see the image, the transcript is as follows:

Hold yew hard, ole partner, I'm gornta hev a look at 'test.tex'
(thass 693 bytes big, that is, and that was last chearnged on
07/26/2018 12:09:08 in case yew dunt remember).

(PDFLaTeX) PDFLaTeX engine ..... THASS A MASTERLY JOB, MY BEWTY
(Bib2Gls) The Bib2Gls sof....... THASS A MASTERLY JOB, MY BEWTY
(PDFLaTeX) PDFLaTeX engine ..... THASS A MASTERLY JOB, MY BEWTY

Wuh that took 1.14 seconds but if thass a slight longer than you
expected, dunt yew go mobbing me abowt it cors that ent my fault.
My grandf'ar dint have none of these pearks. He had to use a pen
and a bit o' pearper, but thass bin nice mardling wi' yew. Dew
yew keep a troshin'!

For comparison, the default English setting produces:

Image of arara output (reproduced below).

For those who can’t see the image, the transcript is as follows:

Processing 'test.tex' (size: 693 bytes, last modified: 07/26/2018
12:09:08), please wait.

(PDFLaTeX) PDFLaTeX engine .............................. SUCCESS
(Bib2Gls) The Bib2Gls software .......................... SUCCESS
(PDFLaTeX) PDFLaTeX engine .............................. SUCCESS

Total: 1.18 seconds

For a bit of variety, I then introduced an error that causes the second task (Bib2Gls) to fail. Here’s the Broad Norfolk response:

Image of arara output (reproduced below).

For those who can’t see the image, the transcript is as follows:

Hold yew hard, ole partner, I'm gornta hev a look at 'test.tex'
(thass 694 bytes big, that is, and that was last chearnged on
07/26/2018 12:23:42 in case yew dunt remember).

(PDFLaTeX) PDFLaTeX engine ..... THASS A MASTERLY JOB, MY BEWTY
(Bib2Gls) The Bib2Gls sof....... THAT ENT GORN RIGHT, OLE PARTNER

Wuh that took 0.91 seconds but if thass a slight longer than you
expected, dunt yew go mobbing me abowt it cors that ent my fault.
My grandf'ar dint have none of these pearks. He had to use a pen
and a bit o' pearper, but thass bin nice mardling wi' yew. Dew
yew keep a troshin'!

For comparison, the default English setting produces:

Image of arara output (reproduced below).

For those who can’t see the image, the transcript is as follows:

Processing 'test.tex' (size: 694 bytes, last modified: 07/26/2018
12:23:42), please wait.

(PDFLaTeX) PDFLaTeX engine .............................. SUCCESS
(Bib2Gls) The Bib2Gls software .......................... FAILURE

Total: 0.91 seconds

Here’s the help message in Broad Norfolk:

Image of arara output (reproduced below).

For those who can’t see the image, the transcript is as follows:

arara 4.0 (revision 1)
Copyright (c) 2012-2018, Paulo Roberto Massa Cereda
Orl them rights are reserved, ole partner

usage: arara [file [--dry-run] [--log] [--verbose | --silent] [--timeout
 N] [--max-loops N] [--language L] [ --preamble P ] [--header]
 | --help | --version]
 -h,--help          wuh, cor blast me, my bewty, but that'll tell
                    me to dew jist what I'm dewun rite now
 -H,--header        wuh, my bewty, that'll only peek at directives
                    what are in the file header
 -l,--log           that'll make a log file wi' orl my know dew
                    suffin go wrong
 -L,--language      that'll tell me what language to mardle in
 -m,--max-loops     wuh, yew dunt want me to run on forever, dew
                    you, so use this to say when you want me to
                    stop
 -n,--dry-run       that'll look like I'm dewun suffin, but I ent
 -p,--preamble      dew yew git hold o' that preamble from the
                    configuration file
 -s,--silent        that'll make them system commands clam up and
                    not run on about what's dewin
 -t,--timeout       wuh, yew dunt want them system commands to run
                    on forever dew suffin' go wrong, dew you, so
                    use this to set the execution timeout (thass in
                    milliseconds)
 -V,--version       dew yew use this dew you want my know abowt
                    this version
 -v,--verbose       thass dew you want ter system commands to hav'
                    a mardle wi'yew an'orl

For comparison, the default English setting produces:

Image of arara output (reproduced below).

For those who can’t see the image, the transcript is as follows:

arara 4.0 (revision 1)
Copyright (c) 2012-2018, Paulo Roberto Massa Cereda
All rights reserved

usage: arara [file [--dry-run] [--log] [--verbose | --silent] [--timeout
 N] [--max-loops N] [--language L] [ --preamble P ] [--header]
 | --help | --version]
 -h,--help          print the help message
 -H,--header        extract directives only in the file header
 -l,--log           generate a log output
 -L,--language      set the application language
 -m,--max-loops     set the maximum number of loops
 -n,--dry-run       go through all the motions of running a
                    command, but with no actual calls
 -p,--preamble      set the file preamble based on the
                    configuration file
 -s,--silent        hide the command output
 -t,--timeout       set the execution timeout (in milliseconds)
 -V,--version       print the application version
 -v,--verbose       print the command output

In case you’re wondering why Broad Norfolk was included, Paulo originally asked me if I could add a slang version of English as an Easter egg, but I decided to take advantage of this request and introduce Broad Norfolk to the international TeX community as it’s been sadly misrepresented in film and television, much to the annoyance of those who speak it. As far as we know, it’s the only application that includes Broad Norfolk localisation support. (If you know of any other, please say!)

Having decided to add Broad Norfolk, we needed to consider what code to use. The ISO 3166-1 set includes a sub-set of user-assigned codes provided for non-standard territories for in-house application use. These codes are AA, QM to QZ, XA to XZ, and ZZ. I chose ‘QN’ and decided it’s an abbreviation for Queen’s Norfolk, as the Queen has a home in Norfolk.

© OpenStreetMap contributors. (View larger map.)

Norfolk

[Originally posted on Goodreads 2017-06-16.] The Private Enemy is set predominantly in Norfolk, mostly in and around the city of Norwich and in a fictional rural Fenland neighbourhood in the west of Norfolk. The story may be set in the future but, much like today, the people living there aren’t homogeneous. They vary according to their upbringing, social status, employment and surroundings. Norfolk inhabitants are so often unfairly stereotyped in the media as ignorant, Mummerset-speaking, inbred rustics that I thought it might be useful to give a brief overview of the real Norfolk and how the fictional Norfolk of the novel differs from it. (There may be mild spoilers below in terms of the back story, but most of it’s already in the book blurb.)

Norfolk is a largely rural county, and its culture has been influenced by its geography (amongst other things). Situated in the east of England, with the North Sea to the east, north, and north-west, it’s not really a place that travellers pass through on route to somewhere else. In the past, it was even more isolated before the Fens in the west were drained (although that was done a long time ago). The transport links have improved in recent years with a more frequent intercity train service and the duelling of the A11. On the other hand, the rural public transportation within the county has declined.

However, despite its apparent isolation, Norfolk’s culture and language have been shaped by incomers over the centuries: Romans, Angles, Saxons, Danes and Normans have all left their mark. Later, and more peacefully, came the Strangers — refugees from the Low Countries. (The word ‘stranger’ originally meant not a native of that place, but the Strangers in Norfolk has come to mean those particular immigrants.) Their influence can be seen in Norfolk architecture, the language, names and even symbols, such as the canary.

The modern strangers are from further afield, such as Eastern Europe, but there are also incomers from other parts of the UK, include those retiring here, those who fell in love with the county when visiting it on holiday, and those who came here for work placements. (My husband falls into that last category. We moved here in the mid 1990s having both studied at the University of Essex where we met.)

Norfolk is a lovely county with deep roots, but the seeming idyll masks homelessness and poverty. The future Norfolk of The Private Enemy has this same mixture, but in addition it has urban gangsters openly engaging in territorial disputes (which thankfully the real Norfolk doesn’t have).

This deviation from reality is due to events in the back story. Thirty-two years before the start of the novel (at some point in our near future), a fuel crisis triggered global anarchy that lasted two years. Peace was restored and the concept of nationality was abolished. The purported reason for this is that nationalism can cause conflict. Instead the world is divided into numbered sectors with a new capital city (to avoid any associations with the past) in the middle of each region. Sector 1 is the overall administrative centre and is the effective global ruling body.

In reality, far from creating the continually advertised ‘one world united in peace and prosperity’, the sectors (which mostly correspond to the old boundaries) are more fractured than before. Since the story is set mostly in Norfolk, with a few scenes in the capital city for this sector (Sector 55), the focus is on the fractures in this particular region.

The enmity between the rural and urban areas is a result of city raiders invading farmland during the anarchy. The passage of time hasn’t softened the long-held grudges of those who had to defend their homes and families against attack. Within the urban areas, rival gangs emerged during the anarchy to compete for resources, and they still hold sway through corruption and force of arms. So the fictional future Norwich is divided up into neighbourhoods controlled by gangsters and the so-called ‘Neutral Territory’, controlled by financiers and politicians, which acts as a buffer zone.

There are also ideological divides. The ‘Anti-Technology League’ want curbs on technology, claiming that the unsustainable energy demands required by high levels of technology caused the anarchy. Other groups want technological growth (or regrowth). The Anti-Techs seem to get their way some of the time, but Sector 1 are rather selective as to which demands they apparently submit to. Computers are banned, except for government departments (since they’re needed for administrative purposes). This means no Internet, emails or other forms of global electronic communication. Most mobile phone masts were destroyed during the anarchy and haven’t been replaced. This just leaves landlines for instant communication. There are no televisions, but there are cinemas. Radios are back to being analogue, which means they’re subject to static (and if that static happens to interrupt news items, only the paranoid would consider that censorship). And just to show that the Anti-Techs aren’t an all-powerful lobby group, Sector 1 has refused to ban electronic billboards used for product advertising (interspersed with little messages from your friendly politicians).

The Anti-Tech’s message that our modern gadget-filled world caused the anarchy has fuelled nostalgia, and the mismatched retro fashions reflect the desired idylls. This is further back in time for the rural areas than for the city, and the labour-saving devices, such as washing machines, that still exist are used but kept out of sight and not discussed in polite conversation (more a case of keeping back with the Joneses rather than keeping up with them).

The most prominent gangster in future Norwich is Jack Preston. The anarchy broke out when he was eleven years old. A fan of film noirs from the 1930s and 1940s, his adoption of a gangster style image from that era was essentially a coping mechanism, but he becomes so powerful and influential that others copy him, and he now drives the fashion in this region. (Other regions fall back on other styles. The reduced global communications means that sectors start to diverge.)

The next most prominent gangster, and Jack’s rival, is Big Stan O’Brien. He doesn’t want to be seen to be copying Jack, so he taps into his Sector 53 ancestry and adopts a Godfather-like figure, but since this mash-up is from Jack’s preferred era, he’s still effectively mimicking Jack.

So how do people talk in future Norfolk? Much like today, there are a variety of accents. The native Broad Norfolk is still in use, but social status is also a factor. As in real life, there are some professionals who grew up with Broad Norfolk but softened it as they moved up the promotional ladder (for example, this is the case with Detective Inspector Charles Hadley). There are also professionals who don’t soften their accents (Detective Sergeant Sarah Fenning) as they view it as part of their identity. In the city there are those who have a Norwich accent, and then there are those who are trying to copy Jack or Stan’s affectations. There are also incomers with their own accents.

That’s the world of The Private Enemy, but the difficulty came in deciding how to represent these various accents. Writing guides frown on the use of funetik, and they have a point. It can be quite incomprehensible. The first 10,000 words of this novel formed the major part of my portfolio for my diploma in creative writing. The work has also been critiqued on other courses and writing groups, and at various times I’ve used various approaches, including following the much advocated advice to use dictionary spelling and allow the word choice and cadence to establish the voice. After all, if I’m spending all that time studying the art of creative writing, I ought to follow the laws laid down by the experts.

I dutifully corrected all the spelling and sent my first chapter round to my latest group. The result?

Is [Broad Norfolk character] American?

How did that happen? I’d used Norfolk syntax, so why did it sound American? (This wasn’t Jack’s hard-boiled affectation.)

Earlier, I mentioned immigrants to Norfolk, but I didn’t mention the emigrants. When you saw the word Norfolk in this blog’s title, did you immediately think of Norfolk, England (famous for its admiral) or Norfolk, Virginia (famous for its naval base)?

One of the earliest Englishmen to settle in the Virginia colony was Adam Thoroughgood from King’s Lynn, Norfolk (England). The early settlers undoubtedly brought their native accents with them, but over the generations the pronunciation of the sundered groups diverged as new immigrants from other areas arrived and the natural evolution of language occurred. However, despite this change, there are still a few elements common to Broad Norfolk and some parts of America that aren’t so common in the rest of the UK. For example, in Broad Norfolk ‘wholly’ is used in the sense of ‘very’, ‘yard’ can mean garden, and a person might address their friend as ‘ole partner’. So, while there are some very distinctive words and phrases in Broad Norfolk, there are a few cases that can superficially appear American if the pronunciation isn’t clarified.

Another bit of feedback from the group came in the form of corrections in a returned copy where the initial h’s from words in the dialogue were crossed out and replaced with apostrophes. Other dialects may drop their aitches but Norfolk doesn’t drop haitches. In addition, some of the dialect’s idiosyncrasies can look like typographical errors, such as the regularisation of the third person singular present tense (‘she do’, ‘he say’, ‘that look like rain’).

The problem with this creative writing rule is that it relies on the reader being familiar with the accent. Broad Norfolk is a little-known dialect that’s frequently misrepresented. There are so many times that I see this rule presented with some example dialogue followed by a statement that the reader will naturally hear such-and-such well-known accent when reading it.

The other advice to writers is to avoid dialects altogether and always use standard English, but the concept of standard English is a fallacy as English is a pluricentric language. (I’ve seen enough edit wars over the years to verify this.) There are standards within regions but even these can be disputed. Alice may believe that her public school accent is standard English and think that Bob sounds awfully common. Bob may believe his estuary accent is standard and think that Alice sounds a bit posh.

I could’ve saved myself a lot of headaches if I’d stuck with one specific textbook English for all the characters. Not only was the Broad Norfolk causing me problems, but also the hybrid accents for characters like Jack and Stan. However the drawback with standardizing the way everyone talks is that it suggests a lack of diversity, but the whole point of the setting was its fractured nature.

Incidentally, in case there’s any misunderstanding, I’m not a linguistic expert nor can I speak Broad Norfolk. My experience is limited to living in Norfolk for over twenty years and listening to people airing their views on the local radio, nattering on the bus, conversing with cashiers or checkout assistants, or chatting with friends and neighbours. (Any resident of Norfolk who claims that the dialect is extinct must be living in some kind of élite enclave.) I therefore decided to solicit the advice of Norfolk dialect expert Keith Skipper, which was just as well as it turned out that I’d unwittingly picked up some long-defunct words from an old book written by a late Norfolk author.

In the end, I decided on a small amount of spelling deviations. The feedback so far has included:

Didn’t like the dialect.
Really didn’t like the dialect.
Didn’t have a problem with the dialect.
Liked the dialect.
Would’ve liked more guide to the pronunciation.
Would’ve liked footnotes.
Haven’t got round to reading the story yet but really enjoyed reading the glossary of Norfolk terms at the back.

Which just goes to show that readers (like people in general) are diverse, and there’s no one-size-fits-all solution.

Incidentally, the second edition of The Private Enemy is due out on 30th September 2017. The font is smaller (10pt instead of 11pt) and the layout is more compact. This has reduced the page count and overall size and weight, which means a reduction in print and postage costs and this will be reflected in a reduction in the retail price. The revised first edition will continue to be available until the end of September [2017]. More news on the new edition to follow in the next month or so.

Plural Pronouns

[Originally published on Facebook 2015-09-12.] When I was a child I was taught that when conversing in French with any of my adult Belgian relatives I had to use the plural form “vous” when addressing them (rather than the singular “tu”) since the plural form has to be used in formal contexts. Not many people realise this, but English had the same rule. The second person singular is “thou” and the plural is “you”. The plural form was used in formal contexts. Prayer books used the informal singular form to denote the closeness encouraged by instructions such as “call God Father” and the symbolic tearing of the temple veil.

Living languages have an interesting fluidity. They evolve with the people who continually use them. The English language is often criticised for its many exceptions to rules. Some of this is caused by the blending of the different languages that have contributed to its evolution, but some of it comes from so many people breaking a rule that the broken rule becomes standard. (How many use “awful” to mean “full of awe”?) Over time, people began to use the formal “you” in increasingly informal contexts to the point where “thou” was considered old-fashioned. Additionally, its retention in prayer books and the change in attitudes towards religion made “thou” seem stuffy and formal.

This use of the plural form in singular contexts to indicate formality can also be seen in the so-called “royal we”. When the Queen addresses the nation, she refers to herself in a formal context using the plural “we”. Over the past decade or so, more and more non-fiction writers are using the plural third person “they” in a singular context. This is done to avoid the reference to gender and has attracted some criticism from people who feel it’s breaking the language rules, but it actually follows the old linguistic tradition of using the plural instead of the singular in a formal context. So, if you abhor the use of “they” in a singular context, perhaps thou shouldst consider thy use of “you” when addressing only one individual.