Font Conversion & Repair - Revision history

Geep: /* Additional constraints on changing metrics of long-deployed fonts */

2024-03-18T15:28:58Z

Additional constraints on changing metrics of long-deployed fonts

← Older revision		Revision as of 15:28, 18 March 2024
Line 57:		Line 57:
	Consider a particular TDM font that has been in use for a while, and likely incorporated into, say, the readables of many FMs. Suppose you'd like to improve a particular character within it, say, by adjusting its DAT metrics. Maybe the glyph is showing stray marks from adjoining characters in its bitmap.		Consider a particular TDM font that has been in use for a while, and likely incorporated into, say, the readables of many FMs. Suppose you'd like to improve a particular character within it, say, by adjusting its DAT metrics. Maybe the glyph is showing stray marks from adjoining characters in its bitmap.

	It's generally safe to move the bitmap cell horizontally a pixel at a time, by changing x-axis corner metrics s & s2 together, keeping imageWidth unchanged. (~~Exception~~: if the glyph is abutted against the overall bitmap side boundary, the alternative of bitmap surgery may be needed.)		It's generally safe to move the bitmap cell boundaries horizontally a pixel at a time, by changing x-axis corner metrics s & s2 together, keeping imageWidth unchanged. When you do that, generally the "pitch" value (which denotes an xOffset distance from the s edge to the layout origin) needs compensating adjustment, to keep the layout origin the same with respect to the glyph. (Note: if the glyph is abutted against the overall bitmap side boundary, this approach may not be viable; the alternative of bitmap surgery may be needed.)

	~~On the other hand,~~ changing the xSkip value that controls a character’s horizontal spacing ~~can be problematic~~. A readable’s author may have designed a particular text layout and expect word-wraps at particular place. An enlarged xSkip may force the end of a readable’s paragraph off the page. Even a shortened xSkip might interfere, e.g., with "ASCII art", tabular presentation, or bullet-point-style indentations that rely on word-wrap within a paragraph instead of separated sentences. So, either forego such a change, or be prepared to research into where and how the candidate font character is used across FMs, including in translation strings.		More problematic would be changing the xSkip value that controls a character’s horizontal spacing. Why? A readable’s author may have designed a particular text layout and expect word-wraps at particular place. An enlarged xSkip may force the end of a readable’s paragraph off the page. Even a shortened xSkip might interfere, e.g., with "ASCII art", tabular presentation, or bullet-point-style indentations that rely on word-wrap within a paragraph instead of separated sentences. So, either forego such a change, or be prepared for difficult research into where and how the candidate font character is used across FMs, including in translation strings.

	A change to ImageWidth in theory has similar concerns, but in the more limited context of affecting only the first character rendered in any given line. So shrinking it is far less likely to be a problem in practice.		A change to ImageWidth in theory has similar concerns, but in the more limited context of affecting only the first character rendered in any given line. So shrinking it is far less likely to be a problem in practice.

Geep: Add the Cautionary Considerations section

2024-03-17T17:54:43Z

Add the Cautionary Considerations section

← Older revision		Revision as of 17:54, 17 March 2024
Line 43:		Line 43:
	''Geep adds: see [[Font Files]] for a fuller, more recent treatment about font file usage. For more details about Fidcal's 2009 improvements to TDM fonts, see [https://forums.thedarkmod.com/index.php?/topic/8265-found-a-way-to-repair-fonts-at-last/#comment-163449 this forum thread].''		''Geep adds: see [[Font Files]] for a fuller, more recent treatment about font file usage. For more details about Fidcal's 2009 improvements to TDM fonts, see [https://forums.thedarkmod.com/index.php?/topic/8265-found-a-way-to-repair-fonts-at-last/#comment-163449 this forum thread].''

	== ~~For More~~ ==		== Main Tools ==
	* [[ExportFontToDoom3]] is, as Fidcal says, the recommended method, if you want to start a Doom3/TDM font project by generating from a TrueType font.		* [[ExportFontToDoom3]] is, as Fidcal says, the recommended method, if you want to start a Doom3/TDM font project by generating from a TrueType font.
	* [[Q3Font]] is the traditional Windows utility program to fix Doom3/TDM fonts. Fidcal provides a simple example of using it. (Some of this info used to be here in Font Conversion & Repair; some is an update.)		* [[Q3Font]] is the traditional Windows utility program to fix Doom3/TDM fonts. Fidcal provides a simple example of using it. (Some of this info used to be here in Font Conversion & Repair; some is an update.)
	* [[Refont]] is another command-line program, new in 2024, that handles some of Q3font's functionality, but is easier to use. This article includes a detailed comparison.		* [[Refont]] is another command-line program, new in 2024, that handles some of Q3font's functionality, but is easier to use. This article includes a detailed comparison.
	* [[Font Patcher]] details the font_patcher.pl utility, which is a preferred method (over Q3font) to fix and change fonts. Includes links to examples.		* [[Font Patcher]] details the font_patcher.pl utility, which is a preferred method (over Q3font) to fix and change fonts. Includes links to examples.

			== Cautionary Considerations ==
			=== Usually convert only once ===
			If a font was converted from TrueType and subsequently received tweaks and repairs to its DAT or DDS files (as is very common), then you never want to apply conversion again, because that will throw away all those time-consuming customizations.
			=== When changing font metrics in the DAT File ===
			General constraints on the values of font metrics in a DAT file are discussed in [[Font Metrics & DAT File Format]].
			=== Additional constraints on changing metrics of long-deployed fonts ===
			Consider a particular TDM font that has been in use for a while, and likely incorporated into, say, the readables of many FMs. Suppose you'd like to improve a particular character within it, say, by adjusting its DAT metrics. Maybe the glyph is showing stray marks from adjoining characters in its bitmap.

			It's generally safe to move the bitmap cell horizontally a pixel at a time, by changing x-axis corner metrics s & s2 together, keeping imageWidth unchanged. (Exception: if the glyph is abutted against the overall bitmap side boundary, the alternative of bitmap surgery may be needed.)

			On the other hand, changing the xSkip value that controls a character’s horizontal spacing can be problematic. A readable’s author may have designed a particular text layout and expect word-wraps at particular place. An enlarged xSkip may force the end of a readable’s paragraph off the page. Even a shortened xSkip might interfere, e.g., with "ASCII art", tabular presentation, or bullet-point-style indentations that rely on word-wrap within a paragraph instead of separated sentences. So, either forego such a change, or be prepared to research into where and how the candidate font character is used across FMs, including in translation strings.

			A change to ImageWidth in theory has similar concerns, but in the more limited context of affecting only the first character rendered in any given line. So shrinking it is far less likely to be a problem in practice.

			== For More ==
	* [[I18N]] (Internationalization) introduces consideration for non-English languages.		* [[I18N]] (Internationalization) introduces consideration for non-English languages.
	* [[I18N - Charset]] details the TDM-specific character mapping for non-English languages. For instance, if you convert a Russian font, you need to move the character 0xFF to 0xB6, otherwise it will not show in the GUI or readables.		* [[I18N - Charset]] details the TDM-specific character mapping for non-English languages. For instance, if you convert a Russian font, you need to move the character 0xFF to 0xB6, otherwise it will not show in the GUI or readables.

	{{tutorial}} [[Category:Fonts]]		{{tutorial}} [[Category:Fonts]]

Geep: /* Fidcal's Original Take */ add links

2024-03-10T19:41:07Z

Fidcal's Original Take: add links

← Older revision		Revision as of 19:41, 10 March 2024
Line 41:		Line 41:
	This means it is not necessary to create other sizes, as these will be ignored, anyway.		This means it is not necessary to create other sizes, as these will be ignored, anyway.

	''Geep adds: see [[Font Files]] for a fuller, more recent treatment.''		''Geep adds: see [[Font Files]] for a fuller, more recent treatment about font file usage. For more details about Fidcal's 2009 improvements to TDM fonts, see [https://forums.thedarkmod.com/index.php?/topic/8265-found-a-way-to-repair-fonts-at-last/#comment-163449 this forum thread].''

	== For More ==		== For More ==

Geep: /* Fidcal's Original Take */ Link to new Font Files article

2024-03-09T22:07:52Z

Fidcal's Original Take: Link to new Font Files article

← Older revision		Revision as of 22:07, 9 March 2024
Line 41:		Line 41:
	This means it is not necessary to create other sizes, as these will be ignored, anyway.		This means it is not necessary to create other sizes, as these will be ignored, anyway.

	''Geep adds: ~~Size 48 is also used~~ for ~~titles of some readables~~, ~~like those Stone font. The subtitle system as of TDM 2.12 uses Stone size 24, with (at render time) horizontal compression~~.''		''Geep adds: see [[Font Files]] for a fuller, more recent treatment.''

	== For More ==		== For More ==

Geep: /* For repair of TDM metrics */

2024-03-07T17:31:00Z

For repair of TDM metrics

← Older revision		Revision as of 17:31, 7 March 2024
Line 17:		Line 17:

	=== For repair of TDM metrics ===		=== For repair of TDM metrics ===
	** [[Refont]] - New in 2024		* [[Refont]] - New in 2024
	** [[Q3Font]]		* [[Q3Font]]
	** [[Font Patcher]]		* [[Font Patcher]]

	Conversion and repair tools are briefly described further below. These are used in concert with bitmap editors (e.g., Gimp). Also, TGA-to-DDS image conversion may be done with the bitmap editor, or with separate tools.		Conversion and repair tools are briefly described further below. These are used in concert with bitmap editors (e.g., Gimp). Also, TGA-to-DDS image conversion may be done with the bitmap editor, or with separate tools.

	== Fidcal's Original Take ==		== Fidcal's Original Take ==

Geep: Add intro

2024-03-07T17:30:33Z

Add intro

← Older revision		Revision as of 17:30, 7 March 2024
Line 2:		Line 2:

	__TOC__		__TOC__
			== Introduction ==
			Suppose you wished to add a new font to TDM. You could build it either from scratch, or by modifying an existing font. That building could be done with direct metrics+bitmap editing.

	~~As of 2024~~, ~~there are four tools for TDM~~ font conversion ~~and repair:~~		Alternatively, you could start with a new or existing TrueType Font. For fresh creation or modification within the TrueType world, a font editor (e.g., FontForge) would be needed.
			Once the .ttf file is in hand, conversion tools create a draft of the required metrics+bitmap files.

			With either approach, you should expect font completion to have a "long tail" of further "repair", particularly for non-ASCII characters.
			As of 2024, there are four tools of note:

			=== For conversions ===
			...from a TrueType font to TDM bitmaps (in .tga/.dds files) and metrics (in .dat binary files):
	* [[ExportFontToDoom3]]		* [[ExportFontToDoom3]]
	* [[Q3Font]]		* [[Q3Font]]
	* [[Refont]] - New in 2024
	* [[Font Patcher]]		=== For repair of TDM metrics ===
			** [[Refont]] - New in 2024
			** [[Q3Font]]
			** [[Font Patcher]]

			Conversion and repair tools are briefly described further below. These are used in concert with bitmap editors (e.g., Gimp). Also, TGA-to-DDS image conversion may be done with the bitmap editor, or with separate tools.

	== Fidcal's Original Take ==		== Fidcal's Original Take ==

Geep: Replace old WebLinks section with new For More

2024-03-06T16:32:04Z

Replace old WebLinks section with new For More

← Older revision		Revision as of 16:32, 6 March 2024
Line 5:		Line 5:
	As of 2024, there are four tools for TDM font conversion and repair:		As of 2024, there are four tools for TDM font conversion and repair:

	* [[~~ExportFontToDoom~~]] ~~(ARTICLE COMING SOON)~~		* [[ExportFontToDoom3]]
	* [[Q3Font]]		* [[Q3Font]]
	* [[Refont]] - New in 2024		* [[Refont]] - New in 2024
Line 11:		Line 11:

	== Fidcal's Original Take ==		== Fidcal's Original Take ==
	These are some rough notes about converting ttf fonts to doom3 and repairing if necessary.		These are some rough notes ''[from 2009]'' about converting ttf fonts to doom3 and repairing if necessary.

	My understanding is that ''~~ExportFontToDoom~~'' is more suitable than Q3Font for converting. It is what I used to convert a lot of TTF fonts. See notes with that tool as to how use it. But be aware of copyright issues if converting TTF fonts.		My understanding is that ''ExportFontToDoom3'' is more suitable than Q3Font for converting. It is what I used to convert a lot of TTF fonts. See notes with that tool as to how use it. But be aware of copyright issues if converting TTF fonts.

	With ''~~ExportFontToDoom~~'' there were quite a few spacing errors. ''Q3Font'' I found a bit puzzling so never did any conversions (it may be better for all I know.) '''BUT''' it can convert the dat files to readables for editing and back again so I used Q3Font to fix the errors.		With ''ExportFontToDoom3'' there were quite a few spacing errors. ''Q3Font'' I found a bit puzzling so never did any conversions (it may be better for all I know.) '''BUT''' it can convert the dat files to readables for editing and back again so I used Q3Font to fix the errors.

			''Geep adds: Check out newer Font Patcher and Refont to fix errors too.''

	Doom fonts have multiple dat files for each size. However, only the following are loaded by the code:		Doom fonts have multiple dat files for each size. However, only the following are loaded by the code:
Line 24:		Line 26:

	The size 24 is used mostly by readables, while the menu uses 48 (the big headlines and the main menu) and 24 (settings and other headlines).		The size 24 is used mostly by readables, while the menu uses 48 (the big headlines and the main menu) and 24 (settings and other headlines).

	This means it is not necessary to create other sizes, as these will be ignored, anyway.		This means it is not necessary to create other sizes, as these will be ignored, anyway.

	~~== Further Thoughts and Updates ==~~		''Geep adds: Size 48 is also used for titles of some readables, like those Stone font. The subtitle system as of TDM 2.12 uses Stone size 24, with (at render time) horizontal compression.''
	* Usage of ~~font sizes. Some~~ readables, like those ~~with the~~ Stone font~~, use 48 pt for titles~~. The subtitle system (as of TDM 2.12) uses Stone 24 pt, with (at render time) horizontal compression.
	* [[Q3Font]] is where you can find updated info about using this Windows utility program, including Fidcal'~~s simple example. (Some of this info used to be here in Font Conversion & Repair.).~~
	* [[Refont]] describes this command-line program, that handles some of Q3font'~~s functionality, but is easier to use. This new article has a detailed comparison.~~
	* [[ExportFontToDoom]] (ARTICLE COMING SOON)
	* [[Font Patcher]] has details about the font_patcher.pl utility, which is a preferred method (over Q3font) to fix and change fonts.
	* I18N (Internationalization). If you convert a Russian font, you need to move the character 0xFF to 0xB6, otherwise it will not show in the GUI or readables. See [[I18N - Charset]] for details.

	~~== Weblinks ==~~

	* [~~http:~~/~~/www~~.~~inventivedingo.com~~/~~stuff/exportfonttodoom3_modified~~.~~zip Fixed version~~ of ~~ExportFontToDoom]~~ (~~exports special chars, too~~)		== For More ==
	* [~~https://www.wolffiles~~.~~de/index~~.~~php?filebaseDEV&fid=1868 Q3Font]~~		* [[ExportFontToDoom3]] is, as Fidcal says, the recommended method, if you want to start a Doom3/TDM font project by generating from a TrueType font.
	* [~~http://www.bloodgate.com/mirrors/tdm/pub/scripts/font_patcher/~~ font_patcher.pl and examples]		* [[Q3Font]] is the traditional Windows utility program to fix Doom3/TDM fonts. Fidcal provides a simple example of using it. (Some of this info used to be here in Font Conversion & Repair; some is an update.)
	* [[~~Font Patcher~~]]		* [[Refont]] is another command-line program, new in 2024, that handles some of Q3font's functionality, but is easier to use. This article includes a detailed comparison.
	* [[I18N]]		* [[Font Patcher]] details the font_patcher.pl utility, which is a preferred method (over Q3font) to fix and change fonts. Includes links to examples.
			* [[I18N]] (Internationalization) introduces consideration for non-English languages.
			* [[I18N - Charset]] details the TDM-specific character mapping for non-English languages. For instance, if you convert a Russian font, you need to move the character 0xFF to 0xB6, otherwise it will not show in the GUI or readables.

	{{tutorial}} [[Category:Fonts]]		{{tutorial}} [[Category:Fonts]]

Geep: Start of redo. Break out Q3Font info into separate article

2024-03-05T02:00:13Z

Start of redo. Break out Q3Font info into separate article

@@ Line 1: / Line 1: @@
-These are some rough notes about converting ttf fonts to doom3 and repairing if necessary.
 __TOC__
-There are three tools:
+As of 2024, there are four tools for TDM font conversion and repair:
-* ExportFontToDoom
+* [[ExportFontToDoom]] (ARTICLE COMING SOON)
-* Q3Font [http://rfactory.org/q3font.html] (Runs also fine under ''Wine'')
+* [[Q3Font]]
 * [[Font Patcher]]
 My understanding is that ''ExportFontToDoom'' is more suitable than Q3Font for converting. It is what I used to convert a lot of TTF fonts. See notes with that tool as to how use it. But be aware of copyright issues if converting TTF fonts.
@@ Line 21: / Line 25: @@
 The size 24 is used mostly by readables, while the menu uses 48 (the big headlines and the main menu) and 24 (settings and other headlines).
-This means it is not nec. to create other sizes, as these will be ignored, anyway.
+This means it is not necessary to create other sizes, as these will be ignored, anyway.
-If you convert a russian font, you need to move the character 0xFF to 0xB6, otherwise it will not show in the GUI or readables. See [[I18N - Charset]] for details.
+== Further Thoughts and Updates ==
 == Weblinks ==

Nbohr1more: /* Weblinks */

2022-12-09T06:12:35Z

Weblinks

← Older revision		Revision as of 06:12, 9 December 2022
Line 76:		Line 76:

	* [http://www.inventivedingo.com/stuff/exportfonttodoom3_modified.zip Fixed version of ExportFontToDoom] (exports special chars, too)		* [http://www.inventivedingo.com/stuff/exportfonttodoom3_modified.zip Fixed version of ExportFontToDoom] (exports special chars, too)
	* [~~http~~://~~rfactory~~.~~org~~/~~q3font~~.~~html~~ Q3Font]		* [https://www.wolffiles.de/index.php?filebaseDEV&fid=1868 Q3Font]
	* [http://www.bloodgate.com/mirrors/tdm/pub/scripts/font_patcher/ font_patcher.pl and examples]		* [http://www.bloodgate.com/mirrors/tdm/pub/scripts/font_patcher/ font_patcher.pl and examples]
	* [[Font Patcher]]		* [[Font Patcher]]

Tels: update

2012-01-29T15:57:24Z

update

← Older revision		Revision as of 15:57, 29 January 2012
Line 13:		Line 13:
	With ''ExportFontToDoom'' there were quite a few spacing errors. ''Q3Font'' I found a bit puzzling so never did any conversions (it may be better for all I know.) '''BUT''' it can convert the dat files to readables for editing and back again so I used Q3Font to fix the errors.		With ''ExportFontToDoom'' there were quite a few spacing errors. ''Q3Font'' I found a bit puzzling so never did any conversions (it may be better for all I know.) '''BUT''' it can convert the dat files to readables for editing and back again so I used Q3Font to fix the errors.

	Doom fonts have multiple dat files for each size, ~~but sometimes not all of them~~ are ~~used~~:		Doom fonts have multiple dat files for each size. However, only the following are loaded by the code:

	* fontImage_6.dat
	* fontImage_8.dat
	* fontImage_12.dat		* fontImage_12.dat
	* fontImage_24.dat		* fontImage_24.dat
Line 22:		Line 20:

	The size 24 is used mostly by readables, while the menu uses 48 (the big headlines and the main menu) and 24 (settings and other headlines).		The size 24 is used mostly by readables, while the menu uses 48 (the big headlines and the main menu) and 24 (settings and other headlines).

			This means it is not nec. to create other sizes, as these will be ignored, anyway.

	== q3font ==		== q3font ==
Line 67:		Line 67:
	== font_patcher.pl ==		== font_patcher.pl ==

	Please see the [[Font Patcher\|main article]].		The prefered method to fix and change fonts is via the font patcher utility. Please see the [[Font Patcher\|main article]] for details.

	== I18N (Internationalization) ==		== I18N (Internationalization) ==

	If you convert a russian font, you need to move the character 0xFF to 0xB6, otherwise it will not show in the GUI or readables. See [[I18N]] for details.		If you convert a russian font, you need to move the character 0xFF to 0xB6, otherwise it will not show in the GUI or readables. See [[I18N - Charset]] for details.

	== Weblinks ==		== Weblinks ==
Line 78:		Line 78:
	* [http://rfactory.org/q3font.html Q3Font]		* [http://rfactory.org/q3font.html Q3Font]
	* [http://www.bloodgate.com/mirrors/tdm/pub/scripts/font_patcher/ font_patcher.pl and examples]		* [http://www.bloodgate.com/mirrors/tdm/pub/scripts/font_patcher/ font_patcher.pl and examples]
			* [[Font Patcher]]
	* [[I18N]]		* [[I18N]]

	{{tutorial}} [[Category:Fonts]]		{{tutorial}} [[Category:Fonts]]