Better "disp" value for \n or \r content

Issue #19 new
Chase Tingley
created an issue

See also Okapi issue 626, which is the same issue for XLIFF 1.2.

Attached are a sample XML file and ITS rules to extract codes for the text \n and \r. However, when extended code attributes are used, the disp value for these codes is a literal newline/carriage return.

Some users may prefer an alternate (visible) representation of these characters. (<n> / <r> has been suggested, but I don't know if there are other commonly-used conventions.)

Comments (0)

  1. Log in to comment