Punctuation problem with MS Word
Thread poster: Tom in London

Tom in London
United Kingdom
Local time: 22:04
Member (2008)
Italian to English
Jun 22

Has anyone else ever encountered problems when switching between different language versions of MSWord?

I never have - until today.

Apparently the quotation marks and apostrophes that appear correctly on my screen do not appear correctly on my Italian client's screen.

Has anyone else ever come across this problem?


 

Lingua 5B  Identity Verified
Bosnia and Herzegovina
Local time: 23:04
German to Serbian
+ ...
Word version? Jun 22

My guess is this has to do with either Word version or Word settings, they should match in your system and your client's system.

 

Teresa Borges
Portugal
Local time: 22:04
Member (2007)
English to Portuguese
+ ...
No Jun 22

After the last Windows update, I experienced a series of small problems with some peripherals, mainly my printer (stopped working and had to be reinstalled) and my keyboard (because I lived in Belgium for a long while I’ve been using an adapted French keyboard and the system decided to switch automatically to a Portuguese keyboard). I’ve never had the problem you describe though…

 

Tom in London
United Kingdom
Local time: 22:04
Member (2008)
Italian to English
TOPIC STARTER
More details Jun 22

Apparently it's not a Word-to-Word problem but a Word-to-(publishing software) problem.

My apostrophes in Word come out different in their publishing software. Sometimes they even come out as a different symbol (see image).

I'm trying to find out what publishing software they use and if they have recently changed it, or if that software has been updated to a new version.

hcvqkkdvpzd15urcsccw.jpg


 

José Henrique Lamensdorf  Identity Verified
Brazil
Local time: 18:04
English to Portuguese
+ ...
It COULD be a font issue Jun 22

From the days of Word 2 for DOS, Microsoft has had some uncanny ways to handle characters. This page gives some clues.

Furthermore, font matching is often haphazard, using "best match" resources. For instance, the US version of Word includes the Verdana Bold font. In the Brazilian version, this font is named Verdana Negrito (Portuguese for bold). Some programs make this match based on internal font file parameters, others consider the font "unavailable" and go for the best match. The same procedure often takes place between Helvetica (Mac) and Arial (PC).

This leads to some other issues at the Mac x PC frontier checkpoint. In the ancient days of Page Maker, I received a bunch of files generated with a Mac, and many issues came up on my PC. I asked the author about them, and he sent me PC-friendly files generated with a Mac, which were trouble-free.

Apparently Word - depending on the version - has a font-embedding option to avoid these problems.
See https://www.howtogeek.com/106681/how-to-embed-fonts-in-a-microsoft-word-document/
If you are crossing the Mac-PC border, I'd embed the system fonts too.
Files are gonna be big, but that's what the cloud was built for.icon_wink.gif


 

Tom in London
United Kingdom
Local time: 22:04
Member (2008)
Italian to English
TOPIC STARTER
THanks. Jun 22

Thanks José - that's useful

 

Maxi Schwarz
Local time: 16:04
German to English
+ ...
Years ago Jun 22

... an agency's end client complained about the "weird symbols" in place of the Umlauts for German proper names. The client had a much older version of Word which did not recognize the symbols. I think I sent a PDF version that could not be corrupted.

 

Samuel Murray  Identity Verified
Netherlands
Local time: 23:04
Member (2006)
English to Afrikaans
+ ...
Well, that is a known problem Jun 22

Tom in London wrote:
Apparently it's not a Word-to-Word problem but a Word-to-(publishing software) problem.


Yes, some DTP programs have autocorrection enabled, and some DTP programs run autocorrection on existing files. The DTP operator can't speak your language, but he can speak his own, so when the DTP program changes things to match his expecation, he assumes that the program is right. Or, sometimes the DTP operator isn't even aware that his program performs/performed a series of autocorrections.

I often find this in Afrikaans where PDF versions from the client contain single opening quotes (e.g. ‘n) instead of apostrophes (e.g. 'n), even though the Word file I sent them has apostrophes. I find that such programs are less likely to change quotes to quotes (e.g. if I write ’n then it will not change it to ‘n), but sometimes these programs do even that.

W.r.t. "<", I suspect it's not "<" but rather "‹", which is a single guillemet a.k.a. "French quotation mark" -- in some fonts they are more curly, but in other fonts, they look very much like or identical to "<".


 

Tom in London
United Kingdom
Local time: 22:04
Member (2008)
Italian to English
TOPIC STARTER
Very interesting Jun 22

Very interesting, Samuel.

I hope the client finds a way to get round this because otherwise it may be too much hassle for him to continue giving me work...

icon_frown.gif


 

Samuel Murray  Identity Verified
Netherlands
Local time: 23:04
Member (2006)
English to Afrikaans
+ ...
@Tom Jun 22

Tom in London wrote:
I hope the client finds a way to get round this because otherwise it may be too much hassle for him to continue giving me work...


Well, I recommend you tell your client that his DTP program performs an autocorrection, and that he should figure out how to disable that setting.


 

José Henrique Lamensdorf  Identity Verified
Brazil
Local time: 18:04
English to Portuguese
+ ...
Another workflow Jun 23

Tom in London wrote:

I hope the client finds a way to get round this because otherwise it may be too much hassle for him to continue giving me work...


Many people in the trade believe that Word is a kind of DTP app. As its name says, Word is a word/text processor. Its original paradigm is the typewriter. I'd like to introduce my evidence on that:
a) If you add one paragraph, say, on page 12, all the everything beyond that will most likely reflow;
b) You can't work, say, on page 20, then on page 6, and then on page 47, without having to check where everything has gone afterwards;
c) If Word were a DTP app, Microsoft would have discontinued and buried its (horrible!) MS Publisher many years ago.

The original paradigm for DTP is the typesetting and paste-up studio, entirely made "virtual" in Page Maker, InDesign's father. Other DTP programs created their own virtual paradigms, which have no match in real life.

For the record, the various DTP apps in the market use proprietary format files, incompatible with each other, and often incompatible across successive versions of the same software. Among the few converters ever developed for either situation, none is reliably effective. In the rare cases they work, the outcoming file looks cockeyed.

Translators are not DTP operators, and they don't need to be. The need is to get a neatly laid-out publication in another language. The less changes to the original layout, the better. However text often swells or shrinks in translation, which creates the need for graphic adjustments.

While some CAT tools are able to trespass into DTP files, and even PDF files, to get the text translated, this tends to create messy publications, which require adjustments by a DTP operator using the same program adopted to create them.

DTP apps are expensive (at least the good ones), and their learning curve may be a tad too steep for translators. Anyway, they wouldn't have to use any graphic design talent & skills, since the goal is to preserve the layout while translating.

Nowadays nobody sends DTP-app proprietary files out for printing or anything else. Even if the printer has that same DTP software, version conflict is a high risk. The market standard for publication deployment is PDF, which is the ultimate goal of any DTP program, and word processors like MS Word as well.

Two basic strategies have evolved for translation on (editable!) PDF files:
a) Translators work on the PDF using CAT tools that can trespass into them; later a DTP operator uses a PDF editor to fix graphic issues;
b) a 'PDF operator' exports the text from a PDF file , a translator translates it in any compatible way, and then the operator imports that text back into the PDF and fixes it.

I use process (b) and, if the translation involves EN PT, I might be playing both roles or not. The process is shown at http://www.lamensdorf.com.br/direct-pdf-translation.html .

Getting to back the OP, you'll notice that I only offer partnership with translators when the job involves languages that I speak (regardless of whether I translate them or not). So I'll immediately notice if there are any problems with characters being unduly changed, and find a way to solve them. I think it is important that whoever is in charge of the "bridge" between the translation and its final look can do this check, and fix it.


I had an iconic case a few years ago. I translated, and a colleague reviewed EN > PT a book originally laid-out by the author using MS Word. The layout was a bit complex, because it contained a profusion of boxed quotes. As the text got swollen in translation, the resulting DOCX was a mess!

The Canadian PM got a monoglot francophone DTP operator to move our translation into InDesign. The DTP operator used InDesign's Italian dictionary to hyphenate our translations in Portuguese! She sent us a PDF to review. Many wrong hyphens. Every time we spotted a bad hyphen in a paragraph, and she fixed it, a new bad hyphen would come up below, still in the same paragraph.

It took us (translator, reviewer, DTP operator) EIGHT cycles through the entire 200-page book to get rid of the last bad hyphen. This shouldn't happen...


 


To report site rules violations or get help, contact a site moderator:


You can also contact site staff by submitting a support request »

Punctuation problem with MS Word

Advanced search






SDL MultiTerm 2017
Guarantee a unified, consistent and high-quality translation with terminology software by the industry leaders.

SDL MultiTerm 2017 allows translators to create one central location to store and manage multilingual terminology, and with SDL MultiTerm Extract 2017 you can automatically create term lists from your existing documentation to save time.

More info »
Anycount & Translation Office 3000
Translation Office 3000

Translation Office 3000 is an advanced accounting tool for freelance translators and small agencies. TO3000 easily and seamlessly integrates with the business life of professional freelance translators.

More info »



Forums
  • All of ProZ.com
  • Term search
  • Jobs
  • Forums
  • Multiple search