Add TikZ 2D export format and port both SVG and TikZ to the C++ core

.clang-format

@@ -0,0 +1,19 @@
+---
+# Codifies the C++ style already in use across cpp/, bindings/, bindings_js/
+# (K&R braces, 4-space indent, no tabs). Does not apply to cpp/third_party
+# (vendored dependencies) or any fetched build directory.
+BasedOnStyle: Google
+Language: Cpp
+IndentWidth: 4
+UseTab: Never
+ColumnLimit: 100
+BreakBeforeBraces: Attach
+AccessModifierOffset: -4
+NamespaceIndentation: None
+PointerAlignment: Left
+ReferenceAlignment: Left
+AllowShortFunctionsOnASingleLine: Inline
+AllowShortIfStatementsOnASingleLine: false
+AllowShortLoopsOnASingleLine: false
+SortIncludes: Never
+DerivePointerAlignment: false

.clang-tidy

@@ -0,0 +1,16 @@
+# Include hygiene for the C++ core (see tools/include-cleanup.sh + the
+# `include-cleanup` CI job). Only the include-cleaner check is enabled -- this
+# is an IWYU-style "include exactly what you use" gate, NOT the full clang-tidy
+# lint surface. Formatting stays with .clang-format (SortIncludes: Never, so the
+# hand-maintained // System vs // Project ordering is preserved).
+#
+# HeaderFilterRegex restricts diagnostics/fixes to our own headers under cpp/
+# and bindings_c/ -- cpp/third_party (pugixml, eigen) is never touched.
+# Deliberately-"unused"-looking includes (compat shims, guarded optional-dep
+# headers) carry `// IWYU pragma: keep` in the source so include-cleaner leaves
+# them alone.
+---
+Checks: '-*,misc-include-cleaner'
+HeaderFilterRegex: '.*/(cpp/(include|src)|bindings_c)/.*'
+WarningsAsErrors: ''
+FormatStyle: file

.codecov.yml

@@ -1 +1,69 @@
 comment: no
+
+# Coverage arrives from the `coverage` job in .github/workflows/ci.yml as two
+# uploads: the Python package (coverage.xml, pytest-cov) and the C++20 core
+# (cpp-coverage.info, lcov). Both are produced in the same job, so the C++
+# numbers include the format code reached through the pybind11 shims rather
+# than only what the GoogleTest binary touches.
+flags:
+  python:
+    paths:
+      - src/meshioplusplus/
+    carryforward: false
+  cpp:
+    paths:
+      - cpp/
+      - bindings/
+      - bindings_c/
+    carryforward: false
+
+coverage:
+  precision: 2
+  round: down
+  range: "60...90"
+  status:
+    # Blocking on PRs. `target: auto` compares against the base commit, so the
+    # first upload just sets the baseline; later PRs only fail on a real drop
+    # beyond `threshold`. Per-flag project checks gate Python and C++ separately.
+    project:
+      default:
+        target: auto
+        threshold: 1%
+      python:
+        flags: [python]
+        target: auto
+        threshold: 1%
+      cpp:
+        flags: [cpp]
+        target: auto
+        threshold: 1%
+    # New/changed lines must carry tests; modest bar so trivial diffs don't stall.
+    patch:
+      default:
+        target: 70%
+        threshold: 1%
+
+ignore:
+  - "tests/"
+  - "cpp/tests/"
+  - "benchmark/"
+  - "cpp/third_party/"
+  - "doc/"
+  - "example/"
+  - "logo/"
+  - "tools/"
+  # Generated single-header amalgamation: a verbatim duplicate of cpp/ (kept in
+  # sync by CI). Counting it would double every cpp/ line.
+  - "single_include/"
+  # Non-MESHIO mesh backends: instantiated only by the standalone `cpp-tests`
+  # backend matrix, never by the MESHIO-only instrumented `coverage` job, so
+  # they are structurally unreachable here. Mirrors the lcov --remove in ci.yml.
+  - "cpp/include/meshioplusplus/backends/native_mesh.hpp"
+  - "cpp/include/meshioplusplus/backends/kratos_mesh.hpp"
+  - "cpp/include/meshioplusplus/backends/model_part.hpp"
+  - "cpp/include/meshioplusplus/backends/kratos_names.hpp"
+  # Not compiled by the coverage job (no Emscripten / no Fortran toolchain in
+  # this job); listed for clarity so a future config change can't silently
+  # start counting them as uncovered.
+  - "bindings_js/"
+  - "bindings_fortran/"

.flake8

@@ -1,4 +1,5 @@
 [flake8]
+exclude = venv, .tox
 ignore = E203, E266, E501, W503, C901, E741
 max-line-length = 88
 max-complexity = 18

.github/FUNDING.yml

@@ -0,0 +1,15 @@
+# These are supported funding model platforms
+
+github: # Replace with up to 4 GitHub Sponsors-enabled usernames e.g., [user1, user2]
+patreon: # Replace with a single Patreon username
+open_collective: # Replace with a single Open Collective username
+ko_fi: vicentemataixferrandiz # Replace with a single Ko-fi username
+tidelift: # Replace with a single Tidelift platform-name/package-name e.g., npm/babel
+community_bridge: # Replace with a single Community Bridge project-name e.g., cloud-foundry
+liberapay: # Replace with a single Liberapay username
+issuehunt: # Replace with a single IssueHunt username
+lfx_crowdfunding: # Replace with a single LFX Crowdfunding project-name e.g., cloud-foundry
+polar: # Replace with a single Polar username
+buy_me_a_coffee: # Replace with a single Buy Me a Coffee username
+thanks_dev: # Replace with a single thanks.dev username
+custom: # Replace with up to 4 custom sponsorship URLs e.g., ['link1', 'link2']

.github/ISSUE_TEMPLATE/bug_report.md

@@ -15,9 +15,9 @@ A minimal code example that reproduces the problem would be a big help if you ca
 **Diagnose**
 I may ask you to cut and paste the output of the following command.
 ```
-pip freeze | grep meshio
+pip freeze | grep meshioplusplus
 ```
 
 **Did I help?**
 
-If I was able to resolve your problem, consider [sponsoring](https://github.com/sponsors/nschloe) my work on meshio, or [buy me a coffee](https://ko-fi.com/nschloe) to say thanks.
+If I was able to resolve your problem, consider [buy me a coffee](https://ko-fi.com/vicentemataixferrandiz) to say thanks.

.github/ISSUE_TEMPLATE/feature_request.md

@@ -6,9 +6,9 @@ labels: Needs triage
 assignees: ''
 ---
 
-Consider posting in https://github.com/nschloe/meshio/discussions for feedback before raising a feature request.
+Consider posting in https://github.com/loumalouomega/meshioplusplus/discussions for feedback before raising a feature request.
 
-**How would you improve meshio?**
+**How would you improve meshio++?**
 
 Give as much detail as you can. Example code of how you would like it to work would help.
 
@@ -18,4 +18,4 @@ What problem do you have that this feature would solve? I may be able to suggest
 
 **Did I help**
 
-If I was able to resolve your problem, consider [sponsoring](https://github.com/sponsors/nschloe) my work on meshio, or [buy me a coffee](https://ko-fi.com/nschloe) to say thanks.
+If I was able to resolve your problem, consider [buy me a coffee](https://ko-fi.com/vicentemataixferrandiz) to say thanks.

.github/ISSUE_TEMPLATE/new_format.md

@@ -5,14 +5,14 @@ labels: new format
 assignees: ''
 ---
 
-Would you like support for a new mesh format in meshio? First check the existing issues, there are a number of format requests already. It's often easy to get rudimentary support for a format, so don't be afraid to start a PR!
+Would you like support for a new mesh format in meshio++? First check the existing issues, there are a number of format requests already. It's often easy to get rudimentary support for a format, so don't be afraid to start a PR!
 
-Consider posting in https://github.com/nschloe/meshio/discussions for feedback before raising a feature request.
+Consider posting in https://github.com/loumalouomega/meshioplusplus/discussions for feedback before raising a feature request.
 
 **Format specification?**
 
 Most formats have a detailed specification somewhere online. Make sure to post a link to that.
 
 **Did I help**
 
-If I was able to resolve your problem, consider [sponsoring](https://github.com/sponsors/nschloe) my work on meshio, or [buy me a coffee](https://ko-fi.com/nschloe) to say thanks.
+If I was able to resolve your problem, consider [buy me a coffee](https://ko-fi.com/vicentemataixferrandiz) to say thanks.