-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathissues-list-2015-05-27.html
2696 lines (2689 loc) · 220 KB
/
issues-list-2015-05-27.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="utf-8" />
<title>Multidimensional Quality Metrics Definition</title>
<link rel="stylesheet" type="text/css" href="http://www.qt21.eu/mqm-definition/mqm.css">
</head>
<body>
<h1>Multidimensional Quality Metrics (MQM) Issue types</h1>
<div style="background-color:yellow;padding:12px;">
<p>This document is for public comment, with comments due June 30, 2015 at 23:99 CET. Comments will be used to create future versions. Comments can be made via the MQM definition’s Github repository at <a href="https://github.com/multidimensionalquality/mqm-def/issues" target="_blank">https://github.com/multidimensionalquality/mqm-def/issues</a>.</p>
</div>
<ul>
<li>This version: <a href="http://www.qt21.eu/mqm-definition/issues-list-2015-05-27.html">http://www.qt21.eu/mqm-definition/issues-list-2015-05-27.html</a> (version 0.5.0, 2015-05-27)</li>
<li>Previous version: <a href="http://www.qt21.eu/mqm-definition/issues-list-2015-05-20.html">http://www.qt21.eu/mqm-definition/issues-list-2014-05-20.html</a> (version 0.4.0, 2015-05-20)</li>
<li>Current version: <a href="http://www.qt21.eu/mqm-definition/issues-list.html">http://www.qt21.eu/mqm-definition/issues-list.html</a></li>
</ul>
<h2>Copyright</h2>
<p>Copyright ©2015, Deutsches Forschungszentrum für Künstliche Intelligenz GmbH / German Research Center for Artificial Intelligence (DFKI)
<br /><a rel="license" href="http://creativecommons.org/licenses/by-nd/4.0/deed.en_US"><img alt="Creative Commons License" style="border-width:0" src="http://i.creativecommons.org/l/by-nd/4.0/88x31.png" /></a><br />This work is licensed under a <a rel="license" href="http://creativecommons.org/licenses/by-nd/4.0/deed.en_US">Creative Commons Attribution-NoDerivatives 4.0 International License</a>. Note that implementations based on this document are freely permitted as are derivative works provided they do not use the names “MQM”, “Multidimensional Quality Metrics”, “DQF”, or “Dynamic Quality Framework” or otherwise imply endorsement of the derivative work.</p>
<h2>Editors</h2>
<ul>
<li>Arle Lommel (DFKI)</li>
<li>Aljoscha Burchardt (DFKI)</li>
<li>Attila Görög (TAUS)</li>
<li>Hans Uszkoreit (DFKI)</li>
<li>Alan K. Melby (LTAC Global)</li>
</ul>
<h2>Acknowledgements</h2>
<p>Special thanks are due to the following individuals for their contributions:</p>
<ul>
<li>Serge Gladkoff (Logrus)</li>
<li>Leonid Glazychev (Logrus)</li>
<li>Kim Harris (text&form)</li>
<li>Dale Schultz (IBM)</li>
<li>Jean-François Vanreusel (Adobe)</li>
</ul>
<h2>Document status</h2>
<p>This document contains a draft list of the MQM issue types. It is subject to frequent and substantial revision and should not be relied upon for implementation.</p>
<h2>Feedback</h2>
<p>Feedback on this document should be submitted to <a href="mailto:info@qt21.eu">info@qt21.eu</a>.</p>
<h2>Overview</h2>
<p>This document defines the issue types used by the Multidimensional Quality Metrics (MQM) framework. It contains a description of the issue types. For a full definition of MQM, please read the MQM definition file at <a href="http://www.qt21.eu/mqm-definition/definition-2015-05-27.html">http://www.qt21.eu/mqm-definition/definition-2015-05-27.html</a>.</p>
<h2>1. MQM Issue types (normative)</h2>
<p class="note">This version contains major changes from previous versions. Please consult the change log at the end of this document for a detailed listing of changes.</p>
<p>MQM defines a total of over 100 issue types, as defined in this section. They are derived from an examination of major quality assessment systems, both ones based on automatic detection of issues and ones based on manual assessment by reviewers. As quality assessment systems differ considerably in the issues they check, the MQM issue types represent a (non-strict) superset of issues found in translations (as product, as opposed to process). The superset is non-strict because it represents an abstraction of various systems and, in some cases, is less granular than actual systems. For example, an existing system might distinguish between four kinds of issues related to whitespace, but MQM would categorize all of them as <span class="generated-issue-name">Whitespace <a href="#whitespace">(<code>whitespace</code></a>)</span>. Information on extending MQM is available in the <a href="http://www.qt21.eu/mqm-definition/">MQM definition</a>.</p>
<p>In this document MQM issue types are referred to by name followed by the MQM ID value in parentheses on a gray background, e.g., <span class="generated-issue-name">Issue name (<code><a id="fake"></a><a href="#fake">issue-name</a></code>)</span>. The issue ID values are linked to the full description of the issue below.</p>
<p>MTM issues exist in a hierarchy, with more specific issues lower in the hierarchy constituting “subtypes” of their parents. For example the issue type <span class="generated-issue-name">Mistranslation <a href="#mistranslation">(<code>mistranslation</code></a>)</span> is a subtype of the more general issue type <span class="generated-issue-name">Accuracy <a href="#accuracy">(<code>accuracy</code></a>)</span>. Because the issues exist in a hierarchy, rather than as a flat list, MQM can be realized at any level of granularity. At one extreme an MQM-compliant metric could check only two high-level issues, <span class="generated-issue-name">Accuracy <a href="#accuracy">(<code>accuracy</code></a>)</span> and <span class="generated-issue-name">Fluency <a href="#fluency">(<code>fluency</code></a>)</span>; at the other extreme a metric could check all issues defined in MQM. In most cases the number of issues checked will be somewhere between these extremes. Guidance on selecting issue sets can be found in <a href="http://www.qt21.eu/mqm-definition/">MQM definition</a>. As a general rule, metrics should check the fewest number of issues possible to achieve the requirements of users.</p>
<p>This section presents the <a href="#hierarchical_list">hierarchy of MQM issues</a>, followed by the <a href="#issues_list">detailed description of each issue type</a>.</p>
<p>At the top level, MQM issues are grouped into eight major branches or “dimensions”: <span class="generated-issue-name">Accuracy <a href="#accuracy">(<code>accuracy</code></a>)</span>, <span class="generated-issue-name">Fluency <a href="#fluency">(<code>fluency</code></a>)</span>, <span class="generated-issue-name">Terminology <a href="#terminology">(<code>terminology</code></a>)</span>, <span class="generated-issue-name">Locale convention <a href="#locale-convention">(<code>locale-convention</code></a>)</span>, <span class="generated-issue-name">Style <a href="#style">(<code>style</code></a>)</span>, <span class="generated-issue-name">Verity <a href="#verity">(<code>verity</code></a>)</span>, <span class="generated-issue-name">Design <a href="#design">(<code>design</code></a>)</span>, and <span class="generated-issue-name">Internationalization <a href="#internationalization">(<code>internationalization</code></a>)</span>. It also contains <span class="generated-issue-name">Other <a href="#other">(<code>other</code></a>)</span>, used for issues that cannot be assigned elsewhere, and <span class="generated-issue-name">Compatibility (Deprecated) <a href="#compatibility">(<code>compatibility</code></a>)</span>, a branch that contains deprecated issues that are retained for compatibility with legacy systems, notably the LISA QA Model. These seven dimensions represent the top level in the MQM hierarchy and themselves may serve as issue types in cases where no further granularity is needed.</p>
<p>These dimensions may be graphically represented as follows (dimensions in bold are in the “MQM Core”):</p>
<a href="http://qt21.eu/mqm-definition/images/2015-05-27/Dimensions-2015-05-27.svg" target="_blank"><img src="http://qt21.eu/mqm-definition/images/2015-05-27/Dimensions-2015-05-27.png" alt="MQM dimensions" /></a>
<p>Issue type names are not case-sensitive (i.e., “Mistranslation”, “MISTRANSLATION”, “mistranslation”, and “MiStRaNsLaTiOn” are all equivalent). The ID values, however, are case sensitive (and are always lower-case) and do not contain spaces. As a result, implementers should ensure that they do not confuse the two, even though in most cases they are nearly identical.</p>
<div id="hierarchical_list">
<h3>1.1. Hierarchical list of issue types</h3>
<p>The following list of issue types presents the full list of MQM categories in hierarchy. Clicking on any issue type name in the lists will take the reader to the definition of the issue type in the next section. The list is separated into sections by dimension. For those dimensions where current sub-issues are defined, a “mind map” shows the hierarchy of the dimension. Clicking on the embedded image will open and SVG version in a new window. Issues in bold in the graphics or the list are part of the “MQM core”. The graphical versions include both the issue name, which might be localized or displayed in some other fashion in an application, and the ID, which MUST remain as given to provide an unambiguous reference to a particular issue type.</p>
<h4>1.1.1. Accuracy</h4>
<p>Accuracy issues address the relationship of the target text to the source text and can be assessed only by considering this relationship. Changes in intended meaning, addition and omission of content, and similar issues are considered in it.</p>
<a href="http://qt21.eu/mqm-definition/images/2015-05-27/Accuracy-2015-05-27.svg" target="_blank"><img src="http://qt21.eu/mqm-definition/images/2015-05-27/Accuracy-2015-05-27.png" alt="Accuracy dimension" /></a>
<ul>
<li><strong><span class="generated-issue-name">Accuracy <a href="#accuracy">(<code>accuracy</code></a>)</span></strong>
<ul>
<li><strong><span class="generated-issue-name">Addition <a href="#addition">(<code>addition</code></a>)</span></strong></li>
<li><span class="generated-issue-name">Improper exact TM match <a href="#improper-exact-tm-match">(<code>improper-exact-tm-match</code></a>)</span></li>
<li><strong><span class="generated-issue-name">Mistranslation <a href="#mistranslation">(<code>mistranslation</code></a>)</span></strong>
<ul>
<li><span class="generated-issue-name">Ambiguous translation <a href="#ambiguous-translation">(<code>ambiguous-translation</code></a>)</span></li>
<li><span class="generated-issue-name">Date/time <a href="#date-time">(<code>date-time</code></a>)</span></li>
<li><span class="generated-issue-name">Entity (such as name or place) <a href="#entity">(<code>entity</code></a>)</span></li>
<li><span class="generated-issue-name">False friend <a href="#false-friend">(<code>false-friend</code></a>)</span></li>
<li><span class="generated-issue-name">Mistranslation of technical relationship <a href="#technical-relationship">(<code>technical-relationship</code></a>)</span></li>
<li><span class="generated-issue-name">Number <a href="#number">(<code>number</code></a>)</span></li>
<li><span class="generated-issue-name">Overly literal <a href="#overly-literal">(<code>overly-literal</code></a>)</span></li>
<li><span class="generated-issue-name">Should not have been translated <a href="#no-translate">(<code>no-translate</code></a>)</span></li>
<li><span class="generated-issue-name">Unit conversion <a href="#unit-conversion">(<code>unit-conversion</code></a>)</span></li>
</ul>
</li>
<li><strong><span class="generated-issue-name">Omission <a href="#omission">(<code>omission</code></a>)</span></strong>
<ul>
<li><span class="generated-issue-name">Omitted variable <a href="#omitted-variable">(<code>omitted-variable</code></a>)</span></li>
</ul>
</li>
<li><span class="generated-issue-name">Over-translation <a href="#over-translation">(<code>over-translation</code></a>)</span></li>
<li><span class="generated-issue-name">Under-translation <a href="#under-translation">(<code>under-translation</code></a>)</span></li>
<li><strong><span class="generated-issue-name">Untranslated <a href="#untranslated">(<code>untranslated</code></a>)</span></strong>
<ul>
<li><span class="generated-issue-name">Untranslated graphic <a href="#untranslated-graphic">(<code>untranslated-graphic</code></a>)</span></li>
</ul>
</li>
</ul>
</li>
</ul>
<h4>1.1.2. Compatibility (Deprecated)</h4>
<p>The Compatibility dimension includes issues taken from legacy metrics that are not considered appropriate for general use in MQM (because they are related to areas not covered by MQM, such as deadlines, software functionality, or physical production). They are included only for compatibility with these older metrics and should not be used for new MQM metrics.</p>
<ul>
<li><span class="generated-issue-name">Compatibility (Deprecated) <a href="#compatibility">(<code>compatibility</code></a>)</span></li>
</ul>
<h4>1.1.3. Design</h4>
<p>Design includes issues related to the physical presentation of text, typically in a “rich text” or “markup” environment.</p>
<a href="http://qt21.eu/mqm-definition/images/2015-05-27/Design-2015-05-27.svg" target="_blank"><img src="http://qt21.eu/mqm-definition/images/2015-05-27/Design-2015-05-27.png" alt="Design dimension" /></a>
<ul>
<li><span class="generated-issue-name">Design <a href="#design">(<code>design</code></a>)</span> <ul>
<li><span class="generated-issue-name">Graphics and tables <a href="#graphics-tables">(<code>graphics-tables</code></a>)</span> <ul>
<li><span class="generated-issue-name">Call-outs and captions <a href="#call-outs-captions">(<code>call-outs-captions</code></a>)</span></li>
<li><span class="generated-issue-name">Missing graphic/table <a href="#graphics-tables-missing">(<code>graphics-tables-missing</code></a>)</span></li>
<li><span class="generated-issue-name">Position of graphic/table <a href="#graphics-tables-position">(<code>graphics-tables-position</code></a>)</span></li>
</ul>
</li>
<li><span class="generated-issue-name">Hyphenation <a href="#hyphenation">(<code>hyphenation</code></a>)</span></li>
<li><span class="generated-issue-name">Length <a href="#length">(<code>length</code></a>)</span></li>
<li><span class="generated-issue-name">Local formatting <a href="#local-formatting">(<code>local-formatting</code></a>)</span> <ul>
<li><span class="generated-issue-name">Font <a href="#font">(<code>font</code></a>)</span> <ul>
<li><span class="generated-issue-name">Bold/italic <a href="#bold-italic">(<code>bold-italic</code></a>)</span></li>
<li><span class="generated-issue-name">Font, single/double-width (CJK only) <a href="#single-double-width">(<code>single-double-width</code></a>)</span></li>
<li><span class="generated-issue-name">Wrong size <a href="#wrong-font-size">(<code>wrong-font-size</code></a>)</span></li>
</ul>
</li>
<li><span class="generated-issue-name">Leading <a href="#leading">(<code>leading</code></a>)</span></li>
<li><span class="generated-issue-name">Kerning <a href="#kerning">(<code>kerning</code></a>)</span></li>
<li><span class="generated-issue-name">Paragraph indentation <a href="#paragraph-indentation">(<code>paragraph-indentation</code></a>)</span></li>
<li><span class="generated-issue-name">Text alignment <a href="#text-alignment">(<code>text-alignment</code></a>)</span></li>
</ul>
</li>
<li><span class="generated-issue-name">Hyphenation <a href="#hyphenation">(<code>hyphenation</code></a>)</span></li>
<li><span class="generated-issue-name">Markup <a href="#markup">(<code>markup</code></a>)</span> <ul>
<li><span class="generated-issue-name">Added markup <a href="#added-markup">(<code>added-markup</code></a>)</span></li>
<li><span class="generated-issue-name">Inconsistent markup <a href="#inconsistent-markup">(<code>inconsistent-markup</code></a>)</span></li>
<li><span class="generated-issue-name">Misplaced markup <a href="#misplaced-markup">(<code>misplaced-markup</code></a>)</span></li>
<li><span class="generated-issue-name">Missing markup <a href="#missing-markup">(<code>missing-markup</code></a>)</span></li>
<li><span class="generated-issue-name">Questionable markup <a href="#questionable-markup">(<code>questionable-markup</code></a>)</span></li>
</ul>
</li>
<li><span class="generated-issue-name">Missing text <a href="#missing-text">(<code>missing-text</code></a>)</span></li>
<li><span class="generated-issue-name">Truncation/text expansion <a href="#truncation-text-expansion">(<code>truncation-text-expansion</code></a>)</span></li>
<li><span class="generated-issue-name">Overall design (layout) <a href="#overall-design">(<code>overall-design</code></a>)</span> <ul>
<li><span class="generated-issue-name">Color <a href="#color">(<code>color</code></a>)</span></li>
<li><span class="generated-issue-name">Footnote/endnote format <a href="#footnote-format">(<code>footnote-format</code></a>)</span></li>
<li><span class="generated-issue-name">Global font choice <a href="#global-font-choice">(<code>global-font-choice</code></a>)</span></li>
<li><span class="generated-issue-name">Headers and footers <a href="#headers-footers">(<code>headers-footers</code></a>)</span></li>
<li><span class="generated-issue-name">Margins <a href="#margins">(<code>margins</code></a>)</span></li>
<li><span class="generated-issue-name">Page breaks <a href="#page-breaks">(<code>page-breaks</code></a>)</span></li><!-- IDs are immutable once created, so we cannot change this to singular -->
<li><span class="generated-issue-name">Widows/orphans <a href="#widows-orphans">(<code>widows-orphans</code></a>)</span></li>
</ul>
</li>
</ul>
</li>
</ul>
<h4>1.1.4. Fluency</h4>
<p>Fluency includes those issues about the linguistic “well-formedness” of the text that can be assessed without regard to whether the text is a translation or not. Most Fluency issues apply equally to source and target texts.</p>
<a href="http://qt21.eu/mqm-definition/images/2015-05-27/Fluency-2015-05-27.svg" target="_blank"><img src="http://qt21.eu/mqm-definition/images/2015-05-27/Fluency-2015-05-27.png" alt="Fluency dimension" /></a>
<ul>
<li><strong><span class="generated-issue-name">Fluency <a href="#fluency">(<code>fluency</code></a>)</span></strong>
<ul>
<li><span class="generated-issue-name">Ambiguity <a href="#ambiguity">(<code>ambiguity</code></a>)</span> <ul>
<li><span class="generated-issue-name">Unclear reference <a href="#unclear-reference">(<code>unclear-reference</code></a>)</span></li>
</ul>
</li>
<li><span class="generated-issue-name">Character encoding <a href="#character-encoding">(<code>character-encoding</code></a>)</span></li>
<li><span class="generated-issue-name">Coherence <a href="#coherence">(<code>coherence</code></a>)</span></li>
<li><span class="generated-issue-name">Cohesion <a href="#cohesion">(<code>cohesion</code></a>)</span></li>
<li><span class="generated-issue-name">Corpus conformance <a href="#corpus-conformance">(<code>corpus-conformance</code></a>)</span></li>
<li><span class="generated-issue-name">Duplication <a href="#duplication">(<code>duplication</code></a>)</span></li>
<li><strong><span class="generated-issue-name">Grammar <a href="#grammar">(<code>grammar</code></a>)</span></strong>
<ul>
<li><span class="generated-issue-name">Function words <a href="#function-words">(<code>function-words</code></a>)</span></li>
<li><span class="generated-issue-name">Word form <a href="#word-form">(<code>word-form</code></a>)</span> <ul>
<li><span class="generated-issue-name">Agreement <a href="#agreement">(<code>agreement</code></a>)</span></li>
<li><span class="generated-issue-name">Part of speech <a href="#part-of-speech">(<code>part-of-speech</code></a>)</span></li>
<li><span class="generated-issue-name">Tense/mood/aspect <a href="#tense-mood-aspect">(<code>tense-mood-aspect</code></a>)</span></li>
</ul>
</li>
<li><span class="generated-issue-name">Word order <a href="#word-order">(<code>word-order</code></a>)</span></li>
</ul>
</li>
<li><strong><span class="generated-issue-name">Grammatical register <a href="#grammatical-register">(<code>grammatical-register</code></a>)</span></strong></li>
<li><strong><span class="generated-issue-name">Inconsistency <a href="#inconsistency">(<code>inconsistency</code></a>)</span></strong>
<ul>
<li><span class="generated-issue-name">Inconsistent abbreviations <a href="#inconsistent-abbreviations">(<code>inconsistent-abbreviations</code></a>)</span></li>
<li><span class="generated-issue-name">Images vs. text <a href="#images-vs-text">(<code>images-vs-text</code></a>)</span></li>
<li><span class="generated-issue-name">Inconsistent link/cross-reference <a href="#inconsistent-link">(<code>inconsistent-link</code></a>)</span></li>
<li><span class="generated-issue-name">Inconsistent with external reference <a href="#external-inconsistency">(<code>external-inconsistency</code></a>)</span></li>
</ul>
</li>
<li><span class="generated-issue-name">Index/TOC <a href="#index-toc">(<code>index-toc</code></a>)</span> <ul>
<li><span class="generated-issue-name">Index/TOC format <a href="#index-toc-format">(<code>index-toc-format</code></a>)</span></li>
<li><span class="generated-issue-name">Missing/incorrect TOC item <a href="#missing-incorrect-toc-item">(<code>missing-incorrect-toc-item</code></a>)</span></li>
<li><span class="generated-issue-name">Page references <a href="#page-references">(<code>page-references</code></a>)</span></li>
</ul>
</li>
<li><span class="generated-issue-name">Link/cross-reference <a href="#broken-link">(<code>broken-link</code></a>)</span> <ul>
<li><span class="generated-issue-name">Document-external link <a href="#document-external-link">(<code>document-external-link</code></a>)</span></li>
<li><span class="generated-issue-name">Document-internal link <a href="#document-internal-link">(<code>document-internal-link</code></a>)</span></li>
</ul>
</li>
<li><span class="generated-issue-name">Nonallowed characters <a href="#nonallowed-characters">(<code>nonallowed-characters</code></a>)</span></li>
<li><span class="generated-issue-name">Offensive <a href="#offensive">(<code>offensive</code></a>)</span></li>
<li><span class="generated-issue-name">Pattern problem <a href="#pattern-problem">(<code>pattern-problem</code></a>)</span></li>
<li><span class="generated-issue-name">Sorting <a href="#sorting">(<code>sorting</code></a>)</span></li>
<li><strong><span class="generated-issue-name">Spelling <a href="#spelling">(<code>spelling</code></a>)</span></strong>
<ul>
<li><span class="generated-issue-name">Capitalization <a href="#capitalization">(<code>capitalization</code></a>)</span></li>
<li><span class="generated-issue-name">Diacritics <a href="#diacritics">(<code>diacritics</code></a>)</span></li>
</ul>
</li>
<li><strong><span class="generated-issue-name">Typography <a href="#typography">(<code>typography</code></a>)</span></strong>
<ul>
<li><span class="generated-issue-name">Punctuation <a href="#punctuation">(<code>punctuation</code></a>)</span></li>
<li><span class="generated-issue-name">Unpaired quote marks or brackets <a href="#unpaired-marks">(<code>unpaired-marks</code></a>)</span></li>
<li><span class="generated-issue-name">Whitespace <a href="#whitespace">(<code>whitespace</code></a>)</span></li>
</ul>
</li>
<li><strong><span class="generated-issue-name">Unintelligible <a href="#unintelligible">(<code>unintelligible</code></a>)</span></strong></li>
</ul>
</li>
</ul>
<h4>1.1.5. Internationalization</h4>
<p>Internationalization covers areas related to the preparation of the source content for subsequent translation or localization. Internationalization issues may be detected through problems found in the target (particularly from those included in <span class="generated-issue-name">Locale convention <a href="#locale-convention">(<code>locale-convention</code></a>)</span>), but an Internationalization audit is generally conducted separately from a general assessment of translation quality.</p>
<a href="http://qt21.eu/mqm-definition/images/2015-05-27/Internationalization-2015-05-27.svg" target="_blank"><img src="http://qt21.eu/mqm-definition/images/2015-05-27/Internationalization-2015-05-27.png" alt="Internationalization dimension" /></a>
<ul>
<li><span class="generated-issue-name">Internationalization <a href="#internationalization">(<code>internationalization</code></a>)</span> <ul>
<li><span class="generated-issue-name">Concatenation <a href="#concatenation">(<code>concatenation</code></a>)</span></li>
<li><span class="generated-issue-name">Confusable security <a href="#confusable-security">(<code>confusable-security</code></a>)</span> <li><span class="generated-issue-name">Embedded string <a href="#embedded-string">(<code>embedded-string</code></a>)</span> <ul>
<li><span class="generated-issue-name">Embedded string in code <a href="#embedded-string-in-code">(<code>embedded-string-in-code</code></a>)</span></li>
<li><span class="generated-issue-name">Embedded string in graphic <a href="#embedded-string-in-graphic">(<code>embedded-string-in-graphic</code></a>)</span></li>
</ul>
</li>
<li><span class="generated-issue-name">Functional <a href="#functional">(<code>functional</code></a>)</span> <ul>
<li><span class="generated-issue-name">Case folding <a href="#case-folding">(<code>case-folding</code></a>)</span></li>
<li><span class="generated-issue-name">Character set support <a href="#character-set-support">(<code>character-set-support</code></a>)</span></li>
<li><span class="generated-issue-name">Fixed collation <a href="#fixed-collation">(<code>fixed-collation</code></a>)</span></li>
<li><span class="generated-issue-name">Hard-coded keyboard command <a href="#hard-coded-keyboard-command">(<code>hard-coded-keyboard-command</code></a>)</span></li>
<li><span class="generated-issue-name">Input validation <a href="#input-validation">(<code>input-validation</code></a>)</span></li>
<li><span class="generated-issue-name">Missing fall-back text <a href="#missing-fall-back-text">(<code>missing-fall-back-text</code></a>)</span></li>
<li><span class="generated-issue-name">String matching <a href="#string-matching">(<code>string-matching</code></a>)</span></li>
<li><span class="generated-issue-name">Text corruption <a href="#text-corruption">(<code>text-corruption</code></a>)</span></li>
<li><span class="generated-issue-name">Text indexing <a href="#text-indexing">(<code>text-indexing</code></a>)</span></li>
<li><span class="generated-issue-name">Time zone support <a href="#time-zone-support">(<code>time-zone-support</code></a>)</span></li>
<li><span class="generated-issue-name">Writing system support <a href="#writing-system-support">(<code>writing-system-support</code></a>)</span> <ul>
<li><span class="generated-issue-name">Bi-di support <a href="#bi-di-support">(<code>bi-di-support</code></a>)</span></li>
<li><span class="generated-issue-name">Font rendering engine <a href="#font-rendering-engine">(<code>font-rendering-engine</code></a>)</span></li>
<li><span class="generated-issue-name">Keyboard support <a href="#keyboard-support">(<code>keyboard-support</code></a>)</span></li>
</ul>
</li>
</ul>
</li>
<li><span class="generated-issue-name">Graphical aspects <a href="#graphical-internationalization">(<code>graphical-internationalization</code></a>)</span> <ul>
<li><span class="generated-issue-name">Color internationalization <a href="#color-internationalization">(<code>color-internationalization</code></a>)</span></li>
<li><span class="generated-issue-name">Culture-specific graphic <a href="#culture-specific-graphic">(<code>culture-specific-graphic</code></a>)</span></li>
<li><span class="generated-issue-name">Hard-coded graphic <a href="#hard-coded-graphic">(<code>hard-coded-graphic</code></a>)</span></li>
</ul>
</li>
<li><span class="generated-issue-name">Language-dependent logic <a href="#language-dependent-logic">(<code>language-dependent-logic</code></a>)</span></li>
<li><span class="generated-issue-name">Language-specific tool support <a href="#language-specific-tool-support">(<code>language-specific-tool-support</code></a>)</span> <ul>
<li><span class="generated-issue-name">Grammar checker <a href="#grammar-checker">(<code>grammar-checker</code></a>)</span></li>
<li><span class="generated-issue-name">Hyphenator <a href="#hyphenator">(<code>hyphenator</code></a>)</span></li>
<li><span class="generated-issue-name">Spell checker <a href="#spell-checker">(<code>spell-checker</code></a>)</span></li>
</ul>
</li>
<li><span class="generated-issue-name">Localization support <a href="#localization-support">(<code>localization-support</code></a>)</span> <ul>
<li><span class="generated-issue-name">Address internationalization <a href="#address-internationalization">(<code>address-internationalization</code></a>)</span></li>
<li><span class="generated-issue-name">Calendar internationalization <a href="#calendar-internationalization">(<code>calendar-internationalization</code></a>)</span></li>
<li><span class="generated-issue-name">Currency internationalization <a href="#currency-internationalization">(<code>currency-internationalization</code></a>)</span></li>
<li><span class="generated-issue-name">Date internationalization <a href="#date-internationalization">(<code>date-internationalization</code></a>)</span></li>
<li><span class="generated-issue-name">Measurement internationalization <a href="#measurement-internationalization">(<code>measurement-internationalization</code></a>)</span></li>
<li><span class="generated-issue-name">Name internationalization <a href="#name-internationalization">(<code>name-internationalization</code></a>)</span></li>
<li><span class="generated-issue-name">Number internationalization <a href="#number-internationalization">(<code>number-internationalization</code></a>)</span></li>
<li><span class="generated-issue-name">Shortcut key internationalization <a href="#shortcut-key-internationalization">(<code>shortcut-key-internationalization</code></a>)</span></li>
<li><span class="generated-issue-name">Telephone internationalization <a href="#telephone-internationalization">(<code>telephone-internationalization</code></a>)</span></li>
<li><span class="generated-issue-name">Time internationalization <a href="#time-internationalization">(<code>time-internationalization</code></a>)</span></li>
</ul>
</li>
<li><span class="generated-issue-name">Paper/envelope size <a href="#paper-envelope-size">(<code>paper-envelope-size</code></a>)</span></li>
<li><span class="generated-issue-name">Resource externalization <a href="#resource-externalization">(<code>resource-externalization</code></a>)</span></li>
<li><span class="generated-issue-name">Sequence <a href="#sequence">(<code>sequence</code></a>)</span></li>
<li><span class="generated-issue-name">Text expandability <a href="#text-expandability">(<code>text-expandability</code></a>)</span></li>
<li><span class="generated-issue-name">User interface internationalization <a href="#ui-internationalization">(<code>ui-internationalization</code></a>)</span> <ul>
<li><span class="generated-issue-name">Complexity <a href="#complexity">(<code>complexity</code></a>)</span></li>
<li><span class="generated-issue-name">Fixed dialog/UI size <a href="#fixed-dialog-ui-size">(<code>fixed-dialog-ui-size</code></a>)</span></li>
<li><span class="generated-issue-name">Non-dynamic UI <a href="#non-dynamic-ui">(<code>non-dynamic-ui</code></a>)</span></li>
<li><span class="generated-issue-name">Non-reversible UI <a href="#non-reversible-ui">(<code>non-reversible-ui</code></a>)</span></li>
</ul>
</li>
</ul>
</li>
</ul>
<h4>1.1.6. Locale convention</h4>
<p>Issues in Locale convention relate to the formal compliance of content with locale-specific conventions, such as use of proper number formats. If content is otherwise correctly translated and fluent but violates specific locale expectations (as defined in the translation specifications), it is addressed in this dimension. This dimension does <em>not</em> cover issues related to whether the content itself is appropriate for the locale (these issues are covered under <span class="generated-issue-name">Verity <a href="#verity">(<code>verity</code></a>)</span>.</p>
<a href="http://qt21.eu/mqm-definition/images/2015-05-27/Locale-convention-2015-05-27.svg" target="_blank"><img src="http://qt21.eu/mqm-definition/images/2015-05-27/Locale-convention-2015-05-27.png" alt="Locale convention dimension" /></a>
<ul>
<li><strong><span class="generated-issue-name">Locale convention <a href="#locale-convention">(<code>locale-convention</code></a>)</span></strong>
<ul>
<li><span class="generated-issue-name">Address format <a href="#address-format">(<code>address-format</code></a>)</span> <ul>
<li><span class="generated-issue-name">Postal code <a href="#postal-code">(<code>postal-code</code></a>)</span> </ul>
</li>
<li><span class="generated-issue-name">Calendar type <a href="#calendar-type">(<code>calendar-type</code></a>)</span></li>
<li><span class="generated-issue-name">Currency format <a href="#currency-format">(<code>currency-format</code></a>)</span></li>
<li><span class="generated-issue-name">Date format <a href="#date-format">(<code>date-format</code></a>)</span></li>
<li><span class="generated-issue-name">Locale-specific punctuation <a href="#locale-specific-punctuation">(<code>locale-specific-punctuation</code></a>)</span> <ul>
<li><span class="generated-issue-name">Quote mark type <a href="#quote-mark-type">(<code>quote-mark-type</code></a>)</span></li>
</ul>
</li>
<li><span class="generated-issue-name">Measurement format <a href="#measurement-format">(<code>measurement-format</code></a>)</span></li>
<li><span class="generated-issue-name">Name format <a href="#name-format">(<code>name-format</code></a>)</span></li>
<li><span class="generated-issue-name">National language standard <a href="#national-language-standard">(<code>national-language-standard</code></a>)</span></li>
<li><span class="generated-issue-name">Number format <a href="#number-format">(<code>number-format</code></a>)</span></li>
<li><span class="generated-issue-name">Shortcut key <a href="#shortcut-key">(<code>shortcut-key</code></a>)</span></li>
<li><span class="generated-issue-name">Telephone format <a href="#telephone-format">(<code>telephone-format</code></a>)</span></li>
<li><span class="generated-issue-name">Time format <a href="#time-format">(<code>time-format</code></a>)</span></li>
</ul>
</li>
</ul>
<h4>1.1.7. Style</h4>
<p>Style issues relate to what is commonly known as “Style”, defined both formally (in style guides) and informally (e.g., a “light style” or an “engaging style”). These issues are closely related to fluency, but are often treated separately by tools and quality processes and so are grouped as a separate dimension in MQM.</p>
<a href="http://qt21.eu/mqm-definition/images/2015-05-27/Style-2015-05-27.svg" target="_blank"><img src="http://qt21.eu/mqm-definition/images/2015-05-27/Style-2015-05-27.png" alt="Style dimension" /></a>
<ul>
<li><strong><span class="generated-issue-name">Style <a href="#style">(<code>style</code></a>)</span></strong>
<ul>
<li><span class="generated-issue-name">Register <a href="#register">(<code>register</code></a>)</span> <ul>
<li><span class="generated-issue-name">Variants/slang <a href="#variants-slang">(<code>variants-slang</code></a>)</span></li>
</ul>
</li>
<li><span class="generated-issue-name">Awkward <a href="#awkward">(<code>awkward</code></a>)</span></li>
<li><span class="generated-issue-name">Company style <a href="#company-style">(<code>company-style</code></a>)</span></li>
<li><span class="generated-issue-name">Inconsistent style <a href="#inconsistent-style">(<code>inconsistent-style</code></a>)</span></li>
<li><span class="generated-issue-name">Third-party style <a href="#third-party-style">(<code>third-party-style</code></a>)</span></li>
<li><span class="generated-issue-name">Unidiomatic <a href="#unidiomatic">(<code>unidiomatic</code></a>)</span></li>
</ul>
</li>
</ul>
<h4>1.1.8. Terminology</h4>
<p>Terminology issues relate to the use of domain- or organization-specific terminology (i.e., the use of words to relate to specific concepts not considered part of general language). Adherence to specified terminology is widely considered an issue of central concern in both translation and content authoring. Issues in this branch should <em>not</em> be used for general language mistranslation (e.g., translations that would not be considered correct under reasonable circumstances), and should be reserved for issues related to terminology (e.g., a translation is reasonable but incorrect in the context of specific technical domain or for a particular organization).</p>
<a href="http://qt21.eu/mqm-definition/images/2015-05-27/Terminology-2015-05-27.svg" target="_blank"><img src="http://qt21.eu/mqm-definition/images/2015-05-27/Terminology-2015-05-27.png" alt="Terminology dimension" /></a>
<ul>
<li><strong><span class="generated-issue-name">Terminology <a href="#terminology">(<code>terminology</code></a>)</span></strong>
<ul>
<li><span class="generated-issue-name">Inconsistent with termbase <a href="#termbase">(<code>termbase</code></a>)</span> <ul>
<li><span class="generated-issue-name">Company terminology <a href="#terminology-company">(<code>terminology-company</code></a>)</span></li>
<li><span class="generated-issue-name">Third-party termbase <a href="#terminology-third-party">(<code>terminology-third-party</code></a>)</span></li>
</ul>
</li>
<li><span class="generated-issue-name">Inconsistent with domain <a href="#domain-terminology">(<code>domain-terminology</code></a>)</span></li>
<li><span class="generated-issue-name">Inconsistent use of terminology <a href="#term-inconsistency">(<code>term-inconsistency</code></a>)</span> <ul>
<li><span class="generated-issue-name">Multiple terms for concept in source <a href="#multiple-terms-for-concept">(<code>multiple-terms-for-concept</code></a>)</span></li>
<li><span class="generated-issue-name">Multiple translations of same term <a href="#multiple-translations-of-term">(<code>multiple-translations-of-term</code></a>)</span></li>
</ul>
</li>
</ul>
</li>
</ul>
<h4>1.1.9. Verity</h4>
<p>Verity issues relate to the suitability of content for the target locale and audience. They do not relate to fluency or accuracy since content may be fluently written and accurately translated and still be inappropriate for the target locale or audience. For example, if a text translated for Germans in Germany refers to options available only in the UK, these portions will likely be problematic. For more details on Verity, see the discussion below.</p>
<a href="http://qt21.eu/mqm-definition/images/2015-05-27/Verity-2015-05-27.svg" target="_blank"><img src="http://qt21.eu/mqm-definition/images/2015-05-27/Verity-2015-05-27.png" alt="Verity dimension" /></a>
<ul>
<li><strong><span class="generated-issue-name">Verity <a href="#verity">(<code>verity</code></a>)</span></strong>
<ul>
<li><strong><span class="generated-issue-name">Completeness <a href="#completeness">(<code>completeness</code></a>)</span></strong>
<ul>
<li><span class="generated-issue-name">Incomplete List <a href="#incomplete-list">(<code>incomplete-list</code></a>)</span></li>
<li><span class="generated-issue-name">Incomplete procedure <a href="#incomplete-procedure">(<code>incomplete-procedure</code></a>)</span></li>
</ul>
</li>
<li><span class="generated-issue-name">Culture-specific reference <a href="#culture-specific">(<code>culture-specific</code></a>)</span> <li><span class="generated-issue-name">End-user suitability <a href="#end-user-suitability">(<code>end-user-suitability</code></a>)</span> <li><strong><span class="generated-issue-name">Legal requirements <a href="#legal-requirements">(<code>legal-requirements</code></a>)</span></strong></li>
<li><strong><span class="generated-issue-name">Locale-specific content <a href="#locale-specific-content">(<code>locale-specific-content</code></a>)</span></strong></li>
</ul>
</li>
</ul>
<p>As <span class="generated-issue-name">Verity <a href="#verity">(<code>verity</code></a>)</span> is a relatively new concept in translation quality assessment, some examples may help clarify its usage and how it differs from general <span class="generated-issue-name">Accuracy <a href="#accuracy">(<code>accuracy</code></a>)</span> or <span class="generated-issue-name">Fluency <a href="#fluency">(<code>fluency</code></a>)</span>. Note that issues in this branch may be checked in separate processes relating to market compliance before translation begins or may be subject to discussion and negotiation between the requester and the provider.</p>
<p>The examples are:</p>
<ul>
<li>An computer advertisement written in the U.S. directly compares a computer’s features with those of a competitor to conclude that the advertiser’s computer is better that its competitor’s. While this sort of advertisement is perfectly acceptable in U.S., it is illegal under German law. As a result an accurate and fluent translation of the advertisement would subject the maker to potential legal penalties. The appropriate German version would therefore highlight strengths of the computer in absolute terms without reference to a competitor. Note: The necessary changes in such a case are often included under the rubric of transcreation. This issue is classified under <span class="generated-issue-name">Legal requirements <a href="#legal-requirements">(<code>legal-requirements</code></a>)</span></li>
<li>A user guide for a wireless Internet base station is translated, but includes unnecessary legal notifications from the source text and omits needed notifications for the target locale. This issue is classified under <span class="generated-issue-name">Legal requirements <a href="#legal-requirements">(<code>legal-requirements</code></a>)</span></li>
<li>A Hungarian-language novel being translated into Quebec French includes references to Hungarian popular culture and music. When translated in a way that would be appropriate for a French speaker living in Hungary who is familiar with Hungarian culture, these references are unintelligible to the target audience in Quebec. As a result the text includes Verity errors and the appropriate translation for the specifications involves substituting in appropriate Quebecoise pop culture and musical references. These issues can be categorized under <span class="generated-issue-name">Culture-specific reference <a href="#culture-specific">(<code>culture-specific</code></a>)</span></li>
<li>A text is written in a conceptually complex fashion that makes it inaccessible for its intended audience of high-school students (even though the overall register is appropriate). The suitability does not depend on the locale or whether or not the text is translated. It can be categorized as <span class="generated-issue-name">End-user suitability <a href="#end-user-suitability">(<code>end-user-suitability</code></a>)</span>.</li>
<li>An automobile service manual for a British automobile assumes a right-hand drive automobile and includes descriptions of parts for that drive system. When the manual is used in the United States, these references are no longer appropriate to the automobile and must be modified to reflect the use of left-hand drive systems in the U.S., including swapping left and right in physical descriptions of some parts. These issues can be categorized as <span class="generated-issue-name">Locale-specific content <a href="#locale-specific-content">(<code>locale-specific-content</code></a>)</span>.</li>
<li>A document translated from German to U.S. Spanish includes references to European type electrical plugs (which would be appropriate for the product when sold in Spain). These references must be changed to match the physical characteristics of the product as sold in the U.S. This would be classified under <span class="generated-issue-name">Locale-specific content <a href="#locale-specific-content">(<code>locale-specific-content</code></a>)</span>.</li>
<li>A service manual omits needed steps from the description of a technical process, making it impossible to complete the process as written. (Note: this is an example of a monolingual Verity problem that exists independently of the whether the text is translated or not.) This issue is categorized as <span class="generated-issue-name">Incomplete procedure <a href="#incomplete-procedure">(<code>incomplete-procedure</code></a>)</span>.</li>
<li>A text written for an audience of college-educated agriculture managers is translated for use in another country where the local managers are trained on the job and cannot be assumed to have the same education. As a result, the text contains references to knowledge and background that cannot be assumed in the target audience. This problem is an example of the type <span class="generated-issue-name">End-user suitability <a href="#end-user-suitability">(<code>end-user-suitability</code></a>)</span>. Here the text must be changed and clarified for the intended audience.</li>
<li>In a fictional work, an individual sees people dressed in black and thinks of a funeral, but when translated <em>in a covert translation</em> (i.e., a translation that should appear as though it were written in the target locale and language) this association does not work because black is traditionally worn in weddings rather than funerals in the target locale. This would be classified as <span class="generated-issue-name">Culture-specific reference <a href="#culture-specific">(<code>culture-specific</code></a>)</span>.</li>
<li>A verification form for password security requests users to provide the name of the street they grew up on. However, in some countries there are no street names, and addresses refer to “colonies” and blocks within a colony instead. As a result, the question does not make sense to the target audience. This issue would be categorized as <span class="generated-issue-name">Culture-specific reference <a href="#culture-specific">(<code>culture-specific</code></a>)</span>.</li>
</ul>
<h4>1.1.10. Other</h4>
<p>This dimension is used for issues which cannot be otherwise classified into a dimension of MQM. In cases where an unforeseen issue can be classified as belonging to a dimension, it should be classified in that dimension under the top level or using a custom issue type. In practice <em>Other</em> should be used extremely rarely.</p>
<ul>
<li><span class="generated-issue-name">Other <a href="#other">(<code>other</code></a>)</span></li>
</ul>
</div>
<div id="issues_list">
<h3>1.2. Detailed listing of MQM issue types</h3>
<p>This section lists all MQM issue types in alphabetical order, with the following information:</p>
<div class="example">
<h4 id="sample">Name</h4>
<p>The name is the English name for the issue type. This name may be localized in other languages or may be changed in a UI to reflect application-specific preferences. (For example, if an existing system is being converted to use MQM categories and already has an issue type called <em>Terminology problem</em> that corresponds to <span class="generated-issue-name">Terminology <a href="#terminology">(<code>terminology</code></a>)</span>, the UI may display the existing name but refer to the ID value <code>terminology</code> internally for mapping purposes. For new English-language implementations, however, it is recommended to use the existing name to prevent confusion.)</p>
<table>
<tr><th>ID</th><td>An XML identifier for the category. This ID is used to refer unambiguously to each issue type and does not change, even if a UI may display other names for the category.</td></tr>
<tr><th>Definition</th><td>A definition of the issue type</td></tr>
<tr><th>MQM Core?</th><td>(yes|no) Specifies whether the issue is in the MQM core (see the definition of the <a href="http://www.qt21.eu/mqm-definition/definition-2015-05-27.html#mqm-core">MQM Core</a>) or not.</td></tr>
<tr><th>Automatable?</th><td>(yes|no) <strong>Informative</strong>: Indicates whether the issue may be automatically detected. Users interested in fully automatable subsets of MQM may wish to limit themselves to issues marked with “yes”. This specification does not provide any guidance on <em>how</em> to check issues automatically and detection may require language-specific modules or development. Success in detecting issues depends on factors outside the scope of this specification and individual systems may be able to identify issues not identified as automatable in this specification.</td></tr>
<tr><th>Parent</th><td>The parent of the issue type in the hierarchy. Each issue can be understood as a type of its parent.</td></tr>
<tr><th>Children</th><td>A list of any children to the current issue type.</td></tr>
<tr><th>Applies to</th><td>Whether the category applies to target, source, or both</td></tr>
<tr><th>Example(s)</th><td>One or more illustrative examples of the issue type</td></tr>
<tr><th>Note(s)</th><td>Any notes on usage for the issue type.</td></tr>
</table>
</div>
<h4 id="accuracy">Accuracy</h4>
<table>
<tr><th>ID</th><td>accuracy</td></tr>
<tr><th>Definition</th><td>The target text does not accurately reflect the source text, allowing for any differences authorized by specifications.</td></tr>
<tr><th>MQM Core?</th><td>no</td></tr>
<tr><th>Automatable?</th><td>no</td></tr>
<tr><th>Parent</th><td><a href="#"><code></code></a></td></tr>
<tr><th>Children</th><td><a href="#addition"><code>addition</code></a>, <a href="#improper-exact-tm-match"><code>improper-exact-tm-match</code></a>, <a href="#mistranslation"><code>mistranslation</code></a>, <a href="#omission"><code>omission</code></a>, <a href="#over-translation"><code>over-translation</code></a>, <a href="#under-translation"><code>under-translation</code></a>, <a href="#untranslated"><code>untranslated</code></a></td></tr>
<tr><th>Applies to</th><td>target</td></tr>
<tr><th>Example(s)</th><td></td></tr>
<tr><th>Note(s)</th><td><ul><li>Most cases of <a href="#accuracy"><code>accuracy</code></a> are addressed by one of the more specific subtypes listed below.</li><li>In Machine Translation literature, this category is typically referred to as “Adequacy”.</li></ul></td></tr>
</table>
<h4 id="added-markup">Added markup</h4>
<table>
<tr><th>ID</th><td>added-markup</td></tr>
<tr><th>Definition</th><td>The target text has markup added with no corresponding markup in the source.</td></tr>
<tr><th>MQM Core?</th><td>no</td></tr>
<tr><th>Automatable?</th><td>yes</td></tr>
<tr><th>Parent</th><td><a href="#markup"><code>markup</code></a></td></tr>
<tr><th>Children</th><td><em>none</em></td></tr>
<tr><th>Applies to</th><td>target</td></tr>
<tr><th>Example(s)</th><td><ul><li>A source segment has no formatting tags, but the target has a set of italic tags.</li></ul></td></tr>
<tr><th>Note(s)</th><td></td></tr>
</table>
<h4 id="addition">Addition</h4>
<table>
<tr><th>ID</th><td>addition</td></tr>
<tr><th>Definition</th><td>The target text includes text not present in the source.</td></tr>
<tr><th>MQM Core?</th><td>yes</td></tr>
<tr><th>Automatable?</th><td>yes</td></tr>
<tr><th>Parent</th><td><a href="#accuracy"><code>accuracy</code></a></td></tr>
<tr><th>Children</th><td><em>none</em></td></tr>
<tr><th>Applies to</th><td>target</td></tr>
<tr><th>Example(s)</th><td><ul><li>A translation includes portions of another translation that were inadvertently pasted into the document.</li></ul></td></tr>
<tr><th>Note(s)</th><td></td></tr>
</table>
<h4 id="address-format">Address format</h4>
<table>
<tr><th>ID</th><td>address-format</td></tr>
<tr><th>Definition</th><td>Content uses the wrong format for addresses.</td></tr>
<tr><th>MQM Core?</th><td>no</td></tr>
<tr><th>Automatable?</th><td>no</td></tr>
<tr><th>Parent</th><td><a href="#locale-convention"><code>locale-convention</code></a></td></tr>
<tr><th>Children</th><td><a href="#postal-code"><code>postal-code</code></a></td></tr>
<tr><th>Applies to</th><td>source and target</td></tr>
<tr><th>Example(s)</th><td><ul><li>An online form translated from English to Hindi requires a street number even though many addresses in India do not include a house number.</li></ul></td></tr>
<tr><th>Note(s)</th><td><ul><li>Very often this issue indicates an underlying <a href="#internationalization"><code>internationalization</code></a> problem.</li></ul></td></tr>
</table>
<h4 id="address-internationalization">Address internationalization</h4>
<table>
<tr><th>ID</th><td>address-internationalization</td></tr>
<tr><th>Definition</th><td>An inport form, database, or other software component does not properly support international address formats</td></tr>
<tr><th>MQM Core?</th><td>no</td></tr>
<tr><th>Automatable?</th><td>no</td></tr>
<tr><th>Parent</th><td><a href="#localization-support"><code>localization-support</code></a></td></tr>
<tr><th>Children</th><td><em>none</em></td></tr>
<tr><th>Applies to</th><td>source</td></tr>
<tr><th>Example(s)</th><td><ul><li>A form enforces a US model of street addresses that does not apply in many target languages and does not support notation of districts or other important features of addresses in some countries.</li></ul></td></tr>
<tr><th>Note(s)</th><td><ul><li>Corresponds to <a href="#address-format"><code>address-format</code></a> in <a href="#locale-convention"><code>locale-convention</code></a>.</li><li>This is used to mark engineering problems in the source content, not specific problems in the target.</li></ul></td></tr>
</table>
<h4 id="agreement">Agreement</h4>
<table>
<tr><th>ID</th><td>agreement</td></tr>
<tr><th>Definition</th><td>Two or more words do not agree with respect to case, number, person, or other grammatical features</td></tr>
<tr><th>MQM Core?</th><td>no</td></tr>
<tr><th>Automatable?</th><td>yes</td></tr>
<tr><th>Parent</th><td><a href="#word-form"><code>word-form</code></a></td></tr>
<tr><th>Children</th><td><em>none</em></td></tr>
<tr><th>Applies to</th><td>source and target</td></tr>
<tr><th>Example(s)</th><td><ul><li>A text reads “They was expecting a report.”</li></ul></td></tr>
<tr><th>Note(s)</th><td></td></tr>
</table>
<h4 id="ambiguity">Ambiguity</h4>
<table>
<tr><th>ID</th><td>ambiguity</td></tr>
<tr><th>Definition</th><td>The text is ambiguous in its meaning.</td></tr>
<tr><th>MQM Core?</th><td>no</td></tr>
<tr><th>Automatable?</th><td>no</td></tr>
<tr><th>Parent</th><td><a href="#fluency"><code>fluency</code></a></td></tr>
<tr><th>Children</th><td><a href="#unclear-reference"><code>unclear-reference</code></a></td></tr>
<tr><th>Applies to</th><td>source and target</td></tr>
<tr><th>Example(s)</th><td><ul><li>A text reads “I cannot recommend this too highly.” (The meaning can be that the speaker cannot make a good recommendation or that it is highly recommended.)</li></ul></td></tr>
<tr><th>Note(s)</th><td><ul><li>This issue is distinguished from <a href="#ambiguous-translation"><code>ambiguous-translation</code></a> by its focus on monolingual ambiguity. In cases where the translation process has introduced ambiguity, <a href="#ambiguous-translation"><code>ambiguous-translation</code></a> should be used instead, if it is included in a metric. However, any ambiguity in a source text would be classified under this issue.</li></ul></td></tr>
</table>
<h4 id="ambiguous-translation">Ambiguous translation</h4>
<table>
<tr><th>ID</th><td>ambiguous-translation</td></tr>
<tr><th>Definition</th><td>An unambiguous source text is translated ambiguously</td></tr>
<tr><th>MQM Core?</th><td>no</td></tr>
<tr><th>Automatable?</th><td>no</td></tr>
<tr><th>Parent</th><td><a href="#mistranslation"><code>mistranslation</code></a></td></tr>
<tr><th>Children</th><td><em>none</em></td></tr>
<tr><th>Applies to</th><td>target</td></tr>
<tr><th>Example(s)</th><td><ul><li>A text that means that someone is highly recommended is translated as “I cannot recommend this too highly.” (The meaning can be that the speaker cannot make a good recommendation or that it is highly recommended.)</li></ul></td></tr>
<tr><th>Note(s)</th><td><ul><li>This issue is distinct from <a href="#ambiguity"><code>ambiguity</code></a> in that it is limited to issues where the translation process has introduced the ambiguity.</li></ul></td></tr>
</table>
<h4 id="awkward">Awkward</h4>
<table>
<tr><th>ID</th><td>awkward</td></tr>
<tr><th>Definition</th><td>A text is written with an awkward style</td></tr>
<tr><th>MQM Core?</th><td>no</td></tr>
<tr><th>Automatable?</th><td>no</td></tr>
<tr><th>Parent</th><td><a href="#style"><code>style</code></a></td></tr>
<tr><th>Children</th><td><em>none</em></td></tr>
<tr><th>Applies to</th><td>target</td></tr>
<tr><th>Example(s)</th><td><ul><li>A text is written with many embedded clauses and an excessively wordy style. While the meaning can be understood, the text is very awkward and difficult to follow.</li></ul></td></tr>
<tr><th>Note(s)</th><td></td></tr>
</table>
<h4 id="bi-di-support">Bi-di support</h4>
<table>
<tr><th>ID</th><td>bi-di-support</td></tr>
<tr><th>Definition</th><td>The software cannot support bi-directional scripts, such as Arabic and Hebrew</td></tr>
<tr><th>MQM Core?</th><td>no</td></tr>
<tr><th>Automatable?</th><td>no</td></tr>
<tr><th>Parent</th><td><a href="#writing-system-support"><code>writing-system-support</code></a></td></tr>
<tr><th>Children</th><td><em>none</em></td></tr>
<tr><th>Applies to</th><td>source</td></tr>
<tr><th>Example(s)</th><td><ul><li>Text in Arabic is displayed left-to-right rather than right-to-left.</li></ul></td></tr>
<tr><th>Note(s)</th><td></td></tr>
</table>
<h4 id="bold-italic">Bold/italic</h4>
<table>
<tr><th>ID</th><td>bold-italic</td></tr>
<tr><th>Definition</th><td>Bold or italics are used incorrectly.</td></tr>
<tr><th>MQM Core?</th><td>no</td></tr>
<tr><th>Automatable?</th><td>no</td></tr>
<tr><th>Parent</th><td><a href="#font"><code>font</code></a></td></tr>
<tr><th>Children</th><td><em>none</em></td></tr>
<tr><th>Applies to</th><td>source and target</td></tr>
<tr><th>Example(s)</th><td><ul><li>A book title should have been italicized, but the italics were omitted.</li></ul></td></tr>
<tr><th>Note(s)</th><td></td></tr>
</table>
<h4 id="calendar-internationalization">Calendar internationalization</h4>
<table>
<tr><th>ID</th><td>calendar-internationalization</td></tr>
<tr><th>Definition</th><td>Software does not support one or more calendar types needed for some locales.</td></tr>
<tr><th>MQM Core?</th><td>no</td></tr>
<tr><th>Automatable?</th><td>no</td></tr>
<tr><th>Parent</th><td><a href="#localization-support"><code>localization-support</code></a></td></tr>
<tr><th>Children</th><td><em>none</em></td></tr>
<tr><th>Applies to</th><td>source</td></tr>
<tr><th>Example(s)</th><td><ul><li>A task-management system designed in the U.S. displays Sunday as the first day of the week, while many countries list it as the last day of the week.</li><li>A website displays all dates according to the Gregorian calendar, but the target audience in much of the Middle East prefers to use the Islamic calendar.</li></ul></td></tr>
<tr><th>Note(s)</th><td><ul><li>This issue does not apply to cases where dates are displayed in the wrong format, but according to the right calendar system.</li><li>Corresponds to <a href="#calendar-format"><code>calendar-format</code></a> in <a href="#locale-convention"><code>locale-convention</code></a>.</li></li>This is used to mark engineering problems in the source content, not specific problems in the target.</li></ul></td></tr>
</table>
<h4 id="calendar-type">Calendar type</h4>
<table>
<tr><th>ID</th><td>calendar-type</td></tr>
<tr><th>Definition</th><td>Content uses the wrong type of calendar.</td></tr>
<tr><th>MQM Core?</th><td>no</td></tr>
<tr><th>Automatable?</th><td>yes</td></tr>
<tr><th>Parent</th><td><a href="#locale-convention"><code>locale-convention</code></a></td></tr>
<tr><th>Children</th><td><em>none</em></td></tr>
<tr><th>Applies to</th><td>source and target</td></tr>
<tr><th>Example(s)</th><td><ul><li>A tourism text translated from Arabic English gives a year as 1435, but it should have been converted from the Islamic calendar to the Gregorian calendar year 2014.</li></ul></td></tr>
<tr><th>Note(s)</th><td><ul><li>Very often this issue indicates an underlying <a href="#internationalization"><code>internationalization</code></a> problem.</li></ul></td></tr>
</table>
<h4 id="call-outs-captions">Call-outs and captions</h4>
<table>
<tr><th>ID</th><td>call-outs-captions</td></tr>
<tr><th>Definition</th><td>There are issues with call-outs (text within a graphic that identifies parts) or captions.</td></tr>
<tr><th>MQM Core?</th><td>no</td></tr>
<tr><th>Automatable?</th><td>no</td></tr>
<tr><th>Parent</th><td><a href="#graphics-tables"><code>graphics-tables</code></a></td></tr>
<tr><th>Children</th><td><em>none</em></td></tr>
<tr><th>Applies to</th><td>source and target</td></tr>
<tr><th>Example(s)</th><td><ul><li>During localization the location of numbers used for call-outs has been shifted and the call-outs are no longer usable.</li></ul></td></tr>
<tr><th>Note(s)</th><td></td></tr>
</table>
<h4 id="capitalization">Capitalization</h4>
<table>
<tr><th>ID</th><td>capitalization</td></tr>
<tr><th>Definition</th><td>Issues related to capitalization</td></tr>
<tr><th>MQM Core?</th><td>no</td></tr>
<tr><th>Automatable?</th><td>yes</td></tr>
<tr><th>Parent</th><td><a href="#spelling"><code>spelling</code></a></td></tr>
<tr><th>Children</th><td><em>none</em></td></tr>
<tr><th>Applies to</th><td>source and target</td></tr>
<tr><th>Example(s)</th><td><ul><li>The name <em>John Smith</em> is written as “john smith”</li></ul></td></tr>
<tr><th>Note(s)</th><td></td></tr>
</table>
<h4 id="case-folding">Case folding</h4>
<table>
<tr><th>ID</th><td>case-folding</td></tr>
<tr><th>Definition</th><td>Text casing routines do not support needed languages</td></tr>
<tr><th>MQM Core?</th><td>no</td></tr>
<tr><th>Automatable?</th><td>no</td></tr>
<tr><th>Parent</th><td><a href="#functional"><code>functional</code></a></td></tr>
<tr><th>Children</th><td><em>none</em></td></tr>
<tr><th>Applies to</th><td>source</td></tr>
<tr><th>Example(s)</th><td><ul><li>In Turkish the upper-case form of i is İ and the lower-case form of I is ı. As a result case-changing algorithms that are not internationalized and aware of Turkish will change the case of these characters incorrectly.</li></ul></td></tr>
<tr><th>Note(s)</th><td><ul><li>This issue may also impact <a href="#text-indexing"><code>text-indexing</code></a> and <a href="#string-matching"><code>string-matching</code></a> if case-insensitive indexing or matching is used.</li></ul></td></tr>
</table>
<h4 id="character-encoding">Character encoding</h4>
<table>
<tr><th>ID</th><td>character-encoding</td></tr>
<tr><th>Definition</th><td>Characters are garbled due to incorrect application of an encoding.</td></tr>
<tr><th>MQM Core?</th><td>no</td></tr>
<tr><th>Automatable?</th><td>yes</td></tr>
<tr><th>Parent</th><td><a href="#fluency"><code>fluency</code></a></td></tr>
<tr><th>Children</th><td><em>none</em></td></tr>
<tr><th>Applies to</th><td>source and target</td></tr>
<tr><th>Example(s)</th><td><ul><li>A text document in UTF-8 encoding is opened as ISO Latin-1, resulting in all “upper ASCII” characters being garbled.</li></ul></td></tr>
<tr><th>Note(s)</th><td></td></tr>
</table>
<h4 id="character-set-support">Character set support</h4>
<table>
<tr><th>ID</th><td>character-set-support</td></tr>
<tr><th>Definition</th><td>Software does not support character sets needed for specific locales</td></tr>
<tr><th>MQM Core?</th><td>no</td></tr>
<tr><th>Automatable?</th><td>no</td></tr>
<tr><th>Parent</th><td><a href="#functional"><code>functional</code></a></td></tr>
<tr><th>Children</th><td><em>none</em></td></tr>
<tr><th>Applies to</th><td>source</td></tr>
<tr><th>Example(s)</th><td><ul><li>A database application cannot process or produce text stored in ISO Latin 6 (Nordic) encoding and so cannot interface with needed legacy systems in Norway.</li></ul></td></tr>
<tr><th>Note(s)</th><td></td></tr>
</table>
<h4 id="coherence">Coherence</h4>
<table>
<tr><th>ID</th><td>coherence</td></tr>
<tr><th>Definition</th><td>The text is not coherent</td></tr>
<tr><th>MQM Core?</th><td>no</td></tr>
<tr><th>Automatable?</th><td>no</td></tr>
<tr><th>Parent</th><td><a href="#fluency"><code>fluency</code></a></td></tr>
<tr><th>Children</th><td><em>none</em></td></tr>
<tr><th>Applies to</th><td>source and target</td></tr>
<tr><th>Example(s)</th><td><ul><li>While individual sentences of the text are all perfectly fluent, the text as a whole does not make sense and is inconsistent with itself.</li></ul></td></tr>
<tr><th>Note(s)</th><td><ul><li>Since coherence applies above the segment level, this issue type would generally be assessed with a holistic metric rather than an analytic one, although any claims that a text is not coherent should be able to point to specific portions and problems. Often these specific problems can be classified as <a href="#coherence"><code>coherence</code></a> or <a href="#inconsistency"><code>inconsistency</code></a> issues in an analytic metric.</li></ul></td></tr>
</table>
<h4 id="cohesion">Cohesion</h4>
<table>
<tr><th>ID</th><td>cohesion</td></tr>
<tr><th>Definition</th><td>Portions of the text needed to connect it into an understandable whole (e.g., reference, substitution, ellipsis, conjunction, and lexical cohesion) are missing or incorrect.</td></tr>
<tr><th>MQM Core?</th><td>no</td></tr>
<tr><th>Automatable?</th><td>no</td></tr>
<tr><th>Parent</th><td><a href="#fluency"><code>fluency</code></a></td></tr>
<tr><th>Children</th><td><em>none</em></td></tr>
<tr><th>Applies to</th><td>source and target</td></tr>
<tr><th>Example(s)</th><td><ul><li>An English text is missing conjunctions and particles (e.g., “thus”, “therefore”, “but”, and “however”) needed for the logic of the text to be clear.</li></ul></td></tr>
<tr><th>Note(s)</th><td><ul><li>Cohesion applies at the local level to incorrect or missing elements needed for the intended meaning of the text to be clear. Cohesion problems at the local level may contribute to <a href="#coherence"><code>coherence</code></a> problems for the text as a whole.</li></ul></td></tr>
</table>
<h4 id="color-internationalization">Color internationalization</h4>
<table>
<tr><th>ID</th><td>color-internationalization</td></tr>
<tr><th>Definition</th><td>Use of colors is fixed and not adaptable to other locales</td></tr>
<tr><th>MQM Core?</th><td>no</td></tr>
<tr><th>Automatable?</th><td>no</td></tr>
<tr><th>Parent</th><td><a href="#graphical-internationalization"><code>graphical-internationalization</code></a></td></tr>
<tr><th>Children</th><td><em>none</em></td></tr>
<tr><th>Applies to</th><td>source</td></tr>
<tr><th>Example(s)</th><td><ul><li>A UK-based website uses a red, white, and blue color scheme and hard-codes these colors into graphical assets and inline styles. When translated for China, these colors are inappropriate but cannot be changed because of the way they are encoded into the site.</li></ul></td></tr>
<tr><th>Note(s)</th><td><ul><li>This issue type does not apply merely to the use of culture-specific colors, but rather to cases where the colors are not made accessible to the localization process and so cannot be changed.</li></ul></td></tr>
</table>
<h4 id="color">Color</h4>
<table>
<tr><th>ID</th><td>color</td></tr>
<tr><th>Definition</th><td>Colors are used incorrectly</td></tr>
<tr><th>MQM Core?</th><td>no</td></tr>
<tr><th>Automatable?</th><td>no</td></tr>
<tr><th>Parent</th><td><a href="#overall-design"><code>overall-design</code></a></td></tr>
<tr><th>Children</th><td><em>none</em></td></tr>
<tr><th>Applies to</th><td>source and target</td></tr>
<tr><th>Example(s)</th><td><ul><li>Headings should be blue but are green instead.</li></ul></td></tr>
<tr><th>Note(s)</th><td></td></tr>
</table>
<h4 id="company-style">Company style</h4>
<table>
<tr><th>ID</th><td>company-style</td></tr>
<tr><th>Definition</th><td>The text violates company/organization-specific style guidelines.</td></tr>
<tr><th>MQM Core?</th><td>no</td></tr>
<tr><th>Automatable?</th><td>yes</td></tr>
<tr><th>Parent</th><td><a href="#style"><code>style</code></a></td></tr>
<tr><th>Children</th><td><em>none</em></td></tr>
<tr><th>Applies to</th><td>source and target</td></tr>
<tr><th>Example(s)</th><td><ul><li>Company style states that passive sentences may not be used but the text uses passive sentences.</li></ul></td></tr>
<tr><th>Note(s)</th><td></td></tr>
</table>
<h4 id="terminology-company">Company terminology</h4>
<table>
<tr><th>ID</th><td>terminology-company</td></tr>
<tr><th>Definition</th><td>The text violates company/organization-specific terminology guidelines as specified in a termbase.</td></tr>
<tr><th>MQM Core?</th><td>no</td></tr>
<tr><th>Automatable?</th><td>yes</td></tr>
<tr><th>Parent</th><td><a href="#termbase"><code>termbase</code></a></td></tr>
<tr><th>Children</th><td><em>none</em></td></tr>
<tr><th>Applies to</th><td>source and target</td></tr>
<tr><th>Example(s)</th><td><ul><li>Company-specific terminology guidelines specify that a product be called the “Acme Turbo2000™”, but the text calls it the “Acme Turbo” or the “Turbo200”.</li></ul></td></tr>
<tr><th>Note(s)</th><td><ul><li>Should be used when it is necessary to distinguish company-specific terminology issues from more general <a href="#termbase"><code>termbase</code></a> issues.</li></ul></td></tr>
</table>
<h4 id="compatibility">Compatibility (Deprecated)</h4>
<table>
<tr><th>ID</th><td>compatibility</td></tr>
<tr><th>Definition</th><td>The Compatibility extension contains items which may be used for compatibility with legacy metrics even though they would otherwise not be included in MQM. Most of these issue types are taken from the LISA QA Model documentation.</td></tr>
<tr><th>MQM Core?</th><td>no</td></tr>
<tr><th>Automatable?</th><td>no</td></tr>
<tr><th>Parent</th><td><a href="#"><code></code></a></td></tr>
<tr><th>Children</th><td><p>The following issue types (presented without definition) are included in the Compatibility branch:</p><ol><li>Application compatibility</li><li>Bill of materials/runlist</li><li>Book-building sequence</li><li>Covers</li><li>Deadline</li><li>Delivery</li><li>Does not adhere to specifications</li><li>Embedded text</li><li>File format</li><li>Functional</li><li>Output device</li><li>Printing</li><li>Release guide</li><li>Spines</li><li>Style, publishing standards</li><li>Terminology, contextually inappropriate</li></ol></td></tr>
<tr><th>Applies to</th><td>source and target</td></tr>
<tr><th>Example(s)</th><td><ul><li>A quality process checks the LISA QA Model issue “Book-building sequence” and it is included for compatibility with legacy processes</li></ul></td></tr>
<tr><th>Note(s)</th><td><ul><li>Use of these categories is not recommended and these issue types are to be considered deprecated. They are included only for compatibility with legacy processes.</li><li>Since <a href="#compatibility"><code>compatibility</code></a> is not a coherent category, use of this category itself is not recommended in any circumstance, although the children categories listed above may be used for compatibility purposes.</li></ul></td></tr>
</table>
<h4 id="completeness">Completeness</h4>
<table>
<tr><th>ID</th><td>completeness</td></tr>
<tr><th>Definition</th><td>The text is incomplete</td></tr>
<tr><th>MQM Core?</th><td>yes</td></tr>
<tr><th>Automatable?</th><td>no</td></tr>
<tr><th>Parent</th><td><a href="#verity"><code>verity</code></a></td></tr>
<tr><th>Children</th><td><a href="#incomplete-list"><code>incomplete-list</code></a>, <a href="#incomplete-procedure"><code>incomplete-procedure</code></a></td></tr>
<tr><th>Applies to</th><td>source</td></tr>
<tr><th>Example(s)</th><td><ul><li>A process description leaves out key steps needed to complete the process, resulting in an incomplete description of the process.</li></ul></td></tr>
<tr><th>Note(s)</th><td><ul><li><a href="#completeness"><code>completeness</code></a> refers to instances in which needed content is missing in the source language. For cases where material present in the source language is not present in a translation, <a href="#omission"><code>omission</code></a> should be used instead.</li></ul></td></tr>
</table>
<h4 id="complexity">Complexity</h4>
<table>
<tr><th>ID</th><td>complexity</td></tr>
<tr><th>Definition</th><td>Different cultures expect different levels of complexity and presentation of information in user interfaces. If the amount of information is too much or too little for a culture, users will perceive the user interface negatively</td></tr>
<tr><th>MQM Core?</th><td>no</td></tr>
<tr><th>Automatable?</th><td>no</td></tr>
<tr><th>Parent</th><td><a href="#ui-internationalization"><code>ui-internationalization</code></a></td></tr>
<tr><th>Children</th><td><em>none</em></td></tr>
<tr><th>Applies to</th><td>source</td></tr>
<tr><th>Example(s)</th><td><ul><li>A user interface developed in Sweden has a minimalist aesthetic, but when localized into China, Chinese users expect to find information in the UI that is normally hidden under various options. As a result they may find it frustrating and difficult to use.</li></ul></td></tr>
<tr><th>Note(s)</th><td><ul><li>Solving this problem may involve extensive adaptation of localized versions and may not be solvable by simple internationalization steps.</li></ul></td></tr>
</table>
<h4 id="concatenation">Concatenation</h4>
<table>
<tr><th>ID</th><td>concatenation</td></tr>
<tr><th>Definition</th><td>Text is concatenated in ways that will not function properly when the text is translated</td></tr>
<tr><th>MQM Core?</th><td>no</td></tr>
<tr><th>Automatable?</th><td>no</td></tr>
<tr><th>Parent</th><td><a href="#internationalization"><code>internationalization</code></a></td></tr>
<tr><th>Children</th><td><em>none</em></td></tr>
<tr><th>Applies to</th><td>source</td></tr>
<tr><th>Example(s)</th><td><ul><li>A localizable string contains the following: <code>"You have found the ".$item.". Do you wish to pick it up?"</code>. When translated this string will cause problems because the article before the item and the equivalent of “it” will both need to be changed to reflect the content of the variable $item.</li></ul></td></tr>
<tr><th>Note(s)</th><td></td></tr>
</table>
<h4 id="confusable-security">Confusable security</h4>
<table>
<tr><th>ID</th><td>confusable-security</td></tr>
<tr><th>Definition</th><td>Software does not provide any security protection against easily confusable character such as Latin-script A, Greek Α, and Cyrillic А, thus allowing users to impersonate other users’ names.</td></tr>
<tr><th>MQM Core?</th><td>no</td></tr>
<tr><th>Automatable?</th><td>no</td></tr>
<tr><th>Parent</th><td><a href="#internationalization"><code>internationalization</code></a></td></tr>
<tr><th>Children</th><td><em>none</em></td></tr>
<tr><th>Applies to</th><td>source</td></tr>
<tr><th>Example(s)</th><td><ul><li>Users can select user names with any valid, non-control Unicode characters. As a result a user creates the user name Тоny (with the first two letters in Cyrillic) to impersonate an administrative user with the name Tony (all in Latin script).</li></ul></td></tr>
<tr><th>Note(s)</th><td><ul><li>This issue has emerged with the advent of pervasive Unicode support that allows multiple scripts to be combined in input. Solving this problem requires careful parsing of input.</li></ul></td></tr>
</table>
<h4 id="corpus-conformance">Corpus conformance</h4>
<table>
<tr><th>ID</th><td>corpus-conformance</td></tr>
<tr><th>Definition</th><td>The content is deemed to have a level of conformance to a reference corpus. The non-conformance type reflects the degree to which the text conforms to a reference corpus given an algorithm that combines several classes of error type to produce an aggregate rating.</td></tr>
<tr><th>MQM Core?</th><td>no</td></tr>
<tr><th>Automatable?</th><td>yes</td></tr>
<tr><th>Parent</th><td><a href="#fluency"><code>fluency</code></a></td></tr>
<tr><th>Children</th><td><em>none</em></td></tr>
<tr><th>Applies to</th><td>source and target</td></tr>
<tr><th>Example(s)</th><td><ul><li>A text reading “The harbour connected which to printer is busy or configared not properly” is flagged by a language analysis tool as suspect based on its lack of conformance to an existing corpus.</li></ul></td></tr>
<tr><th>Note(s)</th><td><ul><li>One example of this issue type might involve output from a quality estimation system that delivers a warning that a text has a very low quality estimation score.</li></ul></td></tr>
</table>
<h4 id="culture-specific-graphic">Culture-specific graphic</h4>
<table>
<tr><th>ID</th><td>culture-specific-graphic</td></tr>
<tr><th>Definition</th><td>Graphics embed cultural assumptions or references and cannot be changed</td></tr>
<tr><th>MQM Core?</th><td>no</td></tr>
<tr><th>Automatable?</th><td>no</td></tr>
<tr><th>Parent</th><td><a href="#graphical-internationalization"><code>graphical-internationalization</code></a></td></tr>
<tr><th>Children</th><td><em>none</em></td></tr>
<tr><th>Applies to</th><td>source</td></tr>
<tr><th>Example(s)</th><td><ul><li>A graphic depicts a “road trip” by showing sights familiar to a German audience that would be unknown in other locales.</li></ul></td></tr>
<tr><th>Note(s)</th><td><ul><li>If graphics can be easily changed in the localization process, this issue does not apply.</li></ul></td></tr>
</table>
<h4 id="culture-specific">Culture-specific reference</h4>
<table>
<tr><th>ID</th><td>culture-specific</td></tr>
<tr><th>Definition</th><td>Content inappropriately uses a culture-specific reference that will not be understandable to the intended audience</td></tr>
<tr><th>MQM Core?</th><td>no</td></tr>
<tr><th>Automatable?</th><td>yes</td></tr>
<tr><th>Parent</th><td><a href="#locale-convention"><code>locale-convention</code></a></td></tr>
<tr><th>Children</th><td><em>none</em></td></tr>
<tr><th>Applies to</th><td>source and target</td></tr>
<tr><th>Example(s)</th><td><ul><li>An English text refers to steps in a process as “First base”, “Second base”, and “Third base”, and to successful completion as a “Home run” and uses other metaphors from baseball. These prove difficult to translate and confuse the target audience in Germany.</li><li>An marketing text in Greek includes reference to popular Greek music. When translated into English these references are not understandable to the target audience.</li></ul></td></tr>
<tr><th>Note(s)</th><td><ul><li>In the cases of texts that were written with the intention that they be translated, this issue may indicate a broader conceptual or Internationalization problem.</li></ul></td></tr>
</table>
<h4 id="currency-format">Currency format</h4>
<table>
<tr><th>ID</th><td>currency-format</td></tr>
<tr><th>Definition</th><td>Content uses the wrong format for currency.</td></tr>
<tr><th>MQM Core?</th><td>no</td></tr>
<tr><th>Automatable?</th><td>yes</td></tr>
<tr><th>Parent</th><td><a href="#locale-convention"><code>locale-convention</code></a></td></tr>
<tr><th>Children</th><td><em>none</em></td></tr>
<tr><th>Applies to</th><td>source and target</td></tr>
<tr><th>Example(s)</th><td><ul><li>A text dealing with business transactions from English into Hindi assumes that all currencies will be expressed in simple units, while the convention in India is to give such prices in lakh rupees (100,000 rupees)</li></ul></td></tr>
<tr><th>Note(s)</th><td><ul><li>Very often this issue indicates an underlying <a href="#internationalization"><code>internationalization</code></a> problem.</li></ul></td></tr>
</table>
<h4 id="currency-internationalization">Currency internationalization</h4>
<table>
<tr><th>ID</th><td>currency-internationalization</td></tr>
<tr><th>Definition</th><td>A system does not support multiple currencies or specific currencies needed for individual markets</td></tr>
<tr><th>MQM Core?</th><td>no</td></tr>
<tr><th>Automatable?</th><td>no</td></tr>
<tr><th>Parent</th><td><a href="#localization-support"><code>localization-support</code></a></td></tr>
<tr><th>Children</th><td><em>none</em></td></tr>
<tr><th>Applies to</th><td>source</td></tr>
<tr><th>Example(s)</th><td><ul><li>An online commerce form displays all amounts in euros, but customers use the form in countries that use other currencies.</li></ul></td></tr>
<tr><th>Note(s)</th><td><ul><li>Corresponds to <a href="#currency-format"><code>currency-format</code></a> in <a href="#locale-convention"><code>locale-convention</code></a>. This is used to mark engineering problems in the source content, not specific problems in the target.</li></ul></td></tr>
</table>
<h4 id="date-format">Date format</h4>
<table>
<tr><th>ID</th><td>date-format</td></tr>
<tr><th>Definition</th><td>A text uses a date format inappropriate for its locale.</td></tr>
<tr><th>MQM Core?</th><td>no</td></tr>
<tr><th>Automatable?</th><td>yes</td></tr>
<tr><th>Parent</th><td><a href="#locale-convention"><code>locale-convention</code></a></td></tr>
<tr><th>Children</th><td><em>none</em></td></tr>
<tr><th>Applies to</th><td>source and target</td></tr>
<tr><th>Example(s)</th><td><ul><li>An English text has “2012-06-07” instead of the expected “06/07/2012.”</li></ul></td></tr>
<tr><th>Note(s)</th><td></td></tr>
</table>
<h4 id="date-internationalization">Date internationalization</h4>
<table>
<tr><th>ID</th><td>date-internationalization</td></tr>
<tr><th>Definition</th><td>Date formats are not properly internationalized</td></tr>
<tr><th>MQM Core?</th><td>no</td></tr>
<tr><th>Automatable?</th><td>no</td></tr>
<tr><th>Parent</th><td><a href="#localization-support"><code>localization-support</code></a></td></tr>
<tr><th>Children</th><td><em>none</em></td></tr>
<tr><th>Applies to</th><td>source</td></tr>
<tr><th>Example(s)</th><td><ul><li>A system displayes all dates as "Dd/Mm/Yy", resulting in dates that cannot be understood correctly in much of the world.</li></ul></td></tr>
<tr><th>Note(s)</th><td><ul><li>Corresponds to <a href="#date-format"><code>date-format</code></a> in <a href="#locale-convention"><code>locale-convention</code></a>. This is used to mark engineering problems in the source content, not specific problems in the target.</li></ul></td></tr>
</table>
<h4 id="date-time">Date/time</h4>
<table>
<tr><th>ID</th><td>date-time</td></tr>
<tr><th>Definition</th><td>Dates or times do not match between source and target.</td></tr>
<tr><th>MQM Core?</th><td>no</td></tr>
<tr><th>Automatable?</th><td>yes</td></tr>
<tr><th>Parent</th><td><a href="#mistranslation"><code>mistranslation</code></a></td></tr>
<tr><th>Children</th><td><em>none</em></td></tr>
<tr><th>Applies to</th><td>target</td></tr>
<tr><th>Example(s)</th><td><ul><li>A German source text provides the date 09.02.09 (=February 9, 2009) but the English target renders it as September 2, 2009.</li><li>An English source text specifies a time of “4:40 PM” but this is rendered as 04:40 (=4:40 AM) in a German translation.</li></ul></td></tr>
<tr><th>Note(s)</th><td></td></tr>
</table>
<h4 id="design">Design</h4>
<table>
<tr><th>ID</th><td>design</td></tr>
<tr><th>Definition</th><td>There is a problem relating to design aspects (vs. linguistic aspects) of the content.</td></tr>
<tr><th>MQM Core?</th><td>no</td></tr>
<tr><th>Automatable?</th><td>no</td></tr>
<tr><th>Parent</th><td><a href="#"><code></code></a></td></tr>
<tr><th>Children</th><td><a href="#graphics-tables"><code>graphics-tables</code></a>, <a href="#hyphenation"><code>hyphenation</code></a>, <a href="#length"><code>length</code></a>, <a href="#local-formatting"><code>local-formatting</code></a>, <a href="#markup"><code>markup</code></a>, <a href="#missing-text"><code>missing-text</code></a>, <a href="#truncation-text-expansion"><code>truncation-text-expansion</code></a>, <a href="#overall-design"><code>overall-design</code></a>, <a href="#"><code></code></a></td></tr>
<tr><th>Applies to</th><td>source and target</td></tr>
<tr><th>Example(s)</th><td><ul><li>A document is formatted incorrectly</li></ul></td></tr>
<tr><th>Note(s)</th><td><ul><li>Design issues may exist either in documentions in isolation (e.g., a second-level heading is formatted as a first-level heading) or in relationship between source and target (e.g., headings are formatted differently between source and target).</li></ul></td></tr>
</table>
<h4 id="diacritics">Diacritics</h4>
<table>
<tr><th>ID</th><td>diacritics</td></tr>
<tr><th>Definition</th><td>Issues related to the use of diacritics</td></tr>
<tr><th>MQM Core?</th><td>no</td></tr>
<tr><th>Automatable?</th><td>yes</td></tr>
<tr><th>Parent</th><td><a href="#spelling"><code>spelling</code></a></td></tr>
<tr><th>Children</th><td><em>none</em></td></tr>
<tr><th>Applies to</th><td>source and target</td></tr>
<tr><th>Example(s)</th><td><ul><li>The Hungarian word <em>bőven</em> (using o with a double acute (˝)) is spelled as <em>bõven</em>, using a tilde (˜), which is not found in Hungarian.</li></ul></td></tr>
<tr><th>Note(s)</th><td></td></tr>
</table>
<h4 id="document-external-link">Document-external link</h4>
<table>
<tr><th>ID</th><td>document-external-link</td></tr>
<tr><th>Definition</th><td>A link or cross reference points to an incorrect or nonexistent location outside of the same document within which it occurs</td></tr>
<tr><th>MQM Core?</th><td>no</td></tr>
<tr><th>Automatable?</th><td>yes</td></tr>
<tr><th>Parent</th><td><a href="#broken-link"><code>broken-link</code></a></td></tr>
<tr><th>Children</th><td><em>none</em></td></tr>
<tr><th>Applies to</th><td>source and target</td></tr>
<tr><th>Example(s)</th><td><ul><li>A link in an HTML document points to a U.S. government URL that has moved and no longer exists.</li></ul></td></tr>
<tr><th>Note(s)</th><td></td></tr>
</table>
<h4 id="document-internal-link">Document-internal link</h4>
<table>
<tr><th>ID</th><td>document-internal-link</td></tr>
<tr><th>Definition</th><td>A link or cross reference points to an incorrect or nonexistent location within the same document within which it occurs.</td></tr>
<tr><th>MQM Core?</th><td>no</td></tr>
<tr><th>Automatable?</th><td>yes</td></tr>
<tr><th>Parent</th><td><a href="#broken-link"><code>broken-link</code></a></td></tr>
<tr><th>Children</th><td><em>none</em></td></tr>
<tr><th>Applies to</th><td>source and target</td></tr>
<tr><th>Example(s)</th><td><ul><li>An internal link refers to the location “#section5” but there is no anchor “section5” in the document.</li></ul></td></tr>
<tr><th>Note(s)</th><td></td></tr>
</table>
<h4 id="duplication">Duplication</h4>
<table>
<tr><th>ID</th><td>duplication</td></tr>
<tr><th>Definition</th><td>Content has been duplicated (e.g., a word or longer portion of text is repeated unintentionally).</td></tr>
<tr><th>MQM Core?</th><td>no</td></tr>
<tr><th>Automatable?</th><td>yes</td></tr>
<tr><th>Parent</th><td><a href="#fluency"><code>fluency</code></a></td></tr>
<tr><th>Children</th><td><em>none</em></td></tr>
<tr><th>Applies to</th><td>source and target</td></tr>
<tr><th>Example(s)</th><td><ul><li>A text reads “The man the man whom she saw…”</li><li>A paragraph appears verbatim twice in a row.</li></ul></td></tr>
<tr><th>Note(s)</th><td></td></tr>
</table>
<h4 id="embedded-string-in-code">Embedded string in code</h4>
<table>
<tr><th>ID</th><td>embedded-string-in-code</td></tr>
<tr><th>Definition</th><td>String references are embedded in computer code rather than externalized to resource files. As a result the string content is accessible only by manipulatin the source code of the application.</td></tr>
<tr><th>MQM Core?</th><td>no</td></tr>
<tr><th>Automatable?</th><td>no</td></tr>
<tr><th>Parent</th><td><a href="#embedded-string"><code>embedded-string</code></a></td></tr>
<tr><th>Children</th><td><em>none</em></td></tr>
<tr><th>Applies to</th><td>source</td></tr>
<tr><th>Example(s)</th><td><ul><li>Error messages for a product are stored as variables directly in the source code of a software product and are therefore not localized when UI strings are sent for translation.</li></ul></td></tr>
<tr><th>Note(s)</th><td></td></tr>
</table>
<h4 id="embedded-string-in-graphic">Embedded string in graphic</h4>
<table>
<tr><th>ID</th><td>embedded-string-in-graphic</td></tr>
<tr><th>Definition</th><td>A graphics contains embedded text as an image that cannot be edited</td></tr>
<tr><th>MQM Core?</th><td>no</td></tr>
<tr><th>Automatable?</th><td>no</td></tr>
<tr><th>Parent</th><td><a href="#embedded-string"><code>embedded-string</code></a></td></tr>
<tr><th>Children</th><td><em>none</em></td></tr>
<tr><th>Applies to</th><td>source</td></tr>
<tr><th>Example(s)</th><td><ul><li>A service manual contains an image of a mechanical system with part labels stored in the “flattened” graphic. As a result the localization process cannot produce localized versions of the graphic</li></ul></td></tr>
<tr><th>Note(s)</th><td><ul><li>Solving this problem generally requires access to original application files used to produce graphics initially rather than to rendered down-stream versions use for web display, display in software UIs, or embedding in word-processing applications.</li></ul></td></tr>
</table>
<h4 id="embedded-string">Embedded string</h4>
<table>
<tr><th>ID</th><td>embedded-string</td></tr>
<tr><th>Definition</th><td>Textual content is embedded in other elements in ways that make it inaccessible during the localization process.</td></tr>
<tr><th>MQM Core?</th><td>no</td></tr>
<tr><th>Automatable?</th><td>no</td></tr>
<tr><th>Parent</th><td><a href="#internationalization"><code>internationalization</code></a></td></tr>
<tr><th>Children</th><td><a href="#embedded-string-in-code"><code>embedded-string-in-code</code></a>, <a href="#embedded-string-in-graphic"><code>embedded-string-in-graphic</code></a></td></tr>
<tr><th>Applies to</th><td>source</td></tr>
<tr><th>Example(s)</th><td><ul><li>The UI of an industrial system includes graphical images of text that cannot be edited as text.</li></ul></td></tr>
<tr><th>Note(s)</th><td><ul><li>The subtypes of this issue comprise the most common examples.</li></ul></td></tr>
</table>
<h4 id="end-user-suitability">End-user suitability</h4>
<table>
<tr><th>ID</th><td>end-user-suitability</td></tr>
<tr><th>Definition</th><td>The content is not suitable for use by the end user, excluding problems related to suitability for the target locale.</td></tr>
<tr><th>MQM Core?</th><td>no</td></tr>
<tr><th>Automatable?</th><td>no</td></tr>
<tr><th>Parent</th><td><a href="#verity"><code>verity</code></a></td></tr>
<tr><th>Children</th><td><em>none</em></td></tr>
<tr><th>Applies to</th><td>source and target</td></tr>
<tr><th>Example(s)</th><td><ul><li>A text describes a process to repair a device, but following the instructions leads to serious damage to the device and potential injury.</li><li>A text assumes that the reader has knowledge of advanced particular physics, but the target audience does not generally have this knowledge.</li></ul></td></tr>
<tr><th>Note(s)</th><td><ul><li>If the issue relates to the applicability of the content to users in a particular locale, <a href="#locale-specific-content"><code>locale-specific-content</code></a> should be used instead.</li><li>End-user suitability generally applies to issues present in the source text, regardless of the target locale, but may apply in cases where there are distinct differences in audience or purpose between source and target.</li></ul></td></tr>
</table>
<h4 id="entity">Entity (such as name or place)</h4>
<table>
<tr><th>ID</th><td>entity</td></tr>
<tr><th>Definition</th><td>Names, places, or other “named entities” do not match</td></tr>
<tr><th>MQM Core?</th><td>no</td></tr>
<tr><th>Automatable?</th><td>yes</td></tr>
<tr><th>Parent</th><td><a href="#mistranslation"><code>mistranslation</code></a></td></tr>
<tr><th>Children</th><td><em>none</em></td></tr>
<tr><th>Applies to</th><td>target</td></tr>
<tr><th>Example(s)</th><td><ul><li>The source text refers to Dublin, Ohio, but the target incorrectly refers to Dublin, Ireland.</li></ul></td></tr>
<tr><th>Note(s)</th><td></td></tr>
</table>
<h4 id="false-friend">False friend</h4>
<table>
<tr><th>ID</th><td>false-friend</td></tr>
<tr><th>Definition</th><td>The translation has incorrectly used a word that is superficially similar to the source word.</td></tr>
<tr><th>MQM Core?</th><td>no</td></tr>
<tr><th>Automatable?</th><td>no</td></tr>
<tr><th>Parent</th><td><a href="#mistranslation"><code>mistranslation</code></a></td></tr>
<tr><th>Children</th><td><em>none</em></td></tr>
<tr><th>Applies to</th><td>target</td></tr>
<tr><th>Example(s)</th><td><ul><li>The Italian word <em>simpatico</em> has been translated as <em>sympathetic</em> in English.</li></ul></td></tr>
<tr><th>Note(s)</th><td></td></tr>
</table>
<h4 id="fixed-collation">Fixed collation</h4>
<table>
<tr><th>ID</th><td>fixed-collation</td></tr>
<tr><th>Definition</th><td>A collation (text sorting) routine does not support locale-specific collation sequences</td></tr>
<tr><th>MQM Core?</th><td>no</td></tr>
<tr><th>Automatable?</th><td>no</td></tr>
<tr><th>Parent</th><td><a href="#functional"><code>functional</code></a></td></tr>
<tr><th>Children</th><td><em>none</em></td></tr>
<tr><th>Applies to</th><td>source</td></tr>
<tr><th>Example(s)</th><td><ul><li>The sort routine in a spreadsheet does a simple sort by Unicode code-point sequence, and does not support needed collation sequences for various markets.</li></ul></td></tr>
<tr><th>Note(s)</th><td><ul><li>Specific results of this problem will often be classified under <a href="#sorting"><code>sorting</code></a>.</li></ul></td></tr>
</table>
<h4 id="fixed-dialog-ui-size">Fixed dialog/UI size</h4>
<table>