I'm working on modernizing Rosetta Code's infrastructure. Starting with communications. Please accept this time-limited open invite to RC's Slack.. --Michael Mol (talk) 20:59, 30 May 2020 (UTC)

User talk:MizardX/GeSHi Go.php

From Rosetta Code

Hi MizardX,

I had a look at the language file and there are some issues left for fixing.

  1. Checking where to find GeSHi installation ...OK
  2. Listing available language files ... OK
  3. Validating language file for 'go' ... Failed
  1. ERROR Language file contains no $language_data['CASE_SENSITIVE'] specification for keyword group 5!
  2. WARNING Language file contains no GESHI_REPLACE entry in extended regular expression at $language_data['REGEXPS'][0]!
  3. WARNING Language file contains no GESHI_MODIFIERS entry in extended regular expression at $language_data['REGEXPS'][0]!
  4. WARNING Language file contains no GESHI_BEFORE entry in extended regular expression at $language_data['REGEXPS'][0]!
  5. WARNING Language file contains no GESHI_AFTER entry in extended regular expression at $language_data['REGEXPS'][0]!
  6. WARNING Language file contains no GESHI_REPLACE entry in extended regular expression at $language_data['REGEXPS'][1]!
  7. WARNING Language file contains no GESHI_MODIFIERS entry in extended regular expression at $language_data['REGEXPS'][1]!
  8. WARNING Language file contains no GESHI_BEFORE entry in extended regular expression at $language_data['REGEXPS'][1]!
  9. WARNING Language file contains no GESHI_AFTER entry in extended regular expression at $language_data['REGEXPS'][1]!
  10. WARNING Language file contains no GESHI_REPLACE entry in extended regular expression at $language_data['REGEXPS'][2]!
  11. WARNING Language file contains no GESHI_MODIFIERS entry in extended regular expression at $language_data['REGEXPS'][2]!
  12. WARNING Language file contains no GESHI_BEFORE entry in extended regular expression at $language_data['REGEXPS'][2]!
  13. WARNING Language file contains no GESHI_AFTER entry in extended regular expression at $language_data['REGEXPS'][2]!

Messages taken from the language check script.

Regarding the numbers: Could you use multiple number groups with regexps there instead of using the regexps groups to do this.

I pushed a slightly updated version into your wiki page.

Edit: Just forgot to mention: Literal strings can be done with HARD_ESCAPE strings. That's the more natural way to do this ^^

Regards,
BenBE

Thank you. I think I have fixed all that you have mentioned. Could you test it again? --MizardX 13:25, 12 July 2010 (UTC)