1. 06 Sep, 2017 1 commit
    • Sébastien Wilmet's avatar
      language-specs: do not mark strings for translation · eec7a2fe
      Sébastien Wilmet authored
      Keep only the _section translatable, those make sense to translate.
      
      The language names (e.g. Swift, Kotlin, Maxima) should not be
      translated, for example if Maxima is translated the user will certainly
      be confused…
      
      The style names are not very useful to translate, because the user never
      sees those strings! It is used for example by a gedit plugin to
      create/edit style schemes. The style names are probably hard to
      translate anyway, and I'm sure that it was often translated in a way
      that the user didn't understand what it means… So, since those strings
      are extremely rarely used, and since they are hard to translate without
      context, it is better to not translate them at all. It's like GObject
      properties.
      
      Also, the *.lang file format doesn't support well translatable strings.
      Ideally each translatable string should have its own tag, with the
      translatable="yes" property, the possibility to add a context, etc.
      eec7a2fe
  2. 25 Dec, 2016 1 commit
  3. 01 Sep, 2015 4 commits
  4. 20 Jan, 2015 1 commit
  5. 18 Jan, 2015 1 commit
    • David Miguel Susano Pinto's avatar
      matlab/octave: drop its use for files with mime for the other type. · 50497519
      David Miguel Susano Pinto authored
      * both matlab.lang and octave.lang files were currently being used for
      files with mimetypes "text/x-matlab" and "text/x-octave".  Octave has
      plenty of extra syntax missing from Matlab and thus, the matlab mimetype
      should not be used for files identified as octave.  While the opposite
      is not true, i.e., Matlab code should run just fine in Octave, in
      practice, code that is identified as Matlab is probably aiming at Matlab
      compatibility and should avoid using Octave highlight.
      
      * Note that whether a file was written in Octave or Matlab is irrelevant.
      If a file was written in Octave but only uses features that are also
      present in Matlab, it probably aims at Matlab compatibility and should
      be highlighted as Matlab.
      50497519
  6. 11 Dec, 2012 1 commit
  7. 29 Aug, 2012 3 commits
  8. 02 May, 2011 1 commit
  9. 25 Apr, 2011 1 commit
    • Paolo Borelli's avatar
      Split and update matlab and octave lang files. · f25a00ae
      Paolo Borelli authored
      The two syntaxes have grown too different to keep a single lang file.
      Split in two files and leverage inclusion to share common parts.
      Octave lang file can then be improved with all the octave specific
      extensions. Patch by Carnë Draug.
      f25a00ae
  10. 08 Jun, 2010 2 commits
  11. 18 May, 2010 1 commit
  12. 31 Dec, 2009 1 commit
  13. 13 May, 2009 1 commit
  14. 13 Mar, 2009 1 commit
  15. 02 Feb, 2009 1 commit
  16. 01 Nov, 2008 1 commit
  17. 11 Apr, 2008 1 commit
  18. 06 Sep, 2007 1 commit
  19. 27 Jul, 2007 1 commit
  20. 17 Jul, 2007 1 commit
    • Yevgen Muntyan's avatar
      Attempt to fix usage of def:preprocessor style. def:preprocessor stays in, · 8163b7ac
      Yevgen Muntyan authored
      2007-07-17  Yevgen Muntyan  <muntyan@tamu.edu>
      
      	Attempt to fix usage of def:preprocessor style. def:preprocessor
      	stays in, and is supposed to be used for "preprocessor things".
      	Too late now to fix it, should have done it in convert.py a year ago.
      	Added def:special-value style for things like TRUE and FALSE in C.
      
      	* gtksourceview/language-specs/def.lang:
      	* gtksourceview/language-specs/sql.lang:
      	* gtksourceview/language-specs/javascript.lang:
      	* gtksourceview/language-specs/po.lang:
      	* gtksourceview/language-specs/ini.lang:
      	* gtksourceview/language-specs/python.lang:
      	* gtksourceview/language-specs/c.lang:
      	* gtksourceview/language-specs/scheme.lang:
      	* gtksourceview/language-specs/texinfo.lang:
      	* gtksourceview/language-specs/tango.xml:
      	* gtksourceview/language-specs/gtkrc.lang:
      	* gtksourceview/language-specs/gvim.xml:
      	* gtksourceview/language-specs/css.lang:
      	* gtksourceview/language-specs/perl.lang:
      	* gtksourceview/language-specs/kate.xml:
      	* gtksourceview/language-specs/java.lang:
      	* gtksourceview/language-specs/octave.lang:
      	See above.
      
      	* gtksourceview/language-specs/pkgconfig.lang:
      	Added comments.
      
      	* gtksourceview/language-specs/testfiles.sh:
      	A script which outputs bunch of files using different languages,
      	to quick-test whether parsing/highlighting broke.
      
      
      svn path=/trunk/; revision=1507
      8163b7ac
  21. 18 Jun, 2007 1 commit
    • Yevgen Muntyan's avatar
      Continuing great relicensing. · f8e5bb49
      Yevgen Muntyan authored
      2007-06-17  Yevgen Muntyan  <muntyan@tamu.edu>
      
      	Continuing great relicensing.
      
      	* README: updated the paragraph about licenses.
      
      	* gtksourceview/language-specs/*:
      
      	Added authors, contributors and license texts.
      
      
      svn path=/trunk/; revision=1412
      f8e5bb49
  22. 25 May, 2007 1 commit
  23. 03 Jan, 2006 1 commit