Lines Matching full:direction
26 # direction overrides. Update URLs, notes.
111 # it used only a few direction classes (instead of the 19 now used in
114 # characters were encoded twice, one with a left-right direction
115 # attribute and the other with a right-left direction attribute. This
126 # direction attribute than the corresponding Unicode character.
129 # ELLIPSIS with strong right-left direction. However, the Unicode
130 # character HORIZONTAL ELLIPSIS has direction class neutral.
190 # 1. Matching the direction of Mac OS Farsi characters
193 # direction attributes for the two code points - as in the case of
201 # The problem is solved with the use of direction override characters
202 # and direction-dependent mappings. When mapping from Mac OS Farsi
203 # to Unicode, we use direction overrides as necessary to force the
204 # direction of the resulting Unicode characters.
206 # The required direction is indicated by a direction tag in the
214 # indicates LEFT-RIGHT OVERRIDE, PDF indicates POP DIRECTION
219 # When mapping several characters in a row that require direction
225 # If neutral characters that require direction forcing are already
226 # between strong-direction characters with matching directionality,
227 # then direction overrides need not be used. Direction overrides are
232 # direction of the Unicode characters. The mapping from Unicode to
234 # direction:
238 # However, this also means the direction override characters should
240 # they have been used to determine resolved direction), since the
241 # direction override information is carried by the code point itself.
243 # Even when direction overrides are not needed for roundtrip
247 # ellipsis character has direction class right-left,and there is no
249 # character has direction class neutral (which means it may end up
250 # with a resolved direction of left-right if surrounded by left-right
252 # is surrounded with a direction override to help preserve proper
253 # text layout. The resolved direction is not needed or used when