Gen Lang Programs - Revision history

Geep: Add [Catalan]

2025-07-16T20:21:25Z

Add [Catalan]

← Older revision		Revision as of 20:21, 16 July 2025
Line 285:		Line 285:
	[Dutch]		[Dutch]
	[Turkish]		[Turkish]
			[Catalan]

	Case of the language name doesn't matter, nor does order in which sections are listed. But it is a convention to list English first. After the header comes a series of convertible lines and comment lines, as discussed in next sections. The last line of the file has the closing "}".		Case of the language name doesn't matter, nor does order in which sections are listed. But it is a convention to list English first. After the header comes a series of convertible lines and comment lines, as discussed in next sections. The last line of the file has the closing "}".

Geep: /* Downloads */ Add links for v1.1

2025-07-16T18:24:19Z

Downloads: Add links for v1.1

← Older revision		Revision as of 18:24, 16 July 2025
Line 340:		Line 340:
	For PLUS v1.1 of 2025, July 16 (mainly adds Catalan as a supported language)		For PLUS v1.1 of 2025, July 16 (mainly adds Catalan as a supported language)

	[~~soon~~]		* [https://drive.google.com/file/d/1R_qajkfq5_drIGEMYQ8ahpJwfN1LdkiT/view?usp=sharing gen_lang_plus_source_v1.1.zip]. This is a Visual Studio project. Includes open-source license.
			* [https://drive.google.com/file/d/1kj_zE9VN7l1DMztnOHx-UaNbIAECIE6M/view?usp=sharing gen_lang_plus.exe]

	For PLUS v1.0 of 2025, Feb 28:		For PLUS v1.0 of 2025, Feb 28:

Geep: /* Charpunts and Charpunts-Extra Options [PLUS Only] */

2025-07-16T16:48:56Z

Charpunts and Charpunts-Extra Options [PLUS Only]

← Older revision		Revision as of 16:48, 16 July 2025
Line 73:		Line 73:
	TIP: If the results of this option is too voluminous, recall that output from a console app can be directed into a file using "... > filename.txt".		TIP: If the results of this option is too voluminous, recall that output from a console app can be directed into a file using "... > filename.txt".

	These reports give the output line number within <language>.lang, rather than the input line in all.lang, because of difficulties getting the latter value ~~right~~ in the face of, for instance, multiline comments. (Any line numbers that PL reports are usually off.)		These reports give the output line number within <language>.lang, rather than the input line in all.lang, because of difficulties getting the latter value to be correct in the face of, for instance, multiline comments. (Any line numbers that PL reports are usually off.)

	== Old Preamble Option [PLUS Only] ==		== Old Preamble Option [PLUS Only] ==

Geep: Clarify use of strings folder; Get ready for v1.1 release.with Catalan

2025-07-16T16:43:51Z

Clarify use of strings folder; Get ready for v1.1 release.with Catalan

← Older revision		Revision as of 16:43, 16 July 2025
Line 1:		Line 1:
	By Geep, February 2025		By Geep, from February 2025
	== Introduction to Gen_lang.pl ("PL") and Gen_lang_plus ("PLUS") ==		== Introduction to Gen_lang.pl ("PL") and Gen_lang_plus ("PLUS") ==
	This describes two software implementations of command-line programs that essentially do the same thing;		This describes two software implementations of command-line programs that essentially do the same thing;
Line 6:		Line 6:

	The purpose of both is as follows.		The purpose of both is as follows.
	* Read an "all.lang" file, either that associated with the main-menu-system, or with a specific FM under development. This UTF-8 input file has translations of strings for all 16 TDM-supported languages. There are individual sections for each target language. Each string is of form		* Read and write files in child folder "strings". (Caution: "not strings/fm", even if you specify the "fm" option.)
			* Read an "all.lang" file, either that associated with the main-menu-system, or with a specific FM under development. This UTF-8 input file has translations of strings for all TDM-supported languages (currently 17). There are individual sections for each target language. Each string is of form

	"#str_<id>" "<string content>" // optional comment.		"#str_<id>" "<string content>" // optional comment.
Line 126:		Line 127:
	The first line of the file has the field (aka column) headers, with languages in alphabetic order:		The first line of the file has the field (aka column) headers, with languages in alphabetic order:

	ID,czech,danish,dutch,english,french,german,hungarian,italian,polish,portuguese,romanian,russian,slovak,spanish,swedish,turkish,comment		ID,catalan,czech,danish,dutch,english,french,german,hungarian,italian,polish,portuguese,romanian,russian,slovak,spanish,swedish,turkish,comment
	There are 18 comma-separated fields here, so the results is very wide. (Recall in a spreadsheet, you can hide columns not of current interest.)		There are 19 comma-separated fields here, so the results is very wide. (Recall in a spreadsheet, you can hide columns not of current interest.)

	Broadly, the .csv format comes in different variants. Traditionally, as here, comma is the separator. If a field contains a comma, the field overall is wrapped in double quotes. PL also so wraps if there's a contained double-quote, colon, or semi-colon. PLUS mimics that policy. PL unfortunately only considers the language fields for wrapping. PLUS goes a bit further, to consider the "comment" field.		Broadly, the .csv format comes in different variants. Traditionally, as here, comma is the separator. If a field contains a comma, the field overall is wrapped in double quotes. PL also so wraps if there's a contained double-quote, colon, or semi-colon. PLUS mimics that policy. PL unfortunately only considers the language fields for wrapping. PLUS goes a bit further, to consider the "comment" field.
Line 139:		Line 140:
	An example row with some empty fields, for the English word "Error", with no comment:		An example row with some empty fields, for the English word "Error", with no comment:

	#str_02000,,Fejl,,Error,Erreur,Fehler,Hiba,Errore,Błąd,Erro,Eroare,Ошибка,Chyba,,,Hata,		#str_02000,Error.,,Fejl,,Error,Erreur,Fehler,Hiba,Errore,Błąd,Erro,Eroare,Ошибка,Chyba,,,Hata,
	Comments on source lines in sections other than [english] are not included.		Comments on source lines in sections other than [english] are not included.

Line 337:		Line 338:

	== Downloads ==		== Downloads ==
			For PLUS v1.1 of 2025, July 16 (mainly adds Catalan as a supported language)

			[soon]

	For PLUS v1.0 of 2025, Feb 28:		For PLUS v1.0 of 2025, Feb 28:

Geep at 14:58, 1 March 2025

2025-03-01T14:58:15Z

← Older revision		Revision as of 14:58, 1 March 2025
Line 1:		Line 1:
	By Geep, 2025		By Geep, February 2025
	== Introduction to Gen_lang.pl ("PL") and Gen_lang_plus ("PLUS") ==		== Introduction to Gen_lang.pl ("PL") and Gen_lang_plus ("PLUS") ==
	This describes two software implementations of command-line programs that essentially do the same thing;		This describes two software implementations of command-line programs that essentially do the same thing;

Geep: /* Downloads */

2025-03-01T14:38:11Z

Downloads

← Older revision		Revision as of 14:38, 1 March 2025
Line 339:		Line 339:
	For PLUS v1.0 of 2025, Feb 28:		For PLUS v1.0 of 2025, Feb 28:

	* [https://drive.google.com/file/d/1V_FSMEBYsinXPMKlH3_OmzcS8f1zjVeL/view?usp=sharing gen_lang_plus_source_v1.0.zip]		* [https://drive.google.com/file/d/1V_FSMEBYsinXPMKlH3_OmzcS8f1zjVeL/view?usp=sharing gen_lang_plus_source_v1.0.zip]. This is a Visual Studio project.
	* [https://drive.google.com/file/d/1xsas9kZ-6tRdNdFhKHS736xYK5-aYGMg/view?usp=sharing gen_lang_plus.exe]		* [https://drive.google.com/file/d/1xsas9kZ-6tRdNdFhKHS736xYK5-aYGMg/view?usp=sharing gen_lang_plus.exe]

	== See Also ==		== See Also ==
	The Perl program "i18n.pl" contains similar functionality for FM-specific strings, but also parses and edits the FM .map file, so is considerably more complicated.		The Perl program "i18n.pl" contains similar functionality for FM-specific strings, but also parses and edits the FM .map file, so is considerably more complicated.

Geep: /* What's in Each Language Field */

2025-03-01T14:34:32Z

What's in Each Language Field

← Older revision		Revision as of 14:34, 1 March 2025
Line 162:		Line 162:
	* the categorization of the Missing Option.		* the categorization of the Missing Option.

	To make clear the difference, we repeat the Missing Options description, but with '''lines crossed out''' below. (PLUS follows what PL does here, but ~~has~~ commented out code ~~for~~ the crossed-out conditions.)		To make clear the difference, we repeat the Missing Options description, but with '''lines crossed out''' below. (PLUS follows what PL does here, but FYI, there is commented-out code that could implement the crossed-out conditions.)

Geep: /* Runtime Environment for PLUS */ tweaked

2025-03-01T14:29:42Z

Runtime Environment for PLUS: tweaked

← Older revision		Revision as of 14:29, 1 March 2025
Line 18:		Line 18:

	It is helpful to mention what these two programs do '''not''' take into account:		It is helpful to mention what these two programs do '''not''' take into account:
	* the <language>.map file that reroutes European codepoints from a standardized encoding to the TDM-specific custom 8-bit encoding discussed in [[I18N_-_Charset]]]		* the <language>.map file that reroutes European codepoints from a standardized encoding to the TDM-specific custom 8-bit encoding discussed in [[I18N_-_Charset]].
	* what UTF8 characters are allowed by that TDM-specific coding (as opposed to the ISO-8859 encoding).		* what UTF8 characters are allowed by that TDM-specific coding (as opposed to the ISO-8859 encoding).
	* the font and fontsize a specific string will use, and what limitations that entails, and what within-DAT glyph-substitutions may be in effect.		* the font and fontsize a specific string will use, and what limitations that entails, and what within-DAT glyph-substitutions may be in effect.
Line 25:		Line 25:
	To function in all aspects, PLUS requires Windows with certain UTF8 capabilities, introduced in later versions of Windows 10. Because the PLUS build is told explicitly to use UTF8, in theory what your "system locale" is set to should not matter. In particular, you are not required you set the system locale to the Windows 11 beta UTF8 codepage. (PLUS was developed on a dev box with the English (US) locale.)		To function in all aspects, PLUS requires Windows with certain UTF8 capabilities, introduced in later versions of Windows 10. Because the PLUS build is told explicitly to use UTF8, in theory what your "system locale" is set to should not matter. In particular, you are not required you set the system locale to the Windows 11 beta UTF8 codepage. (PLUS was developed on a dev box with the English (US) locale.)

	~~However, if you~~ run it under the traditional Windows console, that will not display UTF8 characters correctly on screen. Instead, use Windows Terminal (or Powershell with UTF8 encoding). Or pipe the console output to a file (i.e., "> myfile.txt"), that can be viewed as UTF8 with Notepad and other text editors.		You may run it under the traditional Windows console. However, that will not display UTF8 characters correctly on screen, which is mainly an issue with the -charstats and -charpunts options. Instead, use Windows Terminal (or Powershell with UTF8 encoding). Or pipe the console output to a file (i.e., "> myfile.txt"), that can be viewed as UTF8 with Notepad and other text editors.

	== Overview of Command-Line Options ==		== Overview of Command-Line Options ==

Geep: /* Downloads */ Add links

2025-03-01T03:08:12Z

Downloads: Add links

← Older revision		Revision as of 03:08, 1 March 2025
Line 337:		Line 337:

	== Downloads ==		== Downloads ==
	[~~SOON~~]		For PLUS v1.0 of 2025, Feb 28:

			* [https://drive.google.com/file/d/1V_FSMEBYsinXPMKlH3_OmzcS8f1zjVeL/view?usp=sharing gen_lang_plus_source_v1.0.zip]
			* [https://drive.google.com/file/d/1xsas9kZ-6tRdNdFhKHS736xYK5-aYGMg/view?usp=sharing gen_lang_plus.exe]

	== See Also ==		== See Also ==
	The Perl program "i18n.pl" contains similar functionality for FM-specific strings, but also parses and edits the FM .map file, so is considerably more complicated.		The Perl program "i18n.pl" contains similar functionality for FM-specific strings, but also parses and edits the FM .map file, so is considerably more complicated.

Geep: /* Charstats Option */ tweak example output

2025-03-01T02:46:45Z

Charstats Option: tweak example output

← Older revision		Revision as of 02:46, 1 March 2025
Line 220:		Line 220:
	8 U+00f6 ö 418		8 U+00f6 ö 418
	9 U+00fa ú 407		9 U+00fa ú 407
	10 U+~~00fd ý 401~~		....
	11 U+~~00e7 ç 326~~		93 U+0152 Œ 1
	12 U+~~017e ž 325~~		94 U+0158 Ř 1
	~~....~~		95 U+0179 Ź 1

	== Ranges Option and Holes Option ==		== Ranges Option and Holes Option ==
	Traditionally, #str_<id>s had only 5-digit numeric values. When a new string needed to be added (i.e., to the [English] master), it was helpful to know what numeric ranges were already fully in use, and conversely, what ranges are unoccupied, dubbed "holes". With these options, that info gets reported to the console. Note that for PL, "holes" reports only if "ranges" is not given as an option. PLUS removes that restriction.		Traditionally, #str_<id>s had only 5-digit numeric values. When a new string needed to be added (i.e., to the [English] master), it was helpful to know what numeric ranges were already fully in use, and conversely, what ranges are unoccupied, dubbed "holes". With these options, that info gets reported to the console. Note that for PL, "holes" reports only if "ranges" is not given as an option. PLUS removes that restriction.