BUG: 6.8 Beta (but probably longstanding): over- (or under-)localization of collection rules

NB.Mick
NB.Mick MVP Posts: 15,972
in Beta Desktop App Forum

Today I used the German localization of Logos when I looked at the collection entries for a recently built PB and found it was listed as belonging to my recent collections non-PBs and Vyrsobooks!

 

This is obviously wrong - and is not the case in the English UI:

The bug is in the unfortunate overlocalization of metadata names, such as type and edition, used by collection rules.

The rules are straightforward and as follows: non-PBs are edition:l OR edition:e

in English UI

switching to German UI this same collection now has over 300 more books: the PBs!

Vyrsobooks are edition:e 

and again under German UI the collection yields wrong results:

 

most probably the 'e' from 'erstellt' (German for created) triggers the collection rule. 

Thus:

  • buggy behavior: collection content changes with different UI, leading to wrong results. 
  • expected behavior: collection content remains the same regardless of UI
  • hints for solution:
    • I can imagine that other software build an internal representation of such data (the three types maybe 0, 1, 2) and have the rules translated into this internal code and run against it. Maybe Logos does the same, but trips up on the way.
    • Or track the source language of a rule and run it against that language's identifiers.
    • Or translate the rules on startup: edition:u for user becomes edition:B - the relevant issue would be not to have different matches, easy to realize here ("benutzererstellt" or "selbsterstellt" as one word is more elegant than the clumsy three words "vom Benutzer erstellt"), much more tricky in the ever-growing list of types.   

Have joy in the Lord! Smile

Comments

  • NB.Mick
    NB.Mick MVP Posts: 15,972

    Huh, no word, not even “Works as designed, live with it“ or so?

    Have joy in the Lord! Smile

  • Dylan Rondeau
    Dylan Rondeau Member, Logos Employee Posts: 1,401
    https://community.logos.com/discussion/comment/792908#Comment_792908

    NB.Mick said:

    Huh, no word, not even “Works as designed, live with it“ or so?

    This seems to me a weakness of basing collections based on a single letter (though admittedly being more explicit would completely break it...), as it seems we either translate the word (which breaks the collection) or don't translate the word (which makes the localization awkward). That said, I'll create a case to see if there's something we can/want to do to improve this. 

    Dylan Rondeau, Software Tester

    Enable Logging: Mac | Windows (Right-click "Save As...")

  • NB.Mick
    NB.Mick MVP Posts: 15,972
    https://community.logos.com/discussion/comment/794411#Comment_794411

    Thanks Dylan for your reply.

    Dylan Rondeau said:

    This seems to me a weakness of basing collections based on a single letter

     

    nope, as you yourself write on:

    Dylan Rondeau said:

    being more explicit would completely break it...

    and

    Dylan Rondeau said:

    as it seems we either translate the word (which breaks the collection)

    which is exactly why I regard it as a bug. 

    Dylan Rondeau said:

    or don't translate the word (which makes the localization awkward).

    why so? The content of the other fields - such as book and author names - (and the fieldnames themselves in the rules) are not translated either!

    awkward is the unpredicatbility of what is translated and how (which makes using the command menu in non-English UI a game of try and error for many users who know the original as well as potential translations, not to speak of search syntax), and outright wrong is to have collection rules giving different results depending on the UI.

    Dylan Rondeau said:

    I'll create a case to see if there's something we can/want to do to improve this. 

    Thanks again.

    Have joy in the Lord! Smile

Categories