Fix automake or autoconf files for allowing make dist command copy the extdata directory with all files in the tarball.

PS C:\work\CodeNowHere> ls -l foo.cpp


    Directory: C:\work\CodeNowHere


Mode                 LastWriteTime         Length Name
----                 -------------         ------ ----
-a----         3/28/2023   8:48 PM           2520 foo.cpp


PS C:\work\CodeNowHere> cnh this foo.cpp
File foo.cpp already exists in this directory. If you continue its content will be replaced
Do you want to continue (Y/n): Y
foo.cpp created!
PS C:\work\CodeNowHere> ls -l foo.cpp


    Directory: C:\work\CodeNowHere


Mode                 LastWriteTime         Length Name
----                 -------------         ------ ----
-a----         3/30/2023   3:10 PM           3360 foo.cpp


PS C:\work\CodeNowHere>

you see that the file size just grows

this is becuase the file is opened in append mode.

Its easy to fix, I can do it, but it would be nice to take my other PR first

Is your feature request related to a problem? Please describe.

Due that some file extensions can be share between different programming or markup languages, the current system of storing data in files could be very problematic in the future. This can be helpful when the program is supposed to create one file that share any common extension, it should ask user to select the correct type of language.

Describe the solution you'd like

It would be cool to implement a light database such as sqlite3 for storing relevant data of each language. And change the logic to access to its data instead of reading it from files.

Describe alternatives you've considered

Additional context

I would like to contribute multiple things to this project. My first contrib is a windows version.

To do this I made a major change. I converted the build system to cmake. This is way more convenient than the autoconf, automake etc.

I fixed a few non portability issues.

I also change how googletest gets run. I followed their instructions for cmake integration - https://google.github.io/googletest/quickstart-cmake.html

It now builds and runs on windows vs2022, ubuntu gcc, and mac clang M1 ( I dont have an intel mac)

Would you like to take a look at the PR

name: Support for custom/enterprise copyright string
about: copyright string part of header of any generated file
title: ''
labels: ''
assignees: guthub.com/Rahul27297

Is your feature request related to a problem? Please describe.
Feature is not related to a problem. The proposed feature is an enhancement.
Several times (always in my case) the author is just an employee/contributor to a project. In such a scenario, the copyright string that is generated needs to be replaced with the actual string. Very often in projects the author is not the sole copyright owner. Hence, I feel this feature is good to have.

Describe the solution you'd like
I propose we can add a new cli option, something like --crs ""which can be used to mention the custom copyright string. This could be made exclusive to the current --cr option which shall by default set the author's copyright.

Describe alternatives you've considered
Another option that I considered was, --crs option proposed above could be used in conjunction with the --cr option. If --crs is present use the custom copyright provided, else use the default. However this will add the number of options that one would need to specify. Hence I feel if we make --crs and --cr exclusive options, it will improve the user's experience.

Additional context
Please revert back if anything else is needed. I prefer to work on this feature myself, if approved by the repo owners.

Supporting more programming languages

Base in the contribution flow and steps present here create your branch and start contributing.

First check that the language you want to add is not already in the file.

You can edit the extdata/lang.dat file; adding new programming language file extensions using the following format:
append below the last line of the file

.ext1 .ext2 .extN : nameoflanguage

for instance:
.rb .rbw : ruby

Then you can edit extdata/inlineComments.txt. There you can add the extensions according to inline comment character(s). It follows the same convention like before, but after the colon is now the inline comment character(s) specified instead of nameoflanguage.

for instance:
if another language extensions uses the same inline comment, then add them next to it.
.py .pyc .pyo .pyd .php .rb .rbw : # {}
otherwise, create a new line below the last line this way:
.rb .rbw : # {}

The {} specifies the closing comment character is not required. But in a language that is required such html you could set it like this:
.html .htm : <!-- -->

Then, you have to create a new file named nameoflanguage.tpl (nameoflanguage must be the same as it was in inlineComments.txt). Open it and write in the first line a sample code of line printing "Hello World" or a main function/method that prints the well known message "Hello World" too.

Finally, do not forget to write the new language into the alphabetically ordered list in README section.

You can create a PR with a message saying what language you are adding.