Results 1 to 11 of 11

Thread: Fall back to untranslated mode

Hybrid View

Previous Post Previous Post   Next Post Next Post
  1. #1
    Join Date
    Jan 2006
    Location
    Warsaw, Poland
    Posts
    33,376
    Qt products
    Qt3 Qt4 Qt5 Qt/Embedded
    Platforms
    Unix/X11 Windows Android Maemo/MeeGo
    Thanks
    4
    Thanked 5,019 Times in 4,795 Posts
    Wiki edits
    10

    Default Re: Fall back to untranslated mode

    That's why I ask you to try with my code... there is no such thing as "untranslated" mode. There always is a translation (of course if you use tr() calls), even if you don't provide any. Try loading an "empty" translation catalog (note my "en" suffix) and see if it works properly (especially if "load" returns true).

  2. #2
    Join Date
    Jan 2006
    Location
    travelling
    Posts
    1,116
    Qt products
    Qt4
    Platforms
    Unix/X11 Windows
    Thanks
    8
    Thanked 127 Times in 121 Posts

    Default Re: Fall back to untranslated mode

    Quote Originally Posted by wysota View Post
    There always is a translation (of course if you use tr() calls)
    The point is, and I can confirm this happens even with a translation loaded, a string that IS NOT handled by current translators WILL BE handled by old translators EVEN IF they have been REMOVED and DESTROYED... This is merely what I call a bug... Does anyone know a way to prevent such thing to happen?
    Current Qt projects : QCodeEdit, RotiDeCode

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
Qt is a trademark of The Qt Company.