default resource font and Factbook
Factbook - Key Article font
vs
Program settings - Default resources font
--------
I'm using the Default Sans Serif font for resources. But the Key Article font ignores it and uses a different font. Is this by design?
Comments
-
I would report it as a bug ...
Orthodox Bishop Alfeyev: "To be a theologian means to have experience of a personal encounter with God through prayer and worship."; Orthodox proverb: "We know where the Church is, we do not know where it is not."
0 -
We have a case for using the default resource font in the Key Article section. The case is currently a low priority, and I don't expect it to be implemented any time soon.
Andrew Batishko | Logos software developer
0 -
[N]
0 -
[N][N]
0 -
I strongly recommend adding a suggestion to https://feedback.faithlife.com/ and adding your vote. Priorities are not fixed in stone, and broad support for a request is a great way to see issues reprioritized.
Andrew Batishko | Logos software developer
0 -
So, you're saying it's a feature not a bug?
0 -
It's pretty sad when you have to vote to fix a bug! [:|]
0 -
Paul Strickert said:
So, you're saying it's a feature not a bug?
I suppose that depends on your definition of a bug. I wouldn't classify it as a bug, since it's currently operating as intended. This is certainly not to say that there aren't better ways it could operate.
There are lots of ways that the Key Article section does not look or behave like the resource display. We do not intend to make the Key Article section fully look and operate like the resource display, and it's not necessarily a bug when it doesn't.
Andrew Batishko | Logos software developer
0 -
TWBeining said:
It's pretty sad when you have to vote to fix a bug!
It is really just a case of resource prioritisation, how much time they will take from other projects to invest in this one.
If something is going to take 20 man days to change, and only 1% will benefit from it, how can that be a priority over 20 man days that 5% will benefit from.
Voting helps them to see what the demand actually is, and therefore where to invest limited resources.
0 -
So, what is the "case" you referred to earlier? Not a bug report? Seems kind of slippery to me, Andrew. Just sayin'.
0 -
Paul Strickert said:
So, what is the "case" you referred to earlier? Not a bug report?
A 'case' is broader than a bug report, for Faithlife.
“The trouble is that everyone talks about reforming others and no one thinks about reforming himself.” St. Peter of Alcántara
0 -
Paul Strickert said:
So, what is the "case" you referred to earlier? Not a bug report? Seems kind of slippery to me, Andrew. Just sayin'.
It turns out this is not a slippery slope. A "case" is an entry in our tracking system (or really any of a broad variety of tracking systems). The tracking system is used to track bugs, features, investigations, etc. Basically any type of work that needs to be done by any team (not just software development).
Andrew Batishko | Logos software developer
0 -
Obviously, I'm not an insider.
I can only recall "case" being used on the forums for bug reports. But I stand corrected.As for the original issue, what seems "wrong" about the info in the Factbook panel is that the font is not consistent. The Key Article font is glaringly different than the font used in other areas of the panel. I'd be satisfied with simple consistency.
Finally, you would think asking for the default resource font to be used in the Key Article section would not be asking too much. I mean, the Key Article text is taken from a standard resource. Instead, I get the impression I'm asking for something exotic. It makes me sorry I asked, to be honest.
0 -
Paul Strickert said:
I mean, the Key Article text is taken from a standard resource. Instead, I get the impression I'm asking for something exotic. It makes me sorry I asked, to be honest.
Whoa ... the request is reasonable and it should have been caught in beta. However, like any other bug, it needs to be scheduled for repair at a reasonable time ... usually this mean no other major changes are being made in the code for a later project and the bundling of all small bugs occurring in the same code to be fixed at the same time. Efficiency and control are the keystones of bug squashing.
Orthodox Bishop Alfeyev: "To be a theologian means to have experience of a personal encounter with God through prayer and worship."; Orthodox proverb: "We know where the Church is, we do not know where it is not."
0 -
Andrew's suggestion of adding a suggestion to feedback.faithlife.com -- as was done with a similar request recently, https://feedback.faithlife.com/boards/logos-mobile-app/posts/factbook-font-size-does-not-match-resrouce-font-size -- really is a good one. That feedback site helps Faithlife prioritize bug fixes.
“The trouble is that everyone talks about reforming others and no one thinks about reforming himself.” St. Peter of Alcántara
0 -
I have no problem with waiting a while. But "low priority" and "not anytime soon" seems pretty dismissive. Like, "It'll be a long wait -- if it happens at all." I'm used to Faithlife taking their time; believe me. I've waited two years for Moltmann to be included in the Theology Guide. And it still probably won't happen "anytime soon." I'm willing to be patient. I'd just like Faithlife to reciprocate with a good faith effort. Funny thing is I've been a Logos user for about 20 years. In all that time, I think I've expressed a specific concern just a couple of times, and both in the past two years -- the font issue and the Theology Guide (which was released half-baked). The Faithlife responses to each, while professional, offered not much more. "Corporate" (not "personal") is the term I'd use. Like boilerplate. Oh, well.
0 -
Paul Strickert said:
But "low priority" and "not anytime soon" seems pretty dismissive.
Not as dismissive as the correction of documentation which they say they'll do ... and two years later on the next major release is still not done. Let's say I appreciate accuracy, consistency, and polish a bit more than the Faithlife corporate culture appears to.
Orthodox Bishop Alfeyev: "To be a theologian means to have experience of a personal encounter with God through prayer and worship."; Orthodox proverb: "We know where the Church is, we do not know where it is not."
0 -
Paul Strickert said:
I have no problem with waiting a while. But "low priority" and "not anytime soon" seems pretty dismissive.
My apologies. I should have been more clear in my initial response to avoid this incorrect impression.
When I said "The case is currently a low priority", I intended "currently" to convey the message that priorities can change. I should have included the feedback link immediately.
My intent was to give a clear picture of the current state of things to avoid false optimism.
Andrew Batishko | Logos software developer
0 -
Thank you, Andrew. I've been around the forums long enough that "false optimism" is not a problem. My default setting is: Not Anytime Soon.
Thus, my reluctance even to ask. 0
