Ben Burton

Inconsistencies around rendering {\i} in unicode

Date-Modified unusable in smart groups

Fair enough - I'm not suggesting any change to the rule for smart group queries (which I agree would be bad for several reasons). The reason I filed this was that in testing I was unable to deduce what the rule was, and it wasn't clear to me if it was because the rule was complex, or if it was because there was a bug in the implementation. I understand now from your comments that the rule for smart group queries is: "look at the parent if and only if (1) the query uses a named field, or (2) the field...

Hi Christiaan - thanks for looking into all of these issues so quickly. :) Regarding inheritance: what you say is very reasonable - whether the search sees the inherited field depends on the field type. The problem I've run into is that it doesn't just depend on the field type - it also depends on the type of query being used in the search rule. What I'm suggesting is that either the child entry should pass both the "geometry" tests, or it should pass none. Likewise, it should either pass both the...

Inconsistent crossref inheritance in smart groups

Hum, it seems the SourceForge tracker has mangled the diff as though it were markup text. I've attached the patch again as a separate file here.

Unnecessary space requirement in tex-to-unicode conversion

Cannot create Remote URL rules in smart groups