> long long debate; as I said the complex part is already solved, and I think Qt to some level have good RTL support and it has layout management, some people thought that they are too smart and they don't need to use them and they hard coded values solving that needs long time of documentation to put big signs on every method or property that set x/y coordinate, "avoid using this method unless you are aware of RTL problems, use any of layout management strategies" and of course it needs to change QA phases ..etc. because new developers will always come that's not an excuse, not being able to read Arabic is something sad but it's not the reason for those bugs, those bugs come because some people thought that they are smarter than those who wrote the BiDi layout engine in Qt for example there are new maintainers come to fedora most of them knows nothing about rpath but fedora won't accept an rpm with rpath why ? because in the review process there is a QA about rpath there is a good documentation about rpaths that's why having new maintainers is not an excuse and as I said KDE was just an failure story, it's not the problem I'm trying to solve by this post the problem wasn't with the new code having RTL problems it's how they got to those problem AGAIN let's back to the topic > Well, in KDE there will be no bug because KDE takes care of mounting devices with the utf8 flag. have you read the consistency problem 3. you introduced new incompatibility levels between the same release of fedora [take the possibility of having some file created in one desktop then mounted in another, after logging of or after using live user switch] -- fedora-devel-list mailing list fedora-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-devel-list
