On the filetypes menu. I have ranted before (at _least_ once) about the inadequacy of the current categories, so I won't go into it again. But really what is the difference between a scripting language and a programming language? Why do we categorise Python as a scripting language when "Python is a programming language..." is the first text on its web page, or Ruby "A dynamic, open source programming language..." according to its web page. But I guess Geany knows better than the language developers? And why are specialised languages like GLSL and VHDL occupying space in "Programming Languages" instead? And its not about AOT compile [(see the table)](https://github.com/geany/geany/blob/7fd2507e6054617354fe941f2964be68b4536f44/src/filetypes.c#L127), Java is Jit not compiled, Julia is JIT or AOT compiled, but one is seen as a programming language and the other as a script, and languages like Python have more than one implementation, since Python has pypy and its a JIT, Python should be in programming languages with Java and so should Julia, and Ruby has Jruby that runs on the JVM, just like Java. The categories don't make sense.
... Oops I seem to have ranted again, oh well while I'm in the mood let me go on to the issue of translations ... Why are just five of the more than 70 filetypes translated? Specifically why are __these__ five translated, shell, makefile, CSS, conf, and PO? If a user is capable of writing a makefile surely they can understand "Make" and don't need "Makefile" translated, that seems condescending to me. Same for "Sh" and "Shell", every current shell has "sh" in it, if a user is competent to write it they will understand what "Sh" is, and many languages don't bother to translate "Shell" (eg French, doesn't say Coquille, or German, Hülse? and those are the references for translations ;-). And "CSS" and "Cascading Stylesheet", FGS!! if someone can read CSS they surely know what "CSS" means. And "PO" and "Gettext translation", users don't write those files (they do edit them, but tools generate them) so the menu item is likely unused, so why go to the effort of translating it (and a quick look at some of the translations they leave "gettext" and just translate "translation", so why not just call the filetype "Gettext". [end rant, I feel much better now] If Geany dropped these frankly useless translations the filetypes menu could then be divided alphabetically, and could then grow in a more sustainable manner, if one sub menu gets too long move a few at the front or end to the previous or next submenu, and if two adjacent get too long split them into a new submenu in between. Makes it simple. -- Reply to this email directly or view it on GitHub: https://github.com/geany/geany/issues/3651#issuecomment-1778323029 You are receiving this because you are subscribed to this thread. Message ID: <geany/geany/issues/3651/[email protected]>
