Open nus-pe-bot opened 2 weeks ago
Due to English being a RTL writing system, and Arabic being a LTR writing system, we do not anticipate anyone to use the two together in writing, and thus it did not seem like a valid factor to address in our app as of this version.
Our current implementation is blind to languages other than English, the main reason being that resource is a constraint and it is not feasible to account for every language. Allowing non-English characters to be used in the details section is a flexibility we extend to the user, but we believe that handling the intricacies of each individual language and the mixing of languages should be left to the user.
We think that this suggestion is still somewhat valid in future, and if we have increased funding, someone experienced in allowing for multi-language support could be hired to expand the app to accurately support more than just English, so we rejected it as Not In Scope
.
--
The details sections appears to accept arabic characters. However, since it reads from right to left, any english characters placed after it is formatted to be placed before it.
In the addressbook.json file: the english characters are placed after the arabic ones
In the application: the english characters are formatted to be before the arabic ones
Implication: This could change the meaning of the detail entirely and could hinder the study. As such, I have placed it as severity medium
[original: nus-cs2103-AY2425S1/pe-interim#2133] [original labels: severity.Medium type.FunctionalityBug]