cpp/openttd-patchpack/source Changeset - r4624:1a07a53b2696

Changeset - r4624:1a07a53b2696

Parent rev.

Child rev.

[Not reviewed]

master

0 1 0

belugas - 18 years ago 2006-09-20 00:24:38
belugas@openttd.org

(svn r6484) -Undo (partly)r6289. If a grf writer wants a string been only a space, why should it be blocked?
It is the wrong test at the wrong place

1 file changed with 0 insertions and 3 deletions:

newgrf_text.c

0 comments (0 inline, 0 general)

newgrf_text.c

➞

Show inline comments

@@ @@ -195,27 +195,24 @@ static void TranslateTTDPatchCodes(char @@
+	}
+}
 /**
  * Add the new read string into our structure.
  */
 StringID AddGRFString(uint32 grfid, uint16 stringid, byte langid_to_add, bool new_scheme, const char *text_to_add, StringID def_string)
+{
 	GRFText *newtext;
 	uint id;
 	/* We do not allow strings of only one char or even fewer*/
 	if (strlen(text_to_add) <= 1) return STR_EMPTY;
 	/* When working with the old language scheme (grf_version is less than 7) and
 	 * English or American is among the set bits, simply add it as English in
 	 * the new scheme, i.e. as langid = 1.
 	 * If English is set, it is pretty safe to assume the translations are not
 	 * actually translated.
 	 */
 	if (!new_scheme) {
 		if (HASBITS(langid_to_add, GRFLB_AMERICAN | GRFLB_ENGLISH)) {
 			langid_to_add = GRFLX_ENGLISH;
 		} else {
 			StringID ret = STR_EMPTY;
 			if (langid_to_add & GRFLB_GERMAN)  ret = AddGRFString(grfid, stringid, 1 << 6 | GRFLX_GERMAN,  true, text_to_add, def_string);

0 comments (0 inline, 0 general)