TLG Beta Code vs. Unicode FAQ - Revision history

DarcyKrasne: added to Typography category

2026-06-29T20:17:24Z

added to Typography category

← Older revision		Revision as of 21:17, 29 June 2026
Line 20:		Line 20:
	[[Category:FAQ]]		[[Category:FAQ]]
	[[Category:Unicode]]		[[Category:Unicode]]
			[[category:Typography]]

GabrielBodard: heads

2016-02-25T10:59:08Z

heads

← Older revision		Revision as of 11:59, 25 February 2016
Line 1:		Line 1:
	~~=Beta Code vs. Unicode FAQ=~~

	==Should I use TLG betacode or Unicode for polytonic classical Greek in my electronic publications?==		==Should I use TLG betacode or Unicode for polytonic classical Greek in my electronic publications?==

	Some practical considerations one hears quoted for both sides of this debate. (Thanks, Ross. All comments/additions welcome.)		Some practical considerations one hears quoted for both sides of this debate. (Thanks, Ross. All comments/additions welcome.)

	==Arguments one hears for coding polytonic classical Greek with TLG Beta Code even today in new ~~e-pubs~~:==		===Arguments one hears for coding polytonic classical Greek with TLG Beta Code even today in new electronic publications:===

	# Unicode conflates the idea of "character" and "glyph", treating an alpha+acute as a different letter from an alpha+grave, and a terminal sigma as different from a medial sigma.		# Unicode conflates the idea of "character" and "glyph", treating an alpha+acute as a different letter from an alpha+grave, and a terminal sigma as different from a medial sigma.
Line 11:		Line 9:
	# There are symbols defined in Beta Code but not yet defined in Unicode, and symbols defined in both, but with no font support in Unicode (but this is a problem either way).		# There are symbols defined in Beta Code but not yet defined in Unicode, and symbols defined in both, but with no font support in Unicode (but this is a problem either way).

	==Arguments one hears for coding polytonic classical Greek with Unicode in new ~~e-pubs~~:==		===Arguments one hears for coding polytonic classical Greek with Unicode in new electronic publications:===

	# Unicode ''is'' an international standard.		# Unicode ''is'' an international standard.

GabrielBodard: GabrielBodard moved page Greek Fonts (TLG Beta Code vs. Unicode) to TLG Beta Code vs. Unicode FAQ: more meaningful title

2016-02-25T10:58:15Z

GabrielBodard moved page Greek Fonts (TLG Beta Code vs. Unicode) to TLG Beta Code vs. Unicode FAQ: more meaningful title

← Older revision	Revision as of 11:58, 25 February 2016
(No difference)

GabrielBodard: heads

2016-01-13T18:14:23Z

heads

← Older revision		Revision as of 19:14, 13 January 2016
Line 1:		Line 1:
	=== Should I use TLG betacode or Unicode for polytonic classical Greek in my electronic publications? ===		=Beta Code vs. Unicode FAQ=

			==Should I use TLG betacode or Unicode for polytonic classical Greek in my electronic publications?==

	Some practical considerations one hears quoted for both sides of this debate. (Thanks, Ross. All comments/additions welcome.)		Some practical considerations one hears quoted for both sides of this debate. (Thanks, Ross. All comments/additions welcome.)

	=== Arguments one hears for coding polytonic classical Greek with TLG Beta Code even today in new e-pubs: ===		==Arguments one hears for coding polytonic classical Greek with TLG Beta Code even today in new e-pubs:==

	# Unicode conflates the idea of "character" and "glyph", treating an alpha+acute as a different letter from an alpha+grave, and a terminal sigma as different from a medial sigma.		# Unicode conflates the idea of "character" and "glyph", treating an alpha+acute as a different letter from an alpha+grave, and a terminal sigma as different from a medial sigma.
Line 9:		Line 11:
	# There are symbols defined in Beta Code but not yet defined in Unicode, and symbols defined in both, but with no font support in Unicode (but this is a problem either way).		# There are symbols defined in Beta Code but not yet defined in Unicode, and symbols defined in both, but with no font support in Unicode (but this is a problem either way).

	=== Arguments one hears for coding polytonic classical Greek with Unicode in new e-pubs: ===		==Arguments one hears for coding polytonic classical Greek with Unicode in new e-pubs:==

	# Unicode ''is'' an international standard.		# Unicode ''is'' an international standard.

GabrielBodard: cat

2006-11-13T11:39:03Z

cat

← Older revision		Revision as of 12:39, 13 November 2006
Line 19:		Line 19:

	[[Category:FAQ]]		[[Category:FAQ]]
			[[Category:Unicode]]

GabrielBodard: Should I use TLG Beta Code or Unicode moved to Greek Fonts (TLG Beta Code vs. Unicode)

2006-11-13T11:38:38Z

Should I use TLG Beta Code or Unicode moved to Greek Fonts (TLG Beta Code vs. Unicode)

← Older revision	Revision as of 12:38, 13 November 2006
(No difference)

GabrielBodard: Should I use TLG Beta Code or Unicode? moved to Should I use TLG Beta Code or Unicode

2006-11-06T12:02:50Z

Should I use TLG Beta Code or Unicode? moved to Should I use TLG Beta Code or Unicode

← Older revision	Revision as of 13:02, 6 November 2006
(No difference)

GabrielBodard: BetaCode moved to Should I use TLG Beta Code or Unicode?

2006-11-06T11:40:28Z

BetaCode moved to Should I use TLG Beta Code or Unicode?

← Older revision	Revision as of 12:40, 6 November 2006
(No difference)

GabrielBodard: cat

2006-11-06T11:39:31Z

cat

← Older revision		Revision as of 12:39, 6 November 2006
Line 16:		Line 16:
	# By virtue of the transcoder and other conversion methods out there, we can always go ''back'' to Beta Code, on the fly, when it is necessary.		# By virtue of the transcoder and other conversion methods out there, we can always go ''back'' to Beta Code, on the fly, when it is necessary.
	# Beta code, by using punctuation marks in non-standard ways, requires a rewrite of any tokenizer (e.g. you can't count on ")" to follow the end of a word); this requires some extra programming in some instances.		# Beta code, by using punctuation marks in non-standard ways, requires a rewrite of any tokenizer (e.g. you can't count on ")" to follow the end of a word); this requires some extra programming in some instances.


			[[Category:FAQ]]

Sysadmin: Imported from xwiki

2006-10-05T13:39:33Z

Imported from xwiki

New page

=== Should I use TLG betacode or Unicode for polytonic classical Greek in my electronic publications? ===

Some practical considerations one hears quoted for both sides of this debate. (Thanks, Ross. All comments/additions welcome.)

=== Arguments one hears for coding polytonic classical Greek with TLG Beta Code even today in new e-pubs: ===

# Unicode conflates the idea of "character" and "glyph", treating an alpha+acute as a different letter from an alpha+grave, and a terminal sigma as different from a medial sigma.
# Morpheus (Perseus morphological parser, aka cruncher) needs Beta Code input.
# There are symbols defined in Beta Code but not yet defined in Unicode, and symbols defined in both, but with no font support in Unicode (but this is a problem either way).

=== Arguments one hears for coding polytonic classical Greek with Unicode in new e-pubs: ===

# Unicode ''is'' an international standard.
# It sucks to have to implement a transcoder vel sim. in an already hairy process off setting up tomcat/cocoon or other on-the-fly publication framework.
# If you offer your XML source files for download, and the Greek is TLG B C, people can't read them easily, without conversion.
# By virtue of the transcoder and other conversion methods out there, we can always go ''back'' to Beta Code, on the fly, when it is necessary.
# Beta code, by using punctuation marks in non-standard ways, requires a rewrite of any tokenizer (e.g. you can't count on ")" to follow the end of a word); this requires some extra programming in some instances.