cnp3-ebook/principles/referencemodels

Source strings

44	Strings		100%	Browse Translate
1,407	Words		100%	Browse Translate

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

Strings status

44		All strings — 1,407 words	Browse Translate Zen
44		Read-only strings — 1,407 words	Browse Translate Zen

Other components

Component	Unfinished	Unfinished words	Unfinished characters	Untranslated	Checks	Suggestions	Comments
exercises/ex-sharing CC-BY-SA-3.0	0	0	0	0	0	0	0

exercises/intro CC-BY-SA-3.0	0	0	0	0	0	0	0

exercises/reliability CC-BY-SA-3.0	0	0	0	0	0	0	0

exercises/transport CC-BY-SA-3.0	0	0	0	0	0	0	0

principles/naming CC-BY-SA-3.0	0	0	0	0	1	0	0

principles/security CC-BY-SA-3.0	0	0	0	0	1	0	0

exercises/dns CC-BY-SA-3.0	0	0	0	0	3	0	0

exercises/http CC-BY-SA-3.0	0	0	0	0	0	0	0

exercises/lan CC-BY-SA-3.0	0	0	0	0	0	0	0

exercises/routing-protocols CC-BY-SA-3.0	0	0	0	0	0	0	0

Browse all components

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 #126 from INGIbot/weblate-cnp3-ebook-index `d9f8d8f` Olivier Bonaventure authored 7 months ago
Weblate repository	`https://weblate.info.ucl.ac.be/git/cnp3-ebook/index/`
File mask	`locale/*/LC_MESSAGES/principles/referencemodels.po`
Translation file	Download `locale/pot/principles/referencemodels.pot`
Last change	None
Last author	None

String statistics

	Strings percent	Hosted strings	Words percent	Hosted words	Characters percent	Hosted characters
Total		44		1,407		9,088
Translated	100%	44	100%	1,407	100%	9,088
Needs editing	0%	0	0%	0	0%	0
Read-only	100%	44	100%	1,407	100%	9,088
Failing checks	0%	0	0%	0	0%	0
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


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

Quick numbers

1,407

Hosted words

Hosted strings

100%

Translated

Contributors

and previous 30 days

Trends of last 30 days

—

Hosted words

—

Hosted strings

—

Translated

—

Contributors

—

None Resource update cnp3-ebook / principles/referencemodels — English	File `locale/pot/principles/referencemodels.pot` was added. 2 years ago
None String updated in the repository cnp3-ebook / principles/referencemodels — English	English the `Presentation layer` was designed to cope with the different ways of representing information on computers. There are many differences in the way computer store information. Some computers store integers as 32 bits field, others use 64 bits field and the same problem arises with floating point number. For textual information, this is even more complex with the many different character codes that have been used [#funicode]_. The situation is even more complex when considering the exchange of structured information such as database records. To solve this problem, the Presentation layer provides a common representation of the data transferred. The :term:`ASN.1` notation was designed for the Presentation layer and is still used today by some protocols. English 762 characters edited Current translation Read only the `Presentation layer` was designed to cope with the different ways of representing information on computers. There are many differences in the way computer store information. Some computers store integers as 32 bits field, others use 64 bits field and the same problem arises with floating point number. For textual information, this is even more complex with the many different character codes that have been used [#funicode]_. The situation is even more complex when considering the exchange of structured information such as database records. To solve this problem, the Presentation layer provides a common representation of the data transferred. The :term:`ASN.1` notation was designed for the Presentation layer and is still used today by some protocols. 2 years ago
None String updated in the repository cnp3-ebook / principles/referencemodels — English	English the `Session layer`. The Session layer contains the protocols and mechanisms that are necessary to organize and to synchronize the dialogue and to manage the data exchange of presentation layer entities. While one of the main functions of the transport layer is to cope with the unreliability of the network layer, the session's layer objective is to hide the possible failures of transport-level connections to the upper layer higher. For this, the Session Layer provides services that allow establishing a session-connection, to support in-order data exchange (including mechanisms that allow recovering from the abrupt release of an underlying transport connection), and to release the connection in an orderly manner. English 721 characters edited Current translation Read only the `Session layer`. The Session layer contains the protocols and mechanisms that are necessary to organize and to synchronize the dialogue and to manage the data exchange of presentation layer entities. While one of the main functions of the transport layer is to cope with the unreliability of the network layer, the session's layer objective is to hide the possible failures of transport-level connections to the upper layer higher. For this, the Session Layer provides services that allow establishing a session-connection, to support in-order data exchange (including mechanisms that allow recovering from the abrupt release of an underlying transport connection), and to release the connection in an orderly manner. 2 years ago
None String updated in the repository cnp3-ebook / principles/referencemodels — English	English In contrast with OSI, the TCP/IP community did not spend a lot of effort defining a detailed reference model; in fact, the goals of the Internet architecture were only documented after TCP/IP had been deployed [Clark88]_. :rfc:`1122`, which defines the requirements for Internet hosts, mentions four different layers. Starting from the top, these are : English 352 characters edited Current translation Read only In contrast with OSI, the TCP/IP community did not spend a lot of effort defining a detailed reference model; in fact, the goals of the Internet architecture were only documented after TCP/IP had been deployed [Clark88]_. :rfc:`1122`, which defines the requirements for Internet hosts, mentions four different layers. Starting from the top, these are : 2 years ago
None String updated in the repository cnp3-ebook / principles/referencemodels — English	English There are different types of transport layers. The most widely used transport layers on the Internet are :term:`TCP`, that provides a reliable connection-oriented bytestream transport service, and :term:`UDP`, that provides an unreliable connection-less transport service. English 272 characters edited Current translation Read only There are different types of transport layers. The most widely used transport layers on the Internet are :term:`TCP`, that provides a reliable connection-oriented bytestream transport service, and :term:`UDP`, that provides an unreliable connection-less transport service. 2 years ago
None String updated in the repository cnp3-ebook / principles/referencemodels — English	English The network layer enables hosts to reach each others. However, different communication flows can take place between the same hosts. These communication flows might have different needs (some require reliable delivery, other not) and need to be distinguished. Ensuring an identification of a communication flow between two given hosts is the task of the `transport layer`. `Transport layer` entities exchange `segments`. A segment is a finite sequence of bytes that are transported inside one or more packets. A transport layer entity issues segments (or sometimes part of segments) as `Data.request` to the underlying network layer entity. English 639 characters edited Current translation Read only The network layer enables hosts to reach each others. However, different communication flows can take place between the same hosts. These communication flows might have different needs (some require reliable delivery, other not) and need to be distinguished. Ensuring an identification of a communication flow between two given hosts is the task of the `transport layer`. `Transport layer` entities exchange `segments`. A segment is a finite sequence of bytes that are transported inside one or more packets. A transport layer entity issues segments (or sometimes part of segments) as `Data.request` to the underlying network layer entity. 2 years ago
None String updated in the repository cnp3-ebook / principles/referencemodels — English	English An important point to note about the Physical layer is the service that it provides. This service is usually an unreliable service that allows the users of the Physical layer to exchange bits. The unit of information transfer in the Physical layer is the bit. The Physical layer service is unreliable because : English 310 characters edited Current translation Read only An important point to note about the Physical layer is the service that it provides. This service is usually an unreliable service that allows the users of the Physical layer to exchange bits. The unit of information transfer in the Physical layer is the bit. The Physical layer service is unreliable because : 2 years 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-10-22 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-10-22 AND state:<=needs-editing`	Add