Edit: Done

See https://git-scm.com/book/en/v2/Git-Tools-Submodules documentation.

For me for only two file we don't need git submodule.

Thanks to elevatormind for his initial work on including fonts and Laurent (scorpio810) for packaging the binaries we now have a QElectroTech - Version in 0.100-dev with some included fonts:

• Liberation Mono

• Liberation Sans

• Liberation Serif

• osifont

No effort is required from the user to be able to use the fonts:
The fonts are available in QElectroTech with the installation of QElectroTech!
Of course, all other fonts of the operating system used can still be used in your elements and diagrams!
However, if you think about exchanging of the resulting work between different computers and/or systems, we recommend limiting yourself to the included fonts!

In this context, the default font in QET was set to Liberation Sans and all existing elements were revised so that Liberation fonts are now used everywhere!

With writing these lines, I noticed, that "osifont.ttf" was updated upstream.
This is by no means a problem for users, but it does lead to a question for Laurent:
(How) can we link "fonts/osifont.ttf" and "fonts/osifont-italic.ttf" to the original versions at github?
We already link pugixml and SingleApplication to their github-repos, so it may be possible to link two single files to their position in github-subdirs?
We don't need the whole directory: That would be way too much!
The two ttf-files would be enough: osifont.ttf and osifont-italic.ttf

As a German politician says: ‘Please misunderstand me correctly!’ 
I didn't mean you with the long delay, Laurent!
Just was very surprised that elevatormind didn't get in touch for so long:
As suddenly as he appeared here and contributed so much, so suddenly it became quiet again from Sweden!
Let's hope that he's okay and will be able to discuss and contribute again soon!

Of course I also hope that you are on the road to recovery, Laurent!

In the meantime I uploaded the sources and also the reworked elements to the official QET github-repos.
I don't know, if your scripts have to be adjusted: There are two new sub-directories for fonts and licenses in the tree.
So that we don't have a 'double stock' of licenses, I use symbolic links to the existing licenses from the subdirectory. Github and Linux can handle this...

Since this doesn't change anything for my packaging scripts, yes you can push it.
Sorry for the delay!

More than five weeks with no reaction to my last post and I would like to get further with this topic!

Do you think we should upload elevatormind's source code for/with the fonts and my additions regarding the licenses in one commit? The language files can be adjusted and after that I could also upload the revised elements from my to the official QET-repository.
So: Some changes that depend on each other, but the first step is still missing.

I already prepared that combined commit in my github-repo.

What do you think, Laurent?

haven't heard from you in a while, are you okay?

Could you please create a PR for your additions to the fonts?
Then we could finalize that topic from here.
I have already adjusted the tabs for the licenses locally: All licenses are grouped in one tab and can be selected for viewing via ComboBox.
But that only makes sense to upload once the fonts are available.
And the customized element collection is also waiting to be activated: Only the fonts are missing...