14 replies to this topic

[Son seeker]

A personal request to all Module Makers:

Please format your modules so they utilize e-Sword's user font settings. (Font style, size, etc.) This ensures a uniform "look" across e-Sword. The way it is now many modules are a disarrayed mix of different fonts, sizes, etc. which makes e-Sword look less professional than it could . . . and should.

Thanks for taking this request into consideration. And thanks for all the time and effort you invest in these resources for others!

[Josh Bond]

A personal request to all Module Makers:

Please format your modules so they utilize e-Sword's user font settings. (Font style, size, etc.) This ensures a uniform "look" across e-Sword. The way it is now many modules are a disarrayed mix of different fonts, sizes, etc. which makes e-Sword look less professional than it could . . . and should.

Thanks for taking this request into consideration. And thanks for all the time and effort you invest in these resources for others!

In ToolTip NT, the module maker should have Module > Font Size Set By e-Sword checked. I've tried to get folks to do this for Bibles, Commentaries, Dictionaries, Devotions

Unfortunately, Topic/Resource Library modules can't be made this way. It's the way e-Sword is programmed. The module maker must specify a font type and size, and it overrides anything the user has specified.

[jonathon]

Please format your modules so they utilize e-Sword's user font settings. (Font style, size, etc.) This ensures a uniform "look" across e-Sword

+1

Unfortunately, Topic/Resource Library modules can't be made this way. It's the way e-Sword is programmed.

I think that that is a bigger flaw than the issue you have with commentaries.

jonathon

[superaben]

Unfortunately, Topic/Resource Library modules can't be made this way. It's the way e-Sword is programmed. The module maker must specify a font type and size, and it overrides anything the user has specified.

Although this question has probably already been expressed somewhere, for a refresher for those of us who do a few Topic modules, what are the "best" font settings to use that match the majority of e-Sword users' desires? Is Times New Roman 12 point normally a safe choice?

Thanks!

[DSaw]

I use CTRL+scroll wheel too zoom in ref and topic window also works on bible dictionary and commentary windows it will adjust to to what ever reading size you like it does not chnge font size just zooms in

[Josh Bond]

Although this question has probably already been expressed somewhere, for a refresher for those of us who do a few Topic modules, what are the "best" font settings to use that match the majority of e-Sword users' desires? Is Times New Roman 12 point normally a safe choice?

Thanks!

Times New Roman 12 or Georgia 11. I prefer Georgia because Times New Roman shows an underscore _ on a different elevation than an underline. So on many computers, verse references are just ugly in Times New Roman--the underline in the verse reference appears separate from the underlining of the whole verse. Now, after I convert material to other Bible software formats, I will change the Georgia to whatever font they use, such as Tahoma.

How's that for picky?

Gen_1:1 - Georgia
Gen_1:1 - Times New Roman

[DoctorDaveT]

I use Times New Roman 12 as my standard font for just about every .topx./.refx module I build. Old habits die hard.

[patchworkid]

hi all,

Thanks for the info about T4 checking the RTF old output. - It does shrink the size the of module. and what is the rtf header?

thanks

[Josh Bond]

hi all,

Thanks for the info about T4 checking the RTF old output. - It does shrink the size the of module. and what is the rtf header?

thanks

You should not use the RTF Header unless you have a good reason to. If you don't know what the RTF header is, then that's a good reason not to use it.

You would use the RTF header in commentaries and dictionaries, when foreign language requires a legacy font. The RTF Header will let you specify a font for certain words. I used it on a few modules but now, I convert the font to unicode to avoid RTF headers. I've remade most of the modules that had RTF headers.

The huge drawback with RTF headers is it overrides the user's font type and size preferences. And we receive lots of complaints on modules with an RTF header. It's a bad idea for e-Sword. All official modules do not have an RTF header--and there's a good reason for that.

[APsit190]

I use Times New Roman 12 as my standard font for just about every .topx./.refx module I build. Old habits die hard.

Hi Dave,
Yeah, I'm like that too. Fact is I've changed my e-Sword Font settings to read Times New Roman 12 right across the board with the exception of Hebrew and Greek which remains at Titus thingy. Other foreign language font settings are not an issue to me as I don't use them.

Blessings,