cnp3-ebook

principles/naming

	Language	Translated	Unfinished	Unfinished words	Unfinished characters	Untranslated	Checks	Suggestions	Comments
	English CC-BY-SA-3.0		0	0	0	0	1	0	0

	Chinese (Simplified) CC-BY-SA-3.0	9%	28	1,703	10,837	28	0	0	0

	Czech CC-BY-SA-3.0	0%	31	1,900	12,068	31	0	0	0

	French CC-BY-SA-3.0		0	0	0	0	1	0	0

	Vietnamese CC-BY-SA-3.0	41%	18	813	5,282	18	1	0	0

Please sign in to see the alerts.

Overview

Project website	www.computer-networking.info
Project maintainers	obonaventure qdeconinck
Translation process	Translations can be made directly. Translation suggestions can be made. Any authenticated user can contribute. The translation uses bilingual files.
Translation license	Creative Commons Attribution Share Alike 3.0 Unported
Source code repository	`https://github.com/cnp3/ebook`
Repository branch	master
Last remote commit	Merge pull request #128 from aaaaalbert/fix-typos-in-preface `00ed7a4` Olivier Bonaventure authored 8 months ago
Weblate repository	`https://weblate.info.ucl.ac.be/git/cnp3-ebook/index/`
File mask	`locale/*/LC_MESSAGES/principles/naming.po`

String statistics

	Strings percent	Hosted strings	Words percent	Hosted words	Characters percent	Hosted characters
Total		162		10,357		65,621
Source		38		2,757		17,349
Translated	52%	85	57%	5,941	57%	37,434
Needs editing	0%	0	0%	0	0%	0
Read-only	23%	38	26%	2,757	26%	17,349
Failing checks	1%	3	1%	131	1%	791
Strings with suggestions	0%	0	0%	0	0%	0
Untranslated strings	47%	77	42%	4,416	42%	28,187

Last 12 months Previous

Activity in last 12 months


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

Quick numbers

10,357

Hosted words

162

Hosted strings

52%

Translated

1

Contributors

and previous 30 days

Trends of last 30 days

—

Hosted words

—

—

Hosted strings

—

—

Translated

—

+100%

Contributors

—

Search

Advanced query builder

Query examples

Review strings changed by other users	`changed:>=2023-05-04 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:>=2023-05-04 AND state:<=needs-editing`	Add
Translated strings in a certain language	`is:translated AND language:en`	Add

None Component unlocked cnp3-ebook / principles/naming	Fixing an alert automatically unlocked the component. 11 days ago
None Component locked cnp3-ebook / principles/naming	The component was automatically locked because of an alert. 11 days ago
None New alert cnp3-ebook / principles/naming	Could not update the repository. 11 days ago
None Component unlocked cnp3-ebook / principles/naming	Fixing an alert automatically unlocked the component. 2 months ago
None Component locked cnp3-ebook / principles/naming	The component was automatically locked because of an alert. 2 months ago
None New alert cnp3-ebook / principles/naming	Could not update the repository. 2 months ago
None Resource update cnp3-ebook / principles/naming — English	File `locale/pot/principles/naming.pot` was added. 8 months ago
None String updated in the repository cnp3-ebook / principles/naming — English	English Until February 2008, the root DNS servers only had IPv4 addresses. IPv6 addresses were slowly added to the root DNS servers to avoid creating problems as discussed in http://www.icann.org/en/committees/security/sac018.pdf As of February 2021, there remain a few DNS root servers that are still not reachable using IPv6. The full list is available at http://www.root-servers.org/ English 378 characters edited Current translation Read only Until February 2008, the root DNS servers only had IPv4 addresses. IPv6 addresses were slowly added to the root DNS servers to avoid creating problems as discussed in http://www.icann.org/en/committees/security/sac018.pdf As of February 2021, there remain a few DNS root servers that are still not reachable using IPv6. The full list is available at http://www.root-servers.org/ 8 months ago
None String updated in the repository cnp3-ebook / principles/naming — English	English Names provide a lot of flexibility compared to addresses. For the network, they play a similar role as variables in programming languages. No programmer using a high-level programming language would consider using hardcoded values instead of variables. For the same reasons, all networked applications should depend on names and avoid dealing with addresses as much as possible. English 378 characters edited Current translation Read only Names provide a lot of flexibility compared to addresses. For the network, they play a similar role as variables in programming languages. No programmer using a high-level programming language would consider using hardcoded values instead of variables. For the same reasons, all networked applications should depend on names and avoid dealing with addresses as much as possible. 8 months ago
None String updated in the repository cnp3-ebook / principles/naming — English	English Mapping a single name onto a set of addresses allows popular servers to dynamically scale. There are also benefits in mapping multiple names, possibly a large number of them, onto a single address. Consider the case of information servers run by individuals or SMEs. Some of these servers attract only a few clients per day. Using a single physical server for each of these services would be a waste of resources. A better approach is to use a single server for a set of services that are all identified by different names. This enables service providers to support a large number of servers processes, identified by different names, onto a single physical server. If one of these server processes becomes very popular, it will be possible to map its name onto a set of addresses to be able to sustain the load. There are some deployments where this mapping is done dynamically in function of the load. English 902 characters edited Current translation Read only Mapping a single name onto a set of addresses allows popular servers to dynamically scale. There are also benefits in mapping multiple names, possibly a large number of them, onto a single address. Consider the case of information servers run by individuals or SMEs. Some of these servers attract only a few clients per day. Using a single physical server for each of these services would be a waste of resources. A better approach is to use a single server for a set of services that are all identified by different names. This enables service providers to support a large number of servers processes, identified by different names, onto a single physical server. If one of these server processes becomes very popular, it will be possible to map its name onto a set of addresses to be able to sustain the load. There are some deployments where this mapping is done dynamically in function of the load. 8 months ago

Browse all component changes