Zanski: Blog

A kind reader has pointed out deficiencies in some of the Spanish translations. I am honored that a reader felt involved enough with my story to want to take the time to contact me. Moreover, I am in no position to diagree with the reader's critique because I do not know Spanish. For that same reason, I am unable to agree with the reader.

I use Google Translate. I'm aware it can be inconsistent, that idioms are often lost in translations both ways, that word-for-word translations can be awkward to the point of ridicule, and that colloquial and regional variancces are a problem. On the other hand, amateur human translators, even native speakers, are often subject to some of the same vagaries and may not even be aware of it simply because of their own unconscious and intuitive language facility.

In addition, we have the element of time, of contemporary versus historical language. Just as English varies in diction and vocabulary over the years, decades, and centuries, so do other languages. For instance, the characters in the Arenoso Trail Series are, in presumed context, speaking the borderland variant of Mexican Spanish of the late 19th Century. Supposedly. Obviously, Google Translate does not have that sort of fine-tuning -- nor do human translators, other than those of particular scholarly expertise.

Here, then, is my rationale concerning translated language:

1. The translations into non-English languages are only representative of that language with the presumption of relevant general context.

2. It is not my intention to represent non-English languages with the same facility as I may represent English language. My use of non-English languages is not intended to exemplify them.

3. Using Google Translate affords me the protection of not deliberately including erroneous or offensive content.

4. While I may be glad to discuss most any facet of my novels, I am categorically unable to respond intelligently to issues of non-English vocabulary, diction, and grammar or their practical applications and use. I wish I could.

While still dealing with the health care technical hassles, I have begun reformatting the third book, Feint Trail. This is the longest book in the series. For those not adept at reading between the lines, that means it's going to take a while, especially as I've just noticed I never broke the book into chapters. My original inent was to submit it as a long, multi-page story. But all those indexed chapter headings look impressive on the "More Info" page, so maybe I'll just break it at every ten-thousandth word, just for grins. (Kidding; it would take hours and hours to do all that counting.)

In continuing to become familiar with the SOL Author's utilities, I have now discovered how to update one chapter at a time, hence the wayward date in Chapter 13 in Back Trail has been corrected from "1946" to "eighteen forty six," thus disappointing those who thought it might be a secret Time Travel story.

For those so inclined, consider this: we are all time travelers. It's just that our time machines have only a forward setting at 60 mPH. Nor do I require a DeLorean for temporal transiting; my time machine resembles a La-Z-Boy recliner.

The False Trail HTML file did not produce quite the results I was after (or "after which I was," to avoid ending with a preposition). However, I intend to try a couple more formatting devices and re-post -- but not before a short break to attend to a healthcare procedure I've been neglecting.

Following that, I'll re-touch False Trail, then polish up the next book in the Arenoso Trail Series, Feint Trail.

Just to go on record, the five books of the Arenoso Trail Series are complete, having been a project between 2017 and 2021. However, they were not written in a format that meets the unanticipated requirements of online publication, else I'd have already dumped all of them on you all at once.

Oh, and while I'm fooling around with technical health stuff, I'll likely be neglecting my email, as well. Hopefully everyone will survive that tragedy.

As may be painfully obvious, I have only the minimal acquaintance with the hard and soft technologies that underly my ability to write my thoughts in standard English text which then appears on a video screen. The same goes for those technologies' attendent jargon, even jargon no longer recognized as such by those who have become conversant in its arcane subtleties.

Keeping that in mind, here are my observations of the text formatting following the update of Back Trail dated 3/5/2023:

My bonafides: My Back Trail file was formatted in LibreOffice Writer version 7.4.3.2 (x64), whatever that means. NOT that I'm asking for an explanation--I can already feel my eyelids getting heavy.

I saved it in an odt file by this process: On the standard "writing" screen, I clicked File/Save As/Save as file type: ODF Text Document (from the drop-down list). I saved the file to my Desktop to keep it handy.

Then I uploaded through the SOL wizard.

Here's what I've noticed to date:

Ellipses

The elipsis (...) at the very end of Chapter 18 (and...) converted to a solid line. An ellipsis in Chapter 3 (in the same paragraph as the word "porky," for reference) was preserved in the update.

Italics

As best I can determine, none of the italic formatting transferred. I italicised the cigar brand, Guardia Real, throughout my odt file, but those I've seen are in standard text, not italics.

Text indents

I see no evidence of indented text. Most of the very short Chapter 16 is a handwritten letter formatted both indented and italics in my odt file. I use that format for block quotes from letters and telegram texts. I haven't found any in the update.

ñ (tilde N)

These, most happily, appear to be intact, of the several I searched for. This is perhaps the most gratifying format transfer, for my particular story context. It easily overshadows all other issues herein.

Centering

I only centered the "Chapter #" which were all converted to the SOL standard chapter heading.

To be determined

Will text indent if it is not italics? Any bets? It will be my next format for correspondence quotes.

Just for experience, and per the recommendation from dozens of correspondents, I intend to convert the next book, False Trail, to HTML. I will use LibreOffice Writer's Save As/Save as file type: HTML Document (Writer), then see how that comes out.

After that, I may have to try the unique suggestion of limnophile##### (actual numbers redacted by me), who recommends conversion of text to UTM-8 format. He (presumed gender by me) provided a URL for that purpose, which I will share only with those who will sign a Waiver of Liability, as this limnophile##### comes across as a somewhat shady fellow. Actually, he was quite helpful despite my off-the-wall responses. I have no idea if this is SOL author limnophile, but I have my suspicions.

Thanks to all who offered advice, though I have to confess to having mostly no idea what you all were talking about.