copy

aider/website/docs/languages.md

@@ -5,7 +5,7 @@ description: Aider supports pretty much all popular coding languages.
 ---
 # Supported languages
 
-Aider supports almost all popular coding languages.
+Aider should work well with most popular coding languages.
 This is because top LLMs are fluent in most mainstream languages,
 and familiar with popular libraries, packages and frameworks.
 
@@ -20,8 +20,6 @@ a [repository map](https://aider.chat/docs/repomap.html).
 Aider can currently produce repository maps for many popular
 mainstream languages, listed below.
 
-Aider should work quite well for other languages, even those
-without repo map or linter support.
 
 <!--[[[cog
 from aider.repomap import get_supported_languages_md
@@ -82,3 +80,30 @@ cog.out(get_supported_languages_md())
 
 <!--[[[end]]]-->
 
+
+
+## How to add support for another language
+
+Aider should work quite well for other languages, even those
+without repo map or linter support.
+You should really try coding with aider before
+assuming it needs better support for your language.
+
+That said, if aider already has support for linting your language,
+then it should be possible to add repo map support.
+To build a repo map, aider needs the `tags.scm` file
+from the given language's tree-sitter grammar.
+If you can find and share that file in a 
+[GitHub issue](https://github.com/paul-gauthier/aider/issues),
+then it may be possible to add repo map support.
+
+If aider doesn't support linting, it will be complicated to
+add linting and repo map support.
+That is because aider relies on 
+[py-tree-sitter-languages](https://github.com/grantjenks/py-tree-sitter-languages)
+to provide pre-packaged versions of tree-sitter
+parsers for many languages.
+
+Aider needs to be easy for users to install in many environments,
+and it is probably too complex to add dependencies on
+additional individual tree-sitter parsers.