Talk:Bidirectional text

message: What about mixing top/bottom and l/r or r/l on the same page?  Somewhere, I think I remember reading something about this... does anyone know the details?
: CJK are the only languages I know that can be written vertically.  CJK are traditionally written in columns from right to left. This vertical writing is not a requirement, so they are often display horizontally from left to right.  
: When you purchase CJK fonts, most fonts come w/a vertical variation (name of the vertical variation would start with @ symbol).  They are the same glyphs but rotated 90 degrees counterclockwise.  It is not meant to be read on screen, because you will have to tilt your head 90 degrees to read it.  These rotated fonts are for printing.  When you print, the text will come out vertically.  
: I know there are better implimentation of this in CSS for screen display, but I haven't seen any site using it except for demonstartion. --Voidvector 08:40, Nov 23, 2004 (UTC)
:: Yokogaki and tategaki touches on the subject of vertical and horizontal writing in CJK (but mostly J). —Tokek 06:37, 25 September 2005 (UTC)
thread_title:  vertical 

message: I am very interested to know what tools are there for making the edit pages bi-directional. That is to provide a facility in the form of a button, so the user can choose which direction he/she is going to write.  Any one knows where or how this can be done? Mehrdad 03:29, 5 May 2006 (UTC)
replies: text: As far as I know, bi-directional support is handled by the browser (client-side), not wiki server (server-side). If your browser supports bi-directional text, then the text would be displayed correctly, otherwise, no luck.--Voidvector 19:29, 6 July 2007 (UTC)
replies: text:  The statement about the Hebrew text rendering wrong in some browsers seems like incorrect "Original Research" to me.  The ordering issue isn't about characters, but text orientation and text within controls.  ABC encapsulated in P tags isn't going to render CBA, but is it [ABC  ] or [  ABC].  Whether it is CBA is about whether or not you typed CBA or ABC.  Secondly within input boxes and others it is about whether when I hit A it goes: [A     ] or [     A] and when I hit B does it go [AB    ] or [    BA].  This: http://www.i18nguy.com/markup/right-to-left.html is a good explanation completed by this: http://www.i18nguy.com/MiddleEastUI.html.  Reboot (talk) 19:09, 23 September 2008 (UTC)
thread_title:  What tools Wiki provide for bi-directional text ? 

message: This article mentions the term 'bidi' for bidirectional (of texts that include multiple scripts written in more than one direction). It is also (perhaps only historically now) a term for e.g. dot-matrix printers that can print more quickly by placing ink onto the page whichever way the print head is moving (i.e. not just printing left to right and then "inklessly" moving back to the left-hand side). Since "bidi" redirects here, should there be some sort of disambiguation page dealing with this sense?  —Preceding unsigned comment added by 86.131.102.65 (talk) 21:38, 13 November 2007 (UTC)
thread_title: "Bidi" as printing term

message: The article says, "In Unicode encoding, all non-punctuation characters are stored in writing order." This is not true: text in the Indic ranges is stored in pronunciation order, with the rendering system responsible for rearranging glyphs as the orthography demands.
Section 9.1 of the Unicode Standard 4.0 says:
The orthographic syllable is built up of alphabetic pieces, the actual letters of the Devanagari script. These pieces consist of three distinct character types: consonant letters, independent vowels, and dependent vowel signs. In a text sequence, these characters are stored in logical (phonetic) order.
(page 220)
Additionally, a few Devanagari characters cause a change in the order of the displayed characters. This reordering is not commonly seen in non-Indic scripts and occurs independently of any bidirectional character reordering that might be required.
(page 220)
The greatest variation among different Indic scripts is found in the way that the dependent vowels are applied to base letterforms. Devanagari has a collection of nonspacing dependent vowel signs that may appear above or below a consonant letter, as well as spacing dependent vowel signs that may occur to the right or to the left of a consonant letter or consonant cluster. Other Indic scripts generally have one or more of these forms, but what is a nonspacing mark in one script may be a spacing mark in another. Also, some of the Indic scripts have single dependent vowels that are indicated by two or more glyph components—and those glyph components may surround a consonant letter both to the left and right or may occur both above and below it.
The Devanagari script has only one character denoting a left-side dependent vowel sign: U+093F DEVANAGARI VOWEL SIGN I. Other Indic scripts either have no such vowel signs (Telugu and Kannada) or include as many as three of these signs (Bengali, Tamil, and Malayalam).
(page 220)
Because Devanagari and other Indic scripts have some dependent vowels that must be depicted to the left side of their consonant letter, the software that renders the Indic scripts must be able to reorder elements in mapping from the logical (character) store to the presentational (glyph) rendering. For example, if Cn denotes the nominal form of consonant C, and Vvs denotes a left-side dependent vowel sign form of vowel V, then a reordering of glyphs with respect to encoded characters occurs as just shown.
(page 228)
Anyone want to edit the article to allow for the above without straying from the scope of the article? Christian Campbell (talk) 01:57, 30 November 2007 (UTC)
thread_title:  Unicode logical store vs presentational rendering 

message: The article confuses 'weak' (numbers, mainly) with 'neutral' (punctuation and symbols) characters. The specification is here: http://unicode.org/reports/tr9/
Weak characters are sequenced together, but don't affect neutrals and can be embedded in runs of strong characters without breaking those runs. Neutral characters are sequenced within runs according to the direction of that run, or by the overall document order when they sit on the edge of a run. Iamcal (talk) 22:36, 3 March 2009 (UTC)
thread_title:  Strong vs Weak characters 

message: The Unicode U+8482 for symbol TM as mentioned seems wrong.
I convert it to decimal (3392), and use "ീ ;" in a html file, then it display an unknow symbol (ീ) in my browser.
AFAIK, both U+E150 and U+E143 are for TM symbol.
For example, H E150 == D 57680, and " ;" display as: .--Lovelywcm (talk) 00:09, 3 June 2008 (UTC)
replies: text: 8482 is the correct decimal code for TM, hexa being 2122. E143 and E150 are in a 'private use' section, meaning that there is no guarantee that these would display this sign in all situation. Clpda (talk) 20:02, 12 September 2008 (UTC)
thread_title:  Unicode for "TM" seems wrong 

message: This article is quite good in terms of content. Thank you to all those involved in writing it. But it is a bit top-heavy. Most of the content is in the introductory paragraph, before the table of contents. The opposite should be true. Introductory sections are important, for example for mobile platforms such as cell phones and PDAs where the rest of the article might not be loaded until explicitly requested. But they should be a few paragraph long rather than an entire screen. May I recommend then to summarize the current content into a couple of paragraphs and move the rest under the Table of Content, possibly breaking it down in a couple of subsections? -- manu3d (talk) 12:08, 17 September 2008 (UTC)
thread_title:  Top-Heavy article 

message: see bugzilla:000745#c4. Best regards ‫·‏לערי ריינהארט‏·‏T‏·‏m‏:‏Th‏·‏T‏·‏email me‏·‏‬ 22:31, 25 October 2009 (UTC)
thread_title:  category for languages written in [[right-to-left]] scripta 

message: The Tm-example (trade mark sign) is not convincing, since the single character wil not change an 'order' with vs. without the formatting character. -DePiep (talk) 08:53, 14 September 2010 (UTC)
thread_title:  TM-example not convincing 

message: In analogy to the Unicode section, there should be a Web standards section. AFAIK there are the CSS unicode-bidi and direction properties, the HTML dir attribute and the HTML bdo and bdi elements.--88.73.48.106 (talk) 12:51, 12 November 2011 (UTC)
thread_title:  Web standards 

message: Proposed: merge bidi Right-to-left mark (RLM) into LRM article. See: Talk:Left-to-right mark#Merger proposal: RLM into LRM. -DePiep (talk) 21:45, 28 February 2012 (UTC)
thread_title:  Merger proposal: RLM into LRM 

message: Wikipedia has an article entitled "Bidirectional" with no hyphen, and that spelling seems consistent with predominant usage.  Should the title of this article be modified accordingly? Matchups 14:18, 25 August 2014 (UTC)
replies: text: Agree. Both Unicode  and W3C (following Unicode)  do not use the hyphen (and no capital either, btw). These two are the major standards for electronic text processing. -DePiep (talk) 15:24, 25 August 2014 (UTC)
thread_title:  Article title 

message: Firefox on Linux doesn't work the way the text describes (and probably ever other OS): "حج6341" does not show the year as "1436". The text is just completely WRONG to current implementations, and could never be implemented as written as it would contradict current practice.Scientus (talk) 18:24, 25 May 2015 (UTC)
thread_title:  weak part is incorrect 

message: Hello fellow Wikipedians,
I have just modified  on Bi-directional text. Please take a moment to review my edit. If you have any questions, or need the bot to ignore the links, or the page altogether, please visit this simple FaQ for additional information. I made the following changes:
*Added archive https://web.archive.org/web/20030604190424/http://crl.nmsu.edu:80/~mleisher/ucdata.html to http://crl.nmsu.edu/~mleisher/ucdata.html
*Added archive https://web.archive.org/web/20110721134455/http://imagic.weizmann.ac.il/~dov/Hebrew/logicUI24.htm to http://imagic.weizmann.ac.il/~dov/Hebrew/logicUI24.htm
When you have finished reviewing my changes, please set the checked parameter below to true or failed to let others know (documentation at ).
Cheers.—InternetArchiveBot (Report bug) 15:39, 1 November 2016 (UTC)
thread_title:  External links modified 

message: :The following is a closed discussion of a requested move. Please do not modify it. Subsequent comments should be made in a new section on the talk page. Editors desiring to contest the closing decision should consider a move review after discussing it on the closer's talk page. No further edits should be made to this discussion. 
The result of the move request was: Moved to Bidirectional text per WP:NCCPT. Those who favor the hyphen are free to start a new RM, but the original proposal did not include it, and a move to Bi-directional text has been disputed. No such user (talk) 11:44, 23 October 2019 (UTC)
replies: text: Bidirectional Text →  – This is not a proper noun. — Eru·tuon 16:58, 16 October 2019 (UTC)

text: The above discussion is preserved as an archive of a requested move. Please do not modify it. Subsequent comments should be made in a new section on this talk page or in a move review. No further edits should be made to this section.
For what it's worth, the hyphenless variant is much more common in our titles  16:3. No such user (talk) 11:44, 23 October 2019 (UTC)
thread_title:  Requested move 16 October 2019 

message: When vehicles are inscribed with front-to-back text in both sides, Arabic numbers are left-to-right from what I see in the pictures. 
Is it always so?
--Error (talk) 12:54, 28 April 2021 (UTC)
thread_title:  Front-to-back text and numbers