Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Get Qt Extensions
  • Unsolved
Collapse
Brand Logo
  1. Home
  2. Qt Development
  3. Qt Creator and other tools
  4. lupdate misses strings when called with absolute path
Forum Update on Tuesday, May 27th 2025

lupdate misses strings when called with absolute path

Scheduled Pinned Locked Moved Unsolved Qt Creator and other tools
lupdate
1 Posts 1 Posters 603 Views 2 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • R Offline
    R Offline
    rkohser
    wrote on 4 May 2017, 14:05 last edited by rkohser 5 Apr 2017, 14:06
    #1

    Hi,

    I am witnessing a really weird behaviour regarding the direct call of lupdate :
    When I call

    lupdate C:\project\source -ts result_fr.ts 
    

    I get :

    Updating 'result_fr.ts'...
        Found 56 source text(s) (14 new and 42 already existing)
    

    but if I call it to scan the local directory, which is C:\project\source\ :

    lupdate . -ts result_fr.ts 
    

    I get :

    Updating 'result_fr.ts'...
        Found 42 source text(s) (0 new and 42 already existing)
        Kept 14 obsolete entries
    

    So it seems that the outcome of lupdate is dependant on the using of absolute/relative path. An interesting detail is that the 14 entries difference are only QT_TRANSLATE_NOOP calls. Does anybody have an idea of what's happening here ?

    I am using Qt 5.6.0.

    Thanks,

    Roland

    1 Reply Last reply
    0

    1/1

    4 May 2017, 14:05

    • Login

    • Login or register to search.
    1 out of 1
    • First post
      1/1
      Last post
    0
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Search
    • Get Qt Extensions
    • Unsolved