Arabic was recently added to Crowdin for translating the issue tracker. Assuming it or any other RTL language are worked on and we pull them in, we'll need to make sure the UI can properly display pages for these languages.
Labels |
Added:
UI
|
Thanks for the great work!
thanks for great job.
I'm Hussein Al-bosyri Arabic JDocs Translations WG,JDocs Working Group.
the work is perfect but one thing if there is a code in the text like source code for any file, the text must be in LTR because All codes in English that's include documents in translation pages, for better visual.
thanks again for your work.
Hi Hussein,
If I understand you well, you mean, for example, being able to keep Joomla! 3.6.2 with LTR display in a RTL page, right?
Hi Sandra
No that's another thing, I mean when there is a source code for any file or any example code, The code must be in LTR,. because the code in English language always .
Span lang=en dir=RTL
On 27 Aug 2016 11:04 p.m., "Hussien Al Bosyri" notifications@github.com
wrote:
Hi Sandra
No that's another thing, I mean when there is a source code for any file
or any example code, The code must be in LTR,. because the code in English
language always .—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
#852 (comment), or mute
the thread
https://github.com/notifications/unsubscribe-auth/ABPH8Xe5yV-6xEd277TUA17l-cGuRKKyks5qkLR6gaJpZM4JZHsY
.
protected function parse($raw)
{
$o = new stdClass;
$o->text = $raw;
$this->dispatcher->trigger('onContentPrepare', array('com_tracker.markdown', &$o, new JRegistry));
echo $o->text;
in any screen it must be LTR not RTL.
that's mean left align not right align to the code.
Sorry I of course meant to type LTR
yes brianteeman.
correct
there is another issue in https://issues.joomla.org/markdown => table =>Alignment. the second line in table. colon on the right of the line for value field in LTR language but in RTL language the line is wrong.
| --------- | -----:| this is for RTl but visually it is appear like |:----- |--------- |
you can see the first photo for English(LTR) the second for Arabic(RTL).
so in alignment in table the second line visually is wrong becuase the colon on the left of the separator for value field not for item field.
and in formatting section
the same thing in line to of the table.
and ! in appear in code function name but the output is right.
Some of this is rendered directly through GitHub's Markdown parser, which
IIRC doesn't let you specify something like a direction. So we'll need to
go through the resulting markup on examples page to make tweaks as needed
and add some CSS rules in places we won't be able to manipulate the markup
(unless we want to add our own handler to the mix too).
On Saturday, August 27, 2016, Hussien Al Bosyri notifications@github.com
wrote:
[image: arabic]
https://cloud.githubusercontent.com/assets/20782472/18030542/fc9fa9ca-6cb8-11e6-8d74-67fa214c5ffa.jpg—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
#852 (comment), or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAWfoXJ0wIm-fdKiOpPooQMWBnpBS5vXks5qkL7UgaJpZM4JZHsY
.
i think that's right it's for Markdown. but this will solve a lot of problemin RTL lang. can we put as issue for future.
this will solve problem e.g
the translator translate sentences right but in view it appear deference. when viewing translate from else person they will correct the translate in wrong way. even it's right in view or display on page but still not correct when we solve it we will need to correct again the translation.
For now I've got the markdown examples all wrapped in div elements and forcing LTR display since they're all hardcoded English, this way they'll at least display correctly with the language they're written in even with a RTL language active. Still have a bunch of tweaks to make in general but at least this is one less thing to take care of.
thanks all
For now the output is perfect.
On Sun, Aug 28, 2016 at 1:59 AM, Michael Babker notifications@github.com
wrote:
For now I've got the markdown examples all wrapped in div elements and
forcing LTR display since they're all hardcoded English, this way they'll
at least display correctly with the language they're written in even with a
RTL language active. Still have a bunch of tweaks to make in general but at
least this is one less thing to take care of.—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
#852 (comment), or mute
the thread
https://github.com/notifications/unsubscribe-auth/AT0diCxTsJxp6tI2SXeJ14BrtVUe5T0Bks5qkM9GgaJpZM4JZHsY
.
Status | New | ⇒ | Closed |
Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2016-11-25 03:46:34 |
Closed_By | ⇒ | mbabker |
Arabic's deployed now and the work I've been doing for the template to support RTL display (since the same person also translated the 3.x landing page) is added in now. All in all things aren't too bad, just some minor quirks (as expected).