SpinalDoc-RTD/SpinalHDL/Structuring/components_hierarchy

This project is in a trial period, be cautious while contributing. Setup can still change before being approved as a libre project.

Source strings

44	Strings	100%	Browse Translate
508	Words	100%
3,348	Characters	100%

This translation is being used as source strings within this component.

Strings status

Strings Words Characters
44 508 3,348	All strings	Browse Translate Zen
44 508 3,348	Read-only strings	Browse Translate Zen
1 8 31	Strings with any failing checks	Browse Translate Zen
1 8 31	Failing check: Ellipsis	Browse Translate Zen

Overview

Project website	spinalhdl.github.io/SpinalDoc-RTD
Instructions for translators	SpinalHDL的使用说明
Project maintainers	Readon SpinalHDL-CN tsy0123
Translation license	Creative Commons Zero v1.0 Universal
Translation process	Translations can be made directly. Translation suggestions can be made. Translations are reviewed by dedicated reviewers. Any authenticated user can contribute. The translation uses bilingual files.
Source code repository	`git@github.com:SpinalHDL-CN/SpinalDoc-RTD.git`
Repository branch	master
Last remote commit	update .pot files `26b7610fd` GiHub Action Bot authored 13 days ago
Last commit in Weblate	Translated using Weblate (Chinese (Simplified)) `a01cb3fbd` Readon authored 6 months ago
Weblate repository	`https://hosted.weblate.org/git/spinaldoc-rtd/index/`
File mask	`source/locale/*/LC_MESSAGES/SpinalHDL/Structuring/components_hierarchy.po`
Translation file	Download `source/locale/gettext/SpinalHDL/Structuring/components_hierarchy.pot`
Last change	Jan. 2, 2024, 5:09 p.m.
Last author	None

13 days ago

String statistics

	Strings percent	Hosted strings	Words percent	Hosted words	Characters percent	Hosted characters
Total		44		508		3,348
Approved	0%	0	0%	0	0%	0
Waiting for review	0%	0	0%	0	0%	0
Translated	100%	44	100%	508	100%	3,348
Needs editing	0%	0	0%	0	0%	0
Read-only	100%	44	100%	508	100%	3,348
Failing checks	2%	1	1%	8	1%	31
Strings with suggestions	0%	0	0%	0	0%	0
Untranslated strings	0%	0	0%	0	0%	0

Last 12 months Previous

Activity in last 12 months


Jun	Jul	Aug	Sep	Oct	Nov	Dec	Jan	Feb	Mar	Apr	May

Quick numbers

508

Hosted words

Hosted strings

100%

Translated

Contributors

and previous 30 days

Trends of last 30 days

—

Hosted words

+100%

—

Hosted strings

+100%

—

Translated

+100%

—

Contributors

—

None Resource updated SpinalDoc-RTD SpinalHDL/Structuring/components_hierarchy English	The “`source/locale/gettext/SpinalHDL/Structuring/components_hierarchy.pot`” file was changed. 5 months ago
None Resource updated SpinalDoc-RTD SpinalHDL/Structuring/components_hierarchy English	The “`source/locale/gettext/SpinalHDL/Structuring/components_hierarchy.pot`” file was changed. 6 months ago
None Resource updated SpinalDoc-RTD SpinalHDL/Structuring/components_hierarchy English	File “`source/locale/template/SpinalHDL/Structuring/components_hierarchy.pot`” was added. 6 months ago
None String updated in the repository SpinalDoc-RTD SpinalHDL/Structuring/components_hierarchy English	English When synthesized, each module gets the name of the Scala class defining it. You can override this as well with ``setDefinitionName``. English 133 characters edited Current translation Read only When synthesized, each module gets the name of the Scala class defining it. You can override this as well with ``setDefinitionName``. 6 months ago
None String updated in the repository SpinalDoc-RTD SpinalHDL/Structuring/components_hierarchy English	English Within a module, each component has a name, called a "partial name". The "full" name is built by joining every component's parent name with "_", for example: ``io_clockDomain_reset``. You can use ``setName`` to replace this convention with a custom name. This is especially useful when interfacing with external components. The other methods are called ``getName``, ``setPartialName``, and ``getPartialName`` respectively. English 422 characters edited Current translation Read only Within a module, each component has a name, called a "partial name". The "full" name is built by joining every component's parent name with "_", for example: ``io_clockDomain_reset``. You can use ``setName`` to replace this convention with a custom name. This is especially useful when interfacing with external components. The other methods are called ``getName``, ``setPartialName``, and ``getPartialName`` respectively. 6 months ago
None String updated in the repository SpinalDoc-RTD SpinalHDL/Structuring/components_hierarchy English	English Synthesized component names English 27 characters edited Current translation Read only Synthesized component names 6 months ago
None String updated in the repository SpinalDoc-RTD SpinalHDL/Structuring/components_hierarchy English	English See also :ref:`Blackbox <blackbox>` for more information around support for that mechanism. English 91 characters edited Current translation Read only See also :ref:`Blackbox <blackbox>` for more information around support for that mechanism. 6 months ago
None String updated in the repository SpinalDoc-RTD SpinalHDL/Structuring/components_hierarchy English	English This parametrization occurs entirely within the SpinalHDL code-generation during elaboration. This generates non-generic HDL code. The methods described here do not use VHDL generics or Verilog parameters. English 206 characters edited Current translation Read only This parametrization occurs entirely within the SpinalHDL code-generation during elaboration. This generates non-generic HDL code. The methods described here do not use VHDL generics or Verilog parameters. 6 months ago
None String updated in the repository SpinalDoc-RTD SpinalHDL/Structuring/components_hierarchy English	English You can add functions inside the config, along with requirements on the config attributes: English 90 characters edited Current translation Read only You can add functions inside the config, along with requirements on the config attributes: 6 months ago
None String updated in the repository SpinalDoc-RTD SpinalHDL/Structuring/components_hierarchy English	English If you have several parameters, it is a good practice to give a specific configuration class as follows: English 104 characters edited Current translation Read only If you have several parameters, it is a good practice to give a specific configuration class as follows: 6 months ago

Browse all translation changes

Quick downloads

44	File in original format as translated in the repository	gettext PO file
44	All strings, converted files enriched with comments; suitable for offline translation	CSV	gettext MO	gettext PO	TBX	TMX	XLIFF 1.1 with gettext extensions	XLIFF 1.1	XLSX

Customize download

Search

Advanced query builder

Query examples

Review strings changed by other users	`changed:>=2024-05-27 AND NOT changed_by:anonymous`	Add
Translated strings	`state:>=translated`	Add
Strings with comments	`has:comment`	Add
Strings with any failing checks	`has:check`	Add
Strings with suggestions from others	`has:suggestion AND NOT suggestion_author:anonymous`	Add
Approved strings with suggestions	`state:approved AND has:suggestion`	Add
All untranslated strings added the past month	`added:>=2024-05-27 AND state:<=needs-editing`	Add