Arabic issue #41: Function names and Qt Documentation fails to consider RTL many times
by Munzir Taha
Hi Cuters,
For example:
qstring.html
"QString QString::right ( int len ) const
Returns a substring that contains the len rightmost characters of the string"
For RightToLeft language this would be the leftmost characters of the string.
So, it's better to say the trailing characters of the string.
I suggest that we have overloaded member functions, provided for convenience
to cater for these direction-based functions. For example: QString
QString::trailing
qtextedit.html
"The default mode is WidgetWidth which causes words to be wrapped at the right
edge of the text edit"
This should be at the trailing edge of the text edit.
and sure many other examples...
--
Munzir Taha PGP Key available
gpg --recv-keys --keyserver www.mandrakesecure.net F0671821
Telecommunications and Electronics Engineer
Mandrake Club Member
Maintainer of the OpenBugs project page at
http://www.arabic-fedora.org/munzir/OpenBugs.html
Maintainer of Fedora Arabic Translation Project
https://listman.redhat.com/mailman/listinfo/fedora-trans-ar
Master CIW Designer, ICDL, MOUS, Linux+, LPI 101
New Horizons CLC, Riyadh, SA
19 years
Re: Arabic issue #32: The conversion of a localized 'const QString' to 'double' returns 0
by Munzir Taha
On Yaum al-Sabt 28 Rabi` al-Awal 1426 01:54, you wrote:
> I would say that depends on whether or not you've called
> QTextCodec::setCodecForCStrings() to tell it bare const char * and
> QByteArray should be interpreted as utf-8 (I believe the default is
> latin-1, but I'd probably be explicit if I was using anything other than
> ascii).
Thanks a lot Puetz for your reply but what's confusing me is if I can
QLocale::setDefault(QLocale::German);
d = QString( "1234,56" ).toDouble(&ok); // ok == true, d == 1234.56
without calling QTextCodec::setCodecForCStrings() or trUtf8, why not for
QLocale::Arabic? Is this because the German comma is within ascii range? Is
this justified? Is it for performance reasons that the default is latin-1 and
not utf8?
> > > QLocale ar(QLocale::Arabic);
> > > double d = ar.toDouble( "١٢٣" );
> > Now I found if I do it like this:
> > d = arabic.toDouble(QObject::trUtf8("١٢٣"));
> >
> > It works! Should I consider this bug as invalid?
--
Munzir Taha PGP Key available
gpg --recv-keys --keyserver www.mandrakesecure.net F0671821
Telecommunications and Electronics Engineer
Mandrake Club Member
Maintainer of the OpenBugs project page at
http://www.arabic-fedora.org/munzir/OpenBugs.html
Maintainer of Fedora Arabic Translation Project
https://listman.redhat.com/mailman/listinfo/fedora-trans-ar
Master CIW Designer, ICDL, MOUS, Linux+, LPI 101
New Horizons CLC, Riyadh, SA
19 years
Re: Arabic issue #17: QProgressBar displays the percentage sign in the wrong postion when reversed!
by Munzir Taha
On Yaum al-Khamees 15 Muharram 1426 13:38, Morten Sørvig wrote:
> On Thursday 24 February 2005 09:37, Munzir Taha wrote:
> > On Yaum al-Arbi'a 29 Thu al-Hijjah 1425 7:01 am, Munzir Taha wrote:
> > > Qt Version: qt-x11-opensource-4.0.0-b2-snapshot-20050131
> > > System: Mandrake 10.1 on AMD64
> > >
> > >
> > > CODE:
> > > QProgressBar *w = new QProgressBar(0);
> > >
> > > PROBLEM:
> > > In reverse Mode we expect to see %24 instead of 24%.
> >
> > This wasn't fixed though it's a trivial fix. I believe this should go in
> > the API rather than subclassing, no?
>
> Hi Munzir, this should be fixed now. Thanks for reporting.
Morten, it was working but now with
Qt 4.0.0-rc1-snapshot-20050429
It doesn't seem to work any more. Is this intentional?!
--
Munzir Taha PGP Key available
gpg --recv-keys --keyserver www.mandrakesecure.net F0671821
Telecommunications and Electronics Engineer
Mandrake Club Member
Maintainer of the OpenBugs project page at
http://www.arabic-fedora.org/munzir/OpenBugs.html
Maintainer of Fedora Arabic Translation Project
https://listman.redhat.com/mailman/listinfo/fedora-trans-ar
Master CIW Designer, ICDL, MOUS, Linux+, LPI 101
New Horizons CLC, Riyadh, SA
19 years