CafeTran

After the series How to deal with segments that don't need translation - 4 we'll continu with the series How to deal with words that don't need translation?

Planned episodes are:

• What are non-translatables and how to create and insert them?
• How to create non-translatables from regular expressions?
• How to deal with non-translatables that consist of several words?

• How to handle non-translatables via bilingual review documents?

The topics:

• How to create non-translatables from regular expressions?
• How to deal with non-translatables that consist of several words?

Will be discussed in the dedicated forum: https://cafetran.freshdesk.com/discussions/forums/6000242194 

Non-translatables (or non-translatable fragments) are strings (combinations of letters or letters and numbers) that don't need to be translated. CafeTran Espresso 2019 colours them purple. By default, all numbers are handled as non-translatables and coloured accordingly:

Candidates for non-translatables are:

• Brand names
• Type names
• Personal names
• City names (as long as they are not being localised)
• Other names and 'invariants' (words or codes that don't need to be translated).

Movie: https://youtu.be/DWUdRWNiCS0

Demo files for practising attached.

Creating a new glossary for non-translatables

• Choose Glossary > New Glossary to create a new glossary.
• Check the checkbox Non-translatable fragments only.
• Press the CTRL key, keep it down and click on the yellow pencil icon above the target segment editor.
• In the Target box type a non-translatable, like a name, product type, town, etc.
• Use F4 to insert non-translatables into to target segment editor.

• Choose Glossary > Add Glossary ... to add an existing glossary.
• Check the checkbox Non-translatable fragments only.
• Use F4 to insert non-translatables into to target segment editor.

For more advanced use of glossaries with non-translatables see: https://cafetran.freshdesk.com/support/discussions/topics/6000056846

Note that strings that you've added to a non-translatables glossary, will be ignored during spell-checking. For those strings that contain numbers, this is always the case (even when they aren't defined as non-translatables).

This fact can be used to speed up your spell-checking! You don't have to add words to your spelling custom dictionary. You can decide that a certain word should be flagged for certain clients and projects, by not adding it to your spelling custom dictionary, but to a client- or project-specific non-translatables glossary.

Here is a starter set of generic non-translatables:

# SI and technical units:

A

Bq

C

cd

cm

daN

dm

F

Gy

H

hm

Hz

J

K

kat

kg

kHz

km

kV

kW

lm

lx

m

mm

mol

N

Pa

rad

s

S

sr

Sv

T

V

W

Wb

μm

Ω

# End of SI and technical units

Other candidates:

°C

½

¼

¾

Ah

AlCuMgPb

ANSI

ASTM

Cd

dB

dBm

DHCP

DIN

DIN-EN

EN

fps

ft

ft²

g

GHz

Hz

IAN

Incoterms

ISO

IX

kbit

kN

Kp

kPa

kVA

lbs

m³

mbar

Mbit

Mbit/s

MHz

ml

mm

MM-JJJJ 

mPas

mS

msec

mW

MΩ

nF

Nm

nm³

pF

ppb

ppm

psi

QVGA

VDI

VGA

Wh

x

xx

xxxx

xxxxx

Zn

Δp

µm

μS

μS/cm

Ω