vexy-localizzy 1.0.0__tar.gz

vexy_localizzy-1.0.0/.gitignore

@@ -0,0 +1,226 @@
+# Byte-compiled / optimized / DLL files
+src/vexy_localizzy/_version.py
+*.sqlite
+*.sqlite-*
+*.sources/
+__pycache__/
+*.py[codz]
+*$py.class
+
+# C extensions
+*.so
+
+# Distribution / packaging
+.Python
+build/
+develop-eggs/
+dist/
+downloads/
+eggs/
+.eggs/
+lib/
+lib64/
+parts/
+sdist/
+var/
+wheels/
+share/python-wheels/
+*.egg-info/
+.installed.cfg
+*.egg
+MANIFEST
+
+# PyInstaller
+#   Usually these files are written by a python script from a template
+#   before PyInstaller builds the exe, so as to inject date/other infos into it.
+*.manifest
+*.spec
+
+# Installer logs
+pip-log.txt
+pip-delete-this-directory.txt
+
+# Unit test / coverage reports
+htmlcov/
+.tox/
+.nox/
+.coverage
+.coverage.*
+.cache
+nosetests.xml
+coverage.xml
+*.cover
+*.py.cover
+.hypothesis/
+.pytest_cache/
+cover/
+
+# Translations
+*.mo
+*.pot
+
+# Django stuff:
+*.log
+local_settings.py
+db.sqlite3
+db.sqlite3-journal
+
+# Flask stuff:
+instance/
+.webassets-cache
+
+# Scrapy stuff:
+.scrapy
+
+# Sphinx documentation
+docs/_build/
+
+# PyBuilder
+.pybuilder/
+target/
+
+# Jupyter Notebook
+.ipynb_checkpoints
+
+# IPython
+profile_default/
+ipython_config.py
+
+# pyenv
+#   For a library or package, you might want to ignore these files since the code is
+#   intended to run in multiple environments; otherwise, check them in:
+# .python-version
+
+# pipenv
+#   According to pypa/pipenv#598, it is recommended to include Pipfile.lock in version control.
+#   However, in case of collaboration, if having platform-specific dependencies or dependencies
+#   having no cross-platform support, pipenv may install dependencies that don't work, or not
+#   install all needed dependencies.
+# Pipfile.lock
+
+# UV
+#   Similar to Pipfile.lock, it is generally recommended to include uv.lock in version control.
+#   This is especially recommended for binary packages to ensure reproducibility, and is more
+#   commonly ignored for libraries.
+# uv.lock
+
+# poetry
+#   Similar to Pipfile.lock, it is generally recommended to include poetry.lock in version control.
+#   This is especially recommended for binary packages to ensure reproducibility, and is more
+#   commonly ignored for libraries.
+#   https://python-poetry.org/docs/basic-usage/#commit-your-poetrylock-file-to-version-control
+# poetry.lock
+# poetry.toml
+
+# pdm
+#   Similar to Pipfile.lock, it is generally recommended to include pdm.lock in version control.
+#   pdm recommends including project-wide configuration in pdm.toml, but excluding .pdm-python.
+#   https://pdm-project.org/en/latest/usage/project/#working-with-version-control
+# pdm.lock
+# pdm.toml
+.pdm-python
+.pdm-build/
+
+# pixi
+#   Similar to Pipfile.lock, it is generally recommended to include pixi.lock in version control.
+# pixi.lock
+#   Pixi creates a virtual environment in the .pixi directory, just like venv module creates one
+#   in the .venv directory. It is recommended not to include this directory in version control.
+.pixi
+
+# PEP 582; used by e.g. github.com/David-OConnor/pyflow and github.com/pdm-project/pdm
+__pypackages__/
+
+# Celery stuff
+celerybeat-schedule
+celerybeat.pid
+
+# Redis
+*.rdb
+*.aof
+*.pid
+
+# RabbitMQ
+mnesia/
+rabbitmq/
+rabbitmq-data/
+
+# ActiveMQ
+activemq-data/
+
+# SageMath parsed files
+*.sage.py
+
+# Environments
+.env
+.envrc
+.venv
+env/
+venv/
+ENV/
+env.bak/
+venv.bak/
+
+# Spyder project settings
+.spyderproject
+.spyproject
+
+# Rope project settings
+.ropeproject
+
+# mkdocs documentation
+/site
+
+# mypy
+.mypy_cache/
+.dmypy.json
+dmypy.json
+
+# Pyre type checker
+.pyre/
+
+# pytype static type analyzer
+.pytype/
+
+# Cython debug symbols
+cython_debug/
+
+# PyCharm
+#   JetBrains specific template is maintained in a separate JetBrains.gitignore that can
+#   be found at https://github.com/github/gitignore/blob/main/Global/JetBrains.gitignore
+#   and can be added to the global gitignore or merged into this file.  For a more nuclear
+#   option (not recommended) you can uncomment the following to ignore the entire idea folder.
+# .idea/
+
+# Abstra
+#   Abstra is an AI-powered process automation framework.
+#   Ignore directories containing user credentials, local state, and settings.
+#   Learn more at https://abstra.io/docs
+.abstra/
+
+# Visual Studio Code
+#   Visual Studio Code specific template is maintained in a separate VisualStudioCode.gitignore 
+#   that can be found at https://github.com/github/gitignore/blob/main/Global/VisualStudioCode.gitignore
+#   and can be added to the global gitignore or merged into this file. However, if you prefer, 
+#   you could uncomment the following to ignore the entire vscode folder
+# .vscode/
+# Temporary file for partial code execution
+tempCodeRunnerFile.py
+
+# Ruff stuff:
+.ruff_cache/
+
+# PyPI configuration file
+.pypirc
+
+# Marimo
+marimo/_static/
+marimo/_lsp/
+__marimo__/
+
+# Streamlit
+.streamlit/secrets.toml
+
+# Review frontend build dependencies
+node_modules/
+review/.vite/

vexy_localizzy-1.0.0/DEPENDENCIES.md

@@ -0,0 +1,183 @@
+---
+this_file: DEPENDENCIES.md
+---
+# Dependencies
+
+| Package | Role |
+|---|---|
+| lxml 6.1.x | Streaming XML parsing, preservation of inline XML, no external entity expansion |
+| langcodes 3.5.x | BCP 47 canonicalization without inventing locale mappings |
+| fluent.syntax 0.19.0 (`sources` extra) | Published Fluent AST/parser/serializer for bounded legacy message, term, attribute and selector projections |
+| moz.l10n 0.14.2 (`sources` extra) | Published Mozilla properties/DTD parsing with explicit entity-reference and include handling |
+| javaproperties 0.8.2 (`sources` extra) | Java properties escapes, surrogate pairs, continued lines and ordered duplicate keys |
+| openstep-plist 0.5.2 (`sources` extra) | Published OpenStep parser for ordered Apple .strings extraction; binary/XML resources use stdlib plistlib |
+| language-data 1.x (`sources` extra) | Published CLDR population data for the optional legacy filename policy; resolved at 1.4.0 with marisa-trie 1.4.1 |
+| uubed 1.0.6 + NumPy 2.x (`embeddings` extra) | Published model inference/space identity and bounded float32 vector operations |
+| scikit-learn 1.9.x + threadpoolctl 3.x (`clustering` extra) | MiniBatchKMeans, bounded initialization sampling and reproducible single-thread numerical work |
+| pydantic 2.x | Versioned catalog boundaries, strict fields and original-document checksums |
+| polib 1.2.x | Published gettext parser and serializer, including legacy encodings and obsolete records |
+| Existing ElementTree/polib parsers | Explicit legacy Qt/gettext pair projections; no additional runtime dependency |
+| tree-sitter 0.26.x + tree-sitter-json 0.24.x | Published JSON syntax tree with byte spans for scoped, formatting-preserving resource edits |
+| tree-sitter-cpp 0.23.x | Published C++ grammar for exact literal spans in English source corrections; shares the existing tree-sitter runtime |
+| filelock 3.x (`llm`/`review` extras) | Cross-platform exclusion of simultaneous classification and catalog-review writers |
+| openai 2.54+ (`llm` extra) | Optional bounded transport; preserves provider retry timing for fallbacks |
+| fire 0.7.x | CLI argument parsing and help |
+| loguru 0.7.x | Optional verbose diagnostics |
+| hatchling + hatch-vcs | Build wheel/sdist and derive versions from Git |
+| pytest + pytest-cov + ruff | Behavior tests, coverage and static checks |
+
+SQLite, gzip and atomic file operations use Python's standard library.
+English source correction application also needs Qt's `lupdate` executable
+(Qt Linguist tools). It re-extracts current message contexts and locations before
+planning edits. Preparation and a no-change apply do not need Qt installed.
+Parser usage follows the [Tree-sitter Python API](https://tree-sitter.github.io/py-tree-sitter/).
+Source offsets avoid Point accessors, which reproduced heap corruption locally;
+see [upstream issue 487](https://github.com/tree-sitter/py-tree-sitter/issues/487).
+Selected exports use SQLite's documented [attached databases](https://www.sqlite.org/lang_attach.html)
+for explicit disk staging and window functions for the existing winner policy;
+caller TEMP-table settings are preserved. Classification handoff follows SQLite
+[read-snapshot isolation](https://www.sqlite.org/isolation.html) and Python
+[read-only URI connections](https://docs.python.org/3.12/library/sqlite3.html#how-to-work-with-sqlite-uris),
+with existing Pydantic models for evidence boundaries. The handoff itself needs no additional package. The producer uses the documented
+[filelock context manager](https://py-filelock.readthedocs.io/en/latest/) with a
+zero acquisition timeout; an isolated lock/reacquisition check passed on macOS.
+Catalog compatibility types and key/placeholder helpers are adapted from
+MIT-licensed fl10n; attribution and license text are included in `NOTICE`.
+Legacy filename planning is also adapted from that project. It uses
+[langcodes](https://github.com/rspeer/langcodes) and its published
+[language_data supplement](https://github.com/rspeer/language_data); input locale
+identity remains separate from population-based filename shortening.
+Format preservation and provider routing are original implementations;
+public tests and examples contain synthetic data.
+
+Published integration APIs have been exercised for abersetz 1.0.28 and 1.1 (dev),
+uubed 1.0.6 and quiht-tools 1.0.8; the registry also offers quiht-core 1.0.8.
+The uubed adapter is an optional component. Its CPU integration check uses
+sentence-transformers 5.7.0 and transformers 4.57.6 with the revision-pinned
+MiniLM model from uubed's registry. These inference dependencies are not core
+requirements. The abersetz and quiht adapters are integrated and tested below.
+
+The installed uubed 1.0.6 `Embedder` implementation was inspected for normalized
+float32 output, model revision, prompt, token limit and cache identity semantics.
+Its existing TMX index builder publishes atomically but starts over on interrupted
+inference. Localizzy adds resumable per-source vector storage for classification
+and distillation, retaining checksums, source IDs and explicit engine identity.
+
+Clustering follows the published [MiniBatchKMeans API](https://scikit-learn.org/stable/modules/generated/sklearn.cluster.MiniBatchKMeans.html)
+and reservoir sampling API; the installed `partial_fit` implementation was checked
+before integration. Strict subset responses use the existing Pydantic dependency.
+Subset selection shares classification's cache, retry and identity machinery.
+
+Parser behavior follows the [lxml streaming documentation](https://lxml.de/parsing.html).
+Qt metadata handling follows the [TS format specification](https://doc.qt.io/qt-6/linguist-ts-file-format.html).
+The existing Translate Toolkit TS adapter documents incomplete byte/length-variant
+coverage, so the TS preservation layer uses lxml and retains the original bytes.
+The optional transport follows the [OpenAI SDK error API](https://github.com/openai/openai-python#handling-errors).
+PO parsing follows [polib's API](https://polib.readthedocs.io/en/latest/api.html)
+and [GNU gettext entry syntax](https://www.gnu.org/software/gettext/manual/html_node/PO-File-Entries.html).
+The Python standard library's gettext expression parser checks explicit plural
+rule syntax; category ordering is supplied by the caller. Original bytes remain
+the authority for unchanged documents.
+
+XLIFF handling follows the OASIS [1.2 specification](https://docs.oasis-open.org/xliff/v1.2/os/xliff-core.html),
+[2.1 core](https://docs.oasis-open.org/xliff/xliff-core/v2.1/os/xliff-core-v2.1-os.html)
+and [2.2 core](https://docs.oasis-open.org/xliff/xliff-core/v2.2/xliff-core-v2.2-part1.pdf).
+The lxml preservation layer retains original documents and module data; generated
+and edited examples are checked against official core XSDs in integration audits.
+This is not a claim of complete module/Schematron conformance.
+
+Android resource handling follows the official [string-resource specification](https://developer.android.com/guide/topics/resources/string-resource)
+and AOSP AAPT2 string parsing. The published Translate Toolkit adapter was tested
+but drops unknown backslash escapes that AAPT2 retains, so the preservation layer
+uses lxml with Android text decoding. Integration checks compile and link synthetic
+resources with Google's [AAPT2](https://developer.android.com/tools/aapt2), comparing
+the resulting values with independently authored fixtures. AAPT2 is an audit tool,
+not a runtime dependency; these checks do not claim full Android conformance.
+
+i18next follows the official [v4 resource format](https://www.i18next.com/misc/json-format)
+and [plural behavior](https://www.i18next.com/translation-function/plurals).
+Python's JSON decoder validates strict syntax and duplicate keys; the published
+[Tree-sitter bindings](https://github.com/tree-sitter/py-tree-sitter) and JSON grammar
+locate original value bytes. Both use MIT licenses. Translate Toolkit's i18next
+adapter targets v3 plural suffixes. A JSON source-map candidate also failed escaped
+key identity checks; neither is used. Native integration checks use published
+i18next 26.3.6 as an audit dependency, not a Python runtime dependency.
+
+Catalog TMX uses the existing lxml dependency and follows the
+[TMX 1.4b specification](https://www.ttt.org/oscarStandards/tmx/tmx14b.html).
+Original multilingual XML is retained; catalog-only metadata uses documented
+extension properties. Integration checks validate fresh output against a bundled
+TMX 1.4 DTD and independently compare scoped edits in native catalog samples.
+This is not a claim of complete TMX Level-2 conformance.
+
+The reviewer uses FastAPI and Uvicorn for a loopback HTTP API over the filesystem
+store, without an application database. Its bundled React/Vite/TypeScript client
+uses published quiht-core 1.0.8 to render Qt UI XML, DOMPurify for sanitization and
+lucide-react for UI icons. Exact frontend versions are in `review/package-lock.json`;
+bundled license texts are in `review/public/THIRD_PARTY_LICENSES.txt`. Vitest and
+Testing Library exercise state changes; browser acceptance uses Playwright with
+installed Chrome when the in-app browser is unavailable. Playwright is an audit
+dependency, not a runtime dependency. The iframe permits same-origin DOM access
+but no scripts; native `notr` strings remain unchanged. A small adapter populates
+line-edit/plain-text values omitted by quiht-core 1.0.8.
+
+The optional `translation` extra requires `abersetz>=1.1,<2` for glossary and
+example prompt construction and output extraction, together with OpenAI's SDK.
+abersetz 1.1 is not on PyPI yet, so `[tool.uv.sources]` resolves it from the
+sibling checkout `../../github.twardoch/pub/abersetz` as an editable path source;
+that checkout's hatch-vcs version reads `1.0.29.dev0` until the 1.1 tag exists.
+Switch the source back to PyPI once 1.1 is published. The transport calls the
+public `LlmEngine(..., max_attempts=1)` so that each request is one attempt;
+Localizzy owns fallback and cooldown policy. `TRANSPORT_ID` (`abersetz:1.1;…`) is
+part of the translation cache key, so a changed engine version starts a new cache
+entry. No translation engine implementation is vendored.
+
+`formats/qt_numerus.py` holds Qt Linguist's numerus form count per language. It
+was read from qttools `src/linguist/shared/numerus.cpp` (branch 5.15) on
+2026-09-28 and records facts about Qt's behaviour; no Qt code (LGPL/GPL) is
+copied. Language names were mapped to ISO 639 codes with langcodes. Qt's counts
+differ from CLDR plural categories (French 2 and 3, Polish 3 and 4), which is why
+TS preparation uses this table rather than CLDR.
+
+Content QA reuses Python `string.Formatter` and `html.parser`, plus the existing
+polib dependency. Explicit C printf checks require the external GNU gettext
+`msgfmt` executable; no copied C-format parser or new Python package is added.
+Qt-only QA stays in-process. Native acceptance additionally uses Qt `lconvert`
+and `lrelease`; these are validation tools, not bundled runtime dependencies.
+The adapter records actual response models and rejects ambiguous JSON fields.
+
+The optional Node ICU checker pins `@messageformat/parser` 5.1.1 (MIT) with its
+Moo lexer dependency in `icu/package-lock.json`. It uses the published AST and
+retained parser context, not a replacement ICU grammar. Node `Intl.PluralRules`
+supplies locale categories; installations must pin Node/ICU as well as the npm
+artifact. Python's subprocess bridge adds no Python dependency. The checker is
+packaged separately and must be explicitly installed and configured by consumers.
+
+Apple text extraction uses [fonttools/openstep-plist](https://github.com/fonttools/openstep-plist)
+(MIT), a focused parser based on CoreFoundation. Its published `loads(dict_type=...)`
+API was inspected and exercised in isolation before use. A collector preserves
+repeated keys; a dictionary wrapper enforces complete parsing. This avoids copying
+a grammar or stripping comments from inside values. Translate Toolkit was also
+inspected; its generic properties reader has different line-oriented semantics.
+Apple input contracts follow [String Resources](https://developer.apple.com/library/archive/documentation/Cocoa/Conceptual/LoadingResources/Strings/Strings.html)
+and Python's [plistlib API](https://docs.python.org/3/library/plistlib.html).
+
+Fluent projection reuses [fluent.syntax 0.19.0](https://projectfluent.org/python-fluent/fluent.syntax/stable/).
+The published parser, AST shape and serializer helper implementations were
+inspected and exercised before integration. Syntax junk is rejected before
+emitting resource entries; selector expansion is capped before allocating each
+Cartesian product. Existing term/attribute/suffix and whitespace rules remain an
+explicit extraction projection, not a Fluent runtime or native editor.
+
+Properties extraction uses [javaproperties 0.8.2](https://javaproperties.readthedocs.io/en/stable/plain.html)
+(MIT). The published `loads(object_pairs_hook=list)` and unescape implementation
+were inspected and exercised before adoption. Decoded values are independently
+compared with Java [Properties.load(Reader)](https://docs.oracle.com/en/java/javase/11/docs/api/java.base/java/util/Properties.html#load(java.io.Reader)).
+Java is a verification tool, not a runtime requirement.
+
+Mozilla resource extraction uses [moz.l10n 0.14.2](https://github.com/mozilla/moz-l10n)
+(Apache-2.0). Its published `parse_resource`, `Format`, `Entry` and `PatternMessage`
+contracts and parser implementations were inspected and exercised before adoption.
+DTD include declarations become metadata rather than translatable entries and are
+never resolved by this projection. The sources extra additionally resolves
+gitignorant 0.3.1 and iniparse 0.5; existing Fluent/polib dependencies are reused.

vexy_localizzy-1.0.0/LICENSE

@@ -0,0 +1,201 @@
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

vexy_localizzy-1.0.0/NOTICE

@@ -0,0 +1,33 @@
+The bundled browser reviewer uses published React, React DOM, Scheduler,
+DOMPurify, quiht-core and lucide-react. Their license texts are included in
+vexy_localizzy/review/web/THIRD_PARTY_LICENSES.txt and review/public/THIRD_PARTY_LICENSES.txt.
+
+Canonical catalog compatibility types and key/placeholder helpers in
+src/vexy_localizzy/catalog.py and filename planning in
+src/vexy_localizzy/memory/names.py and literal-token QA contracts in
+src/vexy_localizzy/qa/tokens.py and the explicit compatibility projections in
+src/vexy_localizzy/extract/legacy_pairs.py and the plural/device projection in
+src/vexy_localizzy/extract/apple_resources.py and Fluent projection in
+src/vexy_localizzy/extract/fluent_resources.py and the legacy converters in
+src/vexy_localizzy/extract/ are adapted from fl10n, whose project metadata
+identifies FontLab as author and declares the MIT license.
+
+Copyright FontLab
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.