Lines Matching full:direction

148 #   Hebrew system was fairly simple; it used only a few direction
152 # duplicate code points, one with a left-right direction attribute and
153 # the other with a right-left direction attribute.
163 # direction attribute than the corresponding Unicode character.
166 # ELLIPSIS with strong right-left direction. However, the Unicode
167 # character HORIZONTAL ELLIPSIS has direction class neutral.
188 # 1. Matching the direction of Mac OS Hebrew characters
191 # direction attributes for the two code points - as in the case of
199 # The problem is solved with the use of direction override characters
200 # and direction-dependent mappings. When mapping from Mac OS Hebrew
201 # to Unicode, we use direction overrides as necessary to force the
202 # direction of the resulting Unicode characters.
204 # The required direction is indicated by a direction tag in the
212 # indicates LEFT-RIGHT OVERRIDE, PDF indicates POP DIRECTION
217 # When mapping several characters in a row that require direction
223 # If neutral characters that require direction forcing are already
224 # between strong-direction characters with matching directionality,
225 # then direction overrides need not be used. Direction overrides are
230 # direction of the Unicode characters. The mapping from Unicode to
232 # direction:
236 # However, this also means the direction override characters should
238 # they have been used to determine resolved direction), since the
239 # direction override information is carried by the code point itself.
241 # Even when direction overrides are not needed for roundtrip
245 # ellipsis character has direction class right-left,and there is no
247 # character has direction class neutral (which means it may end up
248 # with a resolved direction of left-right if surrounded by left-right
250 # is surrounded with a direction override to help preserve proper
251 # text layout. The resolved direction is not needed or used when