Refont - Revision history

Geep: /* Downloads */ Add comments about 2.7, 2.8 improvements

2026-03-21T22:16:13Z

Downloads: Add comments about 2.7, 2.8 improvements

← Older revision		Revision as of 22:16, 21 March 2026
Line 424:		Line 424:
	== Downloads ==		== Downloads ==
	Release 2.8 of March 19, 2026:		Release 2.8 of March 19, 2026:
			* Supports partial coverage regeneration (i.e., unicodeMap with not all 256 represented) by ExportUnicodeFontToDoom3.
			* With 512x512 bitmaps, suppresses scaling warnings if scaled by "half", now +/- 1 pixel.
	* [https://drive.google.com/file/d/1BHGkCOhgXP7bFp1mXyfgoRBUtqkbCVRb/view?usp=sharing refont.exe]		* [https://drive.google.com/file/d/1BHGkCOhgXP7bFp1mXyfgoRBUtqkbCVRb/view?usp=sharing refont.exe]
	* [https://drive.google.com/file/d/1Cca_Xo3W5jYB_40RVo4aIPHAGIufA9V0/view?usp=sharing refont_source_v2.8.zip, with refont.cpp, refont.sln, open-source license]		* [https://drive.google.com/file/d/1Cca_Xo3W5jYB_40RVo4aIPHAGIufA9V0/view?usp=sharing refont_source_v2.8.zip, with refont.cpp, refont.sln, open-source license]

			Version 2.7: Fixes poor detection of _<n>_ pattern in shadername, and allow <n> to be 1 or 2 digits, not just 1.

	Release 2.6 of July 28, 2025:		Release 2.6 of July 28, 2025:

Geep: /* Downloads */ v 2.8 released

2026-03-19T17:46:28Z

Downloads: v 2.8 released

← Older revision		Revision as of 17:46, 19 March 2026
Line 423:		Line 423:

	== Downloads ==		== Downloads ==
			Release 2.8 of March 19, 2026:
			* [https://drive.google.com/file/d/1BHGkCOhgXP7bFp1mXyfgoRBUtqkbCVRb/view?usp=sharing refont.exe]
			* [https://drive.google.com/file/d/1Cca_Xo3W5jYB_40RVo4aIPHAGIufA9V0/view?usp=sharing refont_source_v2.8.zip, with refont.cpp, refont.sln, open-source license]

	Release 2.6 of July 28, 2025:		Release 2.6 of July 28, 2025:
	* [https://drive.google.com/file/d/1ABf4771Jr1C1hKbLx4xWq8lx8Kn7HdKP/view?usp=sharing refont.exe]		* [https://drive.google.com/file/d/1ABf4771Jr1C1hKbLx4xWq8lx8Kn7HdKP/view?usp=sharing refont.exe]

Geep: /* Special Handling of Fonts with 512x512 Bitmaps */ v2.8 adds 1-pixel slack, suppress warnings

2026-03-18T17:25:03Z

Special Handling of Fonts with 512x512 Bitmaps: v2.8 adds 1-pixel slack, suppress warnings

← Older revision		Revision as of 17:25, 18 March 2026
Line 326:		Line 326:
	* in the case of Mason, have larger ASCII alphanumeric glyphs that would render with crisper edges.		* in the case of Mason, have larger ASCII alphanumeric glyphs that would render with crisper edges.

	In either case, the font characters when rendered in, say, the game main menu will be the same size as if from 256x256. This is because the imageWidth and ~~imageHeight~~ metrics are not doubled.		In either case, the font characters when rendered in, say, the game main menu will be the same size as if from 256x256. This is because the imageWidth, imageHeight, height, and top metrics are not doubled.
	In effect, a scaling by half is requested for all characters in the DAT file and applied by the engine.		In effect, a scaling by half (approximately, as constrained by integer values) is requested for all characters in the DAT file and applied by the engine.

	=== When generating a REF file from a DAT file ===		=== When generating a REF file from a DAT file ===
Line 346:		Line 346:
	* Values for coord_s, coord_s2, coord_t, and coord_t2 will have a normal range of 0-512 when appropriate. [COMING SOON: Those values may then be read properly by datBounds.].		* Values for coord_s, coord_s2, coord_t, and coord_t2 will have a normal range of 0-512 when appropriate. [COMING SOON: Those values may then be read properly by datBounds.].
	* Any warnings expressed (within the file or within the command-line window) will be in terms of the correct range of values.		* Any warnings expressed (within the file or within the command-line window) will be in terms of the correct range of values.
	* Warning checks will expect a scaling by half for all characters. That is, while 512... requires scaling down by half, that scaling will not generate a warning (unless it's not EXACTLY by half), so the -scaling_ok option is not needed just for the exactly-by-half scaling.		* Warning checks will expect a scaling by half for all characters. That is, while 512... requires scaling down by half, that scaling will not generate a warning (unless it's not EXACTLY by half, or within 1 pixel of that), so the -scaling_ok option is not needed just for the exactly-by-half scaling.

	=== When generating a DAT file from a REF file ===		=== When generating a DAT file from a REF file ===

Geep: /* Post-Read MAJOR Warnings about REF, FNT, and DAT Input Values */

2026-03-18T17:18:00Z

Post-Read MAJOR Warnings about REF, FNT, and DAT Input Values

← Older revision		Revision as of 17:18, 18 March 2026
Line 269:		Line 269:
	** imageHeight == coord_t2 - coord_t?		** imageHeight == coord_t2 - coord_t?

	~~''Suppressing Warnings Due to Scaling.'' The~~ last two "Inconsistent Metrics" criteria ~~will not be true~~ if there is per-character scaling. (Only TDM’s mason and mason-glow use per-character scaling, specifically for all upper-case characters.) ~~In such~~ a ~~case~~, to ~~avoid generating a lot~~ of ~~useless major warnings, use~~ the refont ~~option "~~-~~scaling_ok"~~.		However, warnings about those last two "Inconsistent Metrics" criteria are suppressed if:
			* you use refont's "-scaling_ok" option. This is helpful when there is extensive per-character scaling. (Only TDM’s mason and mason-glow use a lot of per-character scaling, specifically for all upper-case characters.)
			* you have a 512x512 bitmap, where throughout, the imageWidth and imageHeight (and some other metrics) are expected to be scaled to "half" of the corresponding coord difference. As of refont 2.8, 1 pixel of wiggle-room is allowed for integer rounding. Only warnings will be issued that fail these checks:
			** abs(imageWidth * 2 - (coord_s2 - coord_s)) > 1
			** abs(imageHeight * 2 - (coord_t2 - coord_t)) > 1

	===Post-Read MINOR Warnings for FNT’s and DAT’s s, t, s2, t2===		===Post-Read MINOR Warnings for FNT’s and DAT’s s, t, s2, t2===
	''Low Precision.'' This value, when multiplied by 256.0, should be exactly an integer. However, some generation or revision procedure (e.g., Q3Font’s DAT  FNT  DAT) may have not used sufficient precision to ensure this. An offset from an integer value of less than +/- 0.001 is considered a minor problem; otherwise, major as above.		''Low Precision.'' This value, when multiplied by 256.0, should be exactly an integer. However, some generation or revision procedure (e.g., Q3Font’s DAT  FNT  DAT) may have not used sufficient precision to ensure this. An offset from an integer value of less than +/- 0.001 is considered a minor problem; otherwise, major as above.

Geep: /* Downloads */ release 2.6. Link contents refreshed

2025-07-28T20:03:08Z

Downloads: release 2.6. Link contents refreshed

← Older revision		Revision as of 20:03, 28 July 2025
Line 418:		Line 418:

	== Downloads ==		== Downloads ==
	Release 2.5 of ~~December 12~~, ~~2024~~:		Release 2.6 of July 28, 2025:
	* [https://drive.google.com/file/d/1ABf4771Jr1C1hKbLx4xWq8lx8Kn7HdKP/view?usp=sharing refont.exe]		* [https://drive.google.com/file/d/1ABf4771Jr1C1hKbLx4xWq8lx8Kn7HdKP/view?usp=sharing refont.exe]
	* [https://drive.google.com/file/d/1-k68eo0CHKZ-sM7JGP05axm49cc5De0T/view?usp=sharing source code: refont.cpp]		* [https://drive.google.com/file/d/1-k68eo0CHKZ-sM7JGP05axm49cc5De0T/view?usp=sharing source code: refont.cpp]

Geep: /* Generated Within-REF Comments during Output */

2024-12-16T22:36:56Z

Generated Within-REF Comments during Output

← Older revision		Revision as of 22:36, 16 December 2024
Line 305:		Line 305:
	''Coverage of Generated Within-REF Comments.'' A calculated value of coord_s, coord_t, coord_s2, or coord_t2 would have been flagged as a “Major Warning” during read if:		''Coverage of Generated Within-REF Comments.'' A calculated value of coord_s, coord_t, coord_s2, or coord_t2 would have been flagged as a “Major Warning” during read if:
	* the discrepancy from being an integer was non-trivial (+/- 0.001 or more), or		* the discrepancy from being an integer was non-trivial (+/- 0.001 or more), or
	* the calculated and rounded integer is outside the range 0-256.		* the calculated and rounded integer is outside the range given by bitmap size, e.g., 0-256.

	For these, a comment is generated. Other causes are:		For these, a comment is generated. Other causes are:
	* Integer Out of Range 0-256. For height, top, bottom, pitch, xSkip, imageWidth, imageHeight.		* Integer Out of Range 0-256 ''(or 0-512 as applicable)''. For height, top, bottom, pitch, xSkip, imageWidth, imageHeight.
	* Integer Non Zero. For glyph.		* Integer Non Zero. For glyph.
	* Float Less Than Zero. For glyphScale (which is independent of a particular character).		* Float Less Than Zero. For glyphScale (which is independent of a particular character).

Geep: /* When Editing */

2024-12-16T22:33:19Z

When Editing

← Older revision		Revision as of 22:33, 16 December 2024
Line 109:		Line 109:
	== When Editing ==		== When Editing ==
	Refont has a minimal parser. To keep it happy, preserve the file's line structure. In particular:		Refont has a minimal parser. To keep it happy, preserve the file's line structure. In particular:
	* every REF and FNT file has the same number of lines.		* every REF and FNT file has the same number of lines. ''(Exception: REF may have additional starting lines to flag 512x512 bitmaps, discussed below. Generally, you won't edit these.)''
	* all keywords within a block must be present, and in a particular order.		* all keywords within a block must be present, and in a particular order.
	* each block must have exactly the same number of lines (except for the special one at the end).		* each block must have exactly the same number of lines (except for the special one at the end).

	The meaning of the font metrics are explained in [[Font_Metrics_%26_DAT_File_Format]]. The [[Q3Font]] article has an example of simple metric editing that is also pertinent to refont.		The meaning of the font metrics are explained in [[Font_Metrics_%26_DAT_File_Format]]. The [[Q3Font]] article has an example of simple metric editing that is also pertinent to refont.

	== To Move Changed FNT or REF Data Back to a DAT ==		== To Move Changed FNT or REF Data Back to a DAT ==

Geep: /* As a REF File */

2024-12-16T22:29:22Z

As a REF File

← Older revision		Revision as of 22:29, 16 December 2024
Line 76:		Line 76:

	=== As a REF File ===		=== As a REF File ===
	'''Starting with Refont v2.5, a mixture of 256x256 and 512x512 bitmap shaders, encountered with Carleton and Mason family fonts, can be handled. See further below.'''		''Starting with Refont v2.5, a mixture of 256x256 and 512x512 bitmap shaders, encountered with Carleton and Mason family fonts, can be handled. See further below.''

	To create a refont-specific "<dat-name>.ref" file:		To create a refont-specific "<dat-name>.ref" file:
Line 105:		Line 105:
	...		...

	Items bolded differ from FNT format. The starting line expresses the value in hex. And rather than s, t, s2, t2 in fractional [0...1] floating point, the "coord_..." values are expressed (and editable) as integer coordinates of the bitmap, with a range reflecting bitmap size. The default TDM bitmap size is 256x256, but a few fonts use 512x512 and require special treatment discussed further below.		Items bolded differ from FNT format. The starting line expresses the value in hex. And rather than s, t, s2, t2 in fractional [0...1] floating point, the "coord_..." values are expressed (and editable) as integer coordinates of the bitmap, with a range reflecting bitmap size. The default TDM bitmap size is 256x256, but a few fonts use 512x512 and require special treatment discussed further below.

	== When Editing ==		== When Editing ==

Geep: Finish v2.5 update. More revision of 512 section. stats & links too

2024-12-16T22:28:00Z

Finish v2.5 update. More revision of 512 section. stats & links too

← Older revision		Revision as of 22:28, 16 December 2024
Line 1:		Line 1:
	''By Geep, 2024, and similar to the article about Q3Font.''		''By Geep, 2024, and similar to the article about Q3Font.''

	~~As of~~ 2024, the ~~new~~ "refont" command-line utility allows inspection and alteration of [[Font Metrics & DAT File Format \| font metrics]].		Introduced in 2024, the "refont" command-line utility allows inspection and alteration of [[Font Metrics & DAT File Format \| font metrics]].
	It is designed to be an easier-to-use version of the inspection/alteration ~~parts~~ of [[Q3Font]].		It is designed to be an easier-to-use version of the inspection/alteration functionalities of [[Q3Font]].
	It also provides a font analysis feature.		It also provides a font analysis feature.

Line 313:		Line 313:

	''Major Warnings that Don’t Cause Within-REF Comments.'' Currently, this is limited to “Inconsistent Metrics”, which would probably require tagging on multiple lines.		''Major Warnings that Don’t Cause Within-REF Comments.'' Currently, this is limited to “Inconsistent Metrics”, which would probably require tagging on multiple lines.

	== Special Handling of Fonts with 512x512 Bitmaps ==		== Special Handling of Fonts with 512x512 Bitmaps ==
	Some DAT files reference bitmap shaders where some or all are of size 512x512, instead of the default 256x256. Refont v2.5+ can support this (replacing an insufficient first attempt in v2.4).		Some DAT files reference bitmap shaders where some or all are of size 512x512, instead of the default 256x256. Refont v2.5+ can support this (replacing an insufficient first attempt in v2.4).

			Font developers went to double-sized bitmaps to:
			* in the case of Carleton, allow freehand drawing of missing European characters, which could be drawn more easily if twice standard size.
			* in the case of Mason, have larger ASCII alphanumeric glyphs that would render with crisper edges.

			In either case, the font characters when rendered in, say, the game main menu will be the same size as if from 256x256. This is because the imageWidth and imageHeight metrics are not doubled.
			In effect, a scaling by half is requested for all characters in the DAT file and applied by the engine.

	=== When generating a REF file from a DAT file ===		=== When generating a REF file from a DAT file ===
Line 329:		Line 337:

	* There will be a one or more starting lines like:		* There will be a one or more starting lines like:
	# bitmap_<n>_size=512 ''(Refont will look for this if doing a subsequent compile to DAT)''		# bitmap_<n>_size=512 ''(Refont will look for this if doing a subsequent compile to DAT)''
	* If you specified the short form, it will expand to just the right number of starting lines.		* If you specified the short form, it will expand to just the right number of starting lines.
	* Values for coord_s, coord_s2, coord_t, and coord_t2 will have a normal range of 0-512 when appropriate. [COMING SOON: Those values may then be read properly by datBounds.].		* Values for coord_s, coord_s2, coord_t, and coord_t2 will have a normal range of 0-512 when appropriate. [COMING SOON: Those values may then be read properly by datBounds.].
	* Any warnings expressed (within the file or within the command-line window) will be in terms of the correct range of values.		* Any warnings expressed (within the file or within the command-line window) will be in terms of the correct range of values.
	* ~~[NEED TO CLARIFY:]~~Warning checks will expect a scaling by half. That is, while 512 requires scaling down by half, that scaling will not generate a warning (unless it's not EXACTLY by half), so the -scaling_ok option is not needed just for the exactly-by-half scaling.		* Warning checks will expect a scaling by half for all characters. That is, while 512... requires scaling down by half, that scaling will not generate a warning (unless it's not EXACTLY by half), so the -scaling_ok option is not needed just for the exactly-by-half scaling.

	=== When generating a DAT file from a REF file ===		=== When generating a DAT file from a REF file ===
Line 339:		Line 347:
	During refont -compile, no special command line options are needed. Instead, REF's starting lines of form "# bitmap_<n>_size=512" are inspected and coord ranges will be interpreted as 0-512 whenever appropriate.		During refont -compile, no special command line options are needed. Instead, REF's starting lines of form "# bitmap_<n>_size=512" are inspected and coord ranges will be interpreted as 0-512 whenever appropriate.

	=== Special Handling Recommendations for ~~Certain~~ Carleton and Mason ~~Fonts~~ ===		=== Special Handling Recommendations for Carleton and Mason ===
			''For fonts shipped with TDM 2.12 in tdm_fonts01.pk4. Illustrative command paths are shown; adjust to your working copy.''
	==== Mason Family ====		==== Mason Family ====
	Mason uses within-DAT per-character scaling, as well as some ~~larger~~ bitmaps.		The [[Mason Font]] uses within-DAT per-character scaling, as well as some but not all 512x512 bitmaps. Only 48pt Mason is shipped.

	Because ~~tdm_fonts01~~/dds/fonts/english/mason/masonalternate_0_48.dds to _2_ are 512x512, but _3_ to _5_ are not, use:		Because, under /dds/fonts/english/mason/, bitmaps masonalternate_0_48.dds to _2_ are 512x512, but _3_ to _5_ are not, use:

	-decompile mason/fontimage_48.dat -512_0 -512_1 -512_2 -scaling_ok		-decompile /fonts/english/mason/fontimage_48.dat -512_0 -512_1 -512_2 -scaling_ok

	Because ~~tdm_fonts01~~/dds/fonts/english/mason_glow/masonalternate_1_48.dds and _2_ are 512x512, but _0_ and _3_ to _5_ are not, use:		Because, under /dds/fonts/english/mason_glow/, bitmaps masonalternate_1_48.dds and _2_ are 512x512, but _0_ and _3_ to _5_ are not, use:

	-decompile mason_glow/fontimage_48.dat -512_1 -512_2 -scaling_ok		-decompile /fonts/english/mason_glow/fontimage_48.dat -512_1 -512_2 -scaling_ok

	Russian versions use the default ~~256~~. [These possibly benefit from -scaling_ok; didn't investigate.]		Russian versions use the default 256x256. [These possibly benefit from -scaling_ok; didn't investigate.]
	==== Carleton Family ====		==== Carleton Family ====
	The ~~current 24 pt sizes~~ of carleton ~~and carleton_bold (but not other sizes, nor carleton_glow or carleton_condensed) are special cases.~~		The 24pt size of carleton has two bitmaps under /dds/fonts/english/carleton/, namely carleton_0_24.dds and _1_, both of size 512x512. So use:
	~~For these~~ fonts, ~~files fontimage_0_24~~.dds and ~~fontimage_1_24.dds have 512x512 bitmaps~~, ~~instead~~ of ~~256x256. (BTW, those pair of bitmaps are identical for carleton and carleton_bold.)~~
	~~The double-sized bitmap was evidently chosen in the past to allow freehand drawing of double-sized characters, to which scaling by half is requested in the DAT file and applied by the engine~~.

	-decompile ~~tdm_fonts01~~/fonts/english/carleton/fontimage_24.dat -512_0 -512_1 or ~~carleton_24.dat -512~~		-decompile /fonts/english/carleton/fontimage_24.dat -512_0 -512_1
	-decompile ~~tdm_fonts01~~/fonts/english/~~carleton_bold~~/fontimage_24.dat -~~512_0 -512_1~~ ~~or carletonbold_24.dat -512~~		''or''
			-decompile /fonts/english/carleton/fontimage_24.dat -512

			The 24pt size of carleton_bold has bitmaps with identical content to carleton's, so use the same options:

	~~Sizes 12 & 48~~ use the default ~~256~~ bitmaps.		-decompile /fonts/english/carleton_bold/fontimage_24.dat -512_0 -512_1
	~~Fonts~~ carleton_condensed and carleton_glow ~~use the default 256 bitmaps~~.		''or''
	(It is not required the base & glow have identical bitmap sizes.)		-decompile /fonts/english/carleton_bold/fontimage_24.dat -512
	Russian versions ~~use the default 256 bitmaps~~
			Other members of this family use the default 256x256 bitmaps:
			* Sizes 12pt & 48pt
			* carleton_condensed and carleton_glow. (Note: while helpful, it is not required that the base & glow have identical bitmap sizes.)
			* Russian versions

	==== These Fonts with Stats ====		==== These Fonts with Stats ====
	With -stats, ~~when~~ reading a DAT file, you may use the -512... and scaling_ok options to be most correct, although neglecting to specify them will likely have no significant impact on the analytical results.		With -stats discussed next, if reading a DAT file, you may use the -512... and scaling_ok options to be most correct, although neglecting to specify them will likely have no significant impact on the analytical results. If reading a REF file, the included "# bitmap_..." lines will take care of that for you.

	== For Statistics on Unimplemented or Problematic Font Characters ==		== For Statistics on Unimplemented or Problematic Font Characters ==
	~~'''CAUTION:''' Base an analysis of the Mason 48pt font on the DAT file rather than a currently-problematic REF file.~~

	DAT or (as of v2.3) REF file analysis here is primarily designed to benefit english/european fonts. It will use the optional annotation file if provided. Syntax:		DAT or (as of v2.3) REF file analysis here is primarily designed to benefit english/european fonts. It will use the optional annotation file if provided. Syntax:

Line 406:		Line 418:

	== Downloads ==		== Downloads ==
	Release 2.4 of ~~November 11~~, 2024:		Release 2.5 of December 12, 2024:
	* [https://drive.google.com/file/d/1ABf4771Jr1C1hKbLx4xWq8lx8Kn7HdKP/view?usp=sharing refont.exe]		* [https://drive.google.com/file/d/1ABf4771Jr1C1hKbLx4xWq8lx8Kn7HdKP/view?usp=sharing refont.exe]
	* [https://drive.google.com/file/d/1-k68eo0CHKZ-sM7JGP05axm49cc5De0T/view?usp=sharing source code: refont.cpp]		* [https://drive.google.com/file/d/1-k68eo0CHKZ-sM7JGP05axm49cc5De0T/view?usp=sharing source code: refont.cpp]
Line 429:		Line 441:
	== For More ==		== For More ==
	* See the [https://forums.thedarkmod.com/index.php?/topic/22427-analysis-of-212-tdm-fonts/ summary analysis of 2.12 TDM fonts], based on applying 'refont -stats ...' to all 'english' DAT files.		* See the [https://forums.thedarkmod.com/index.php?/topic/22427-analysis-of-212-tdm-fonts/ summary analysis of 2.12 TDM fonts], based on applying 'refont -stats ...' to all 'english' DAT files.
	* [[Mason Font]]

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

Geep: Revise special handling section

2024-12-16T19:01:28Z

Revise special handling section

← Older revision		Revision as of 19:01, 16 December 2024
Line 7:		Line 7:
	== Comparison with Font Patcher ==		== Comparison with Font Patcher ==

	Refont can be seen as complementary to [[Font Patcher]]. The latter has additional features that may be better if planning a wholesale rearrangement or expansion of characters within a bitmap. But Font Patcher requires installation of Perl, while refont.exe is more drop and go.		Refont can be seen as complementary to [[Font Patcher]]. The latter has additional features that may be better if planning a wholesale rearrangement or expansion of characters within a bitmap, particularly for a new font immediately after conversion from a TTF font. But refont is easier to use in later years, and Font Patcher requires installation of Perl, while refont.exe is more drop and go.

	== Comparison with Q3Font ==		== Comparison with Q3Font ==

	For metric alteration, q3font has a native "*.fnt" human-readable format, and supports DAT <==> FNT conversions. For ~~compatability~~, so does refont.		For metric alteration, q3font has a native "*.fnt" human-readable format, and supports DAT <==> FNT conversions. For compatibility, so does refont.

	=== Advantages of Q3Font ===		=== Advantages of Q3Font ===
Line 24:		Line 24:
	* It's open-source, so further C++ development is possible.		* It's open-source, so further C++ development is possible.
	* It has its own native human-readable format, "*.ref", similar to .fnt but better.		* It has its own native human-readable format, "*.ref", similar to .fnt but better.
			* The REF format can be read by [[datBounds]] to generate bitmap boundary & metrics visualizations.

	The better features of REF are:		The better features of REF are:
Line 75:		Line 76:

	=== As a REF File ===		=== As a REF File ===
	'''~~CAUTION:''' The REF file format does not yet properly handle the Mason 48pt font~~, ~~due to its set~~ of ~~mixed-size~~ bitmap shaders~~. Also~~, ~~see "Special-Case~~ Carleton and ~~Carleton_bold Fonts with 512x512 Bitmaps"~~ below.		'''Starting with Refont v2.5, a mixture of 256x256 and 512x512 bitmap shaders, encountered with Carleton and Mason family fonts, can be handled. See further below.'''

	To create a refont-specific "<dat-name>.ref" file:		To create a refont-specific "<dat-name>.ref" file:
Line 338:		Line 339:
	During refont -compile, no special command line options are needed. Instead, REF's starting lines of form "# bitmap_<n>_size=512" are inspected and coord ranges will be interpreted as 0-512 whenever appropriate.		During refont -compile, no special command line options are needed. Instead, REF's starting lines of form "# bitmap_<n>_size=512" are inspected and coord ranges will be interpreted as 0-512 whenever appropriate.

	=== Special Handling ~~Needed:~~ Certain Carleton and Mason Fonts ===		=== Special Handling Recommendations for Certain Carleton and Mason Fonts ===
			==== Mason Family ====
			Mason uses within-DAT per-character scaling, as well as some larger bitmaps.

			Because tdm_fonts01/dds/fonts/english/mason/masonalternate_0_48.dds to _2_ are 512x512, but _3_ to _5_ are not, use:

			-decompile mason/fontimage_48.dat -512_0 -512_1 -512_2 -scaling_ok

			Because tdm_fonts01/dds/fonts/english/mason_glow/masonalternate_1_48.dds and _2_ are 512x512, but _0_ and _3_ to _5_ are not, use:

			-decompile mason_glow/fontimage_48.dat -512_1 -512_2 -scaling_ok

			Russian versions use the default 256. [These possibly benefit from -scaling_ok; didn't investigate.]
			==== Carleton Family ====
	The current 24 pt sizes of carleton and carleton_bold (but not other sizes, nor carleton_glow or carleton_condensed) are special cases.		The current 24 pt sizes of carleton and carleton_bold (but not other sizes, nor carleton_glow or carleton_condensed) are special cases.
	For these fonts, files fontimage_0_24.dds and fontimage_1_24.dds have 512x512 bitmaps, instead of 256x256. (BTW, those pair of bitmaps are identical for carleton and carleton_bold.)		For these fonts, files fontimage_0_24.dds and fontimage_1_24.dds have 512x512 bitmaps, instead of 256x256. (BTW, those pair of bitmaps are identical for carleton and carleton_bold.)
	The double-sized bitmap was evidently chosen in the past to allow freehand drawing of double-sized characters, to which scaling by half is requested in the DAT file and applied by the engine.		The double-sized bitmap was evidently chosen in the past to allow freehand drawing of double-sized characters, to which scaling by half is requested in the DAT file and applied by the engine.

	~~[MORE TO COME]~~		-decompile tdm_fonts01/fonts/english/carleton/fontimage_24.dat -512_0 -512_1 or carleton_24.dat -512
			-decompile tdm_fonts01/fonts/english/carleton_bold/fontimage_24.dat -512_0 -512_1 or carletonbold_24.dat -512

			Sizes 12 & 48 use the default 256 bitmaps.
			Fonts carleton_condensed and carleton_glow use the default 256 bitmaps.
			(It is not required the base & glow have identical bitmap sizes.)
			Russian versions use the default 256 bitmaps

			==== These Fonts with Stats ====
			With -stats, when reading a DAT file, you may use the -512... and scaling_ok options to be most correct, although neglecting to specify them will likely have no significant impact on the analytical results.

	== For Statistics on Unimplemented or Problematic Font Characters ==		== For Statistics on Unimplemented or Problematic Font Characters ==