Bug 99583 - Increased Text Flow Options Providing Multicultural Support
Summary: Increased Text Flow Options Providing Multicultural Support
Status: RESOLVED INSUFFICIENTDATA
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Linguistic (show other bugs)
Version:
(earliest affected)
unspecified
Hardware: All All
: medium enhancement
Assignee: Not Assigned
URL:
Whiteboard:
Keywords: needsDevAdvice
Depends on:
Blocks:
 
Reported: 2016-04-29 21:38 UTC by Kenneth Slayor
Modified: 2018-11-05 16:12 UTC (History)
3 users (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Kenneth Slayor 2016-04-29 21:38:52 UTC
There are alphabets, abjads, syllaberies, etc., such as the Phags-pa, Mongolian, Chinese, Korean, and hieroglyphic systems which do not have to use or simply do not use the traditional left to right or right to left text flow.  One such can be found at the following: http://www.mongolfont.com/ .   If the text flow could be set to various directions (R to L, L to R, T to B, B to T) this would make the use of traditional languages, either as subjects of study or attempting to hold their own in the face of extinction in an era where technology is not produced for their needs, accessible in the modern world.

Of these languages, modernizing to include Mayan might be the hardest as it operates in pictographic syllables arranged in pairs running from top to bottom.  It would be like allowing two Kanji/Hanja/Chinese Characters on a row writing down the column.

I cannot code.  I study linquistics, history, culture, etc.  Programming is not only beyond me, but the last language that made any sense to me was GFA basic decades ago.  However, as a philosopher and student of history it is my hope that this change will be important to you since it will provide access to those human expressions struggling to stave off extinction or find a place in the modern world.

Thank you for your time and consideration,
Kenneth W. Slayor
Comment 1 Buovjaga 2016-05-06 12:07:13 UTC
Kenneth: you seem to want to contribute in other ways. One possibility is to look at unconfirmed bugs that have to do with the languages you work with (rendering issues etc.) and confirm them.
Here is our general intro to bug confirming: https://wiki.documentfoundation.org/QA/Triage_For_Beginners
Comment 2 Volga 2016-11-20 17:10:54 UTC Comment hidden (obsolete)
Comment 3 Volga 2016-11-20 17:13:31 UTC Comment hidden (obsolete)
Comment 4 Xisco Faulí 2017-11-29 10:06:07 UTC
@Buovjaga, Do you think we should move this issue to NEW and put it in the crazy ideas list?
Comment 5 Buovjaga 2017-11-29 10:43:44 UTC
Well, I think Kenneth should describe in more detail what is still needed. Like Volga commented, we now have LTR vertical.
Comment 6 Volga 2018-01-03 07:14:39 UTC
(In reply to Buovjaga from comment #5)
> Well, I think Kenneth should describe in more detail what is still needed.
> Like Volga commented, we now have LTR vertical.
Yes, but the implementation is very limited, because only Writer got support for this, and no way to enable in text box.
Comment 7 Jean-Baptiste Faure 2018-03-11 12:01:31 UTC
Set status to NEEDINFO from comment #5, please set it back to UNCONFIRMED once requested informations are provided.

Best regards. JBF
Comment 8 QA Administrators 2018-10-09 11:26:28 UTC Comment hidden (obsolete)
Comment 9 QA Administrators 2018-11-05 16:12:04 UTC
Dear Bug Submitter,

Please read this message in its entirety before proceeding.

Your bug report is being closed as INSUFFICIENTDATA due to inactivity and
a lack of information which is needed in order to accurately
reproduce and confirm the problem. We encourage you to retest
your bug against the latest release. If the issue is still
present in the latest stable release, we need the following
information (please ignore any that you've already provided):

a) Provide details of your system including your operating
   system and the latest version of LibreOffice that you have
   confirmed the bug to be present

b) Provide easy to reproduce steps – the simpler the better

c) Provide any test case(s) which will help us confirm the problem

d) Provide screenshots of the problem if you think it might help

e) Read all comments and provide any requested information

Once all of this is done, please set the bug back to UNCONFIRMED
and we will attempt to reproduce the issue. Please do not:

a) respond via email 

b) update the version field in the bug or any of the other details
   on the top section of our bug tracker

Warm Regards,
QA Team

MassPing-NeedInfo-20181105