Documentation/books/arch-handbook/usb/

Language	Translated	Unfinished	Unfinished words	Unfinished characters	Untranslated	Checks	Suggestions	Comments
English BSD-2-Clause		0	0	0	0	10	0	0

Chinese (Simplified) (zh_CN) BSD-2-Clause	85%	11	422	3,014	7	5	0	0

Chinese (Traditional) (zh_TW) BSD-2-Clause	1%	76	4,374	27,146	76	0	0	0

Dutch (nl_NL) BSD-2-Clause	1%	76	4,374	27,146	76	0	0	0

French (fr_FR) BSD-2-Clause	1%	76	4,374	27,146	76	0	0	0

German (de_DE) BSD-2-Clause	1%	76	4,374	27,146	76	0	0	0

Greek BSD-2-Clause	1%	76	4,374	27,146	76	0	0	0

Indonesian BSD-2-Clause	1%	76	4,374	27,146	76	0	0	0

Italian (it_IT) BSD-2-Clause	1%	76	4,374	27,146	76	0	0	0

Korean BSD-2-Clause	2%	75	4,370	27,124	75	0	0	0

Norwegian Bokmål BSD-2-Clause	1%	76	4,374	27,146	76	0	0	0

Persian BSD-2-Clause	1%	76	4,374	27,146	76	0	0	0

Polish BSD-2-Clause	1%	76	4,374	27,146	76	0	0	0

Portuguese BSD-2-Clause	0%	77	4,375	27,158	77	0	0	0

Portuguese (Brazil) BSD-2-Clause	1%	76	4,374	27,146	76	0	0	0

Spanish BSD-2-Clause	1%	76	4,374	27,146	76	0	0	0

Turkish (tr_TR) BSD-2-Clause	0%	77	4,375	27,158	77	0	0	0

Please sign in to see the alerts.

Overview

Project website	docs.freebsd.org/en
Translation license	BSD 2-Clause "Simplified" License
Translation process	Translations can be made directly. Translation suggestions can be made. Only chosen users can contribute. The translation uses bilingual files.
File mask	`documentation/content/*/books/arch-handbook/usb/_index.po`

String statistics

	Strings percent	Hosted strings	Words percent	Hosted words	Characters percent	Hosted characters
Total		1,309		74,375		461,686
Source		77		4,375		27,158
Translated	11%	157	11%	8,345	11%	51,480
Needs editing	1%	4	1%	333	1%	2,037
Read-only	5%	77	5%	4,375	5%	27,158
Failing checks	1%	15	1%	768	1%	5,158
Strings with suggestions	0%	0	0%	0	0%	0
Untranslated strings	87%	1,148	88%	65,697	88%	408,169

Last 12 months Previous

Activity in last 12 months


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

Quick numbers

74,375

Hosted words

1,309

Hosted strings

11%

Translated

Contributors

and previous 30 days

Trends of last 30 days

+5%

Hosted words

+100%

+5%

Hosted strings

+100%

−1%

Translated

+12%

+100%

Contributors

—

Search

Advanced query builder

Query examples

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

None Committed changes Documentation / books/arch-handbook/usb/_index — Portuguese	Committed changes 3 weeks ago
None New strings to translate Documentation / books/arch-handbook/usb/_index — Portuguese	77 new strings to translate appeared to the translation. 3 weeks ago
None Resource update Documentation / books/arch-handbook/usb/_index — Portuguese	File `documentation/content/pt/books/arch-handbook/usb/_index.po` was added. 3 weeks ago
None String updated in the repository Documentation / books/arch-handbook/usb/_index — Portuguese	English The support for the USB floppy from Y-E Data is again less straightforward as a new command set has been designed. Portuguese 0 characters edited Current translation 3 weeks ago
None String updated in the repository Documentation / books/arch-handbook/usb/_index — Portuguese	English The Mass Storage Specification supports 2 different types of wrapping of the command block.The initial attempt was based on sending the command and status through the default pipe and using bulk transfers for the data to be moved between the host and the device. Based on experience a second approach was designed that was based on wrapping the command and status blocks and sending them over the bulk out and in endpoint. The specification specifies exactly what has to happen when and what has to be done in case an error condition is encountered. The biggest challenge when writing drivers for these devices is to fit USB based protocol into the existing support for mass storage devices. CAM provides hooks to do this in a fairly straight forward way. ATAPI is less simple as historically the IDE interface has never had many different appearances. Portuguese 0 characters edited Current translation 3 weeks ago
None String updated in the repository Documentation / books/arch-handbook/usb/_index — Portuguese	English Example: Mass Storage Devices Support for mass storage devices is mainly built around existing protocols. The Iomega USB Zipdrive is based on the SCSI version of their drive. The SCSI commands and status messages are wrapped in blocks and transferred over the bulk pipes to and from the device, emulating a SCSI controller over the USB wire. ATAPI and UFI commands are supported in a similar fashion. Portuguese 0 characters edited Current translation 3 weeks ago
None String updated in the repository Documentation / books/arch-handbook/usb/_index — Portuguese	English An example of these types of devices is the ActiveWire I/O board, based on the EZ-USB chip. For this chip a generic firmware downloader is available. The firmware downloaded into the ActiveWire board changes the revision Id. It will then perform a soft reset of the USB part of the EZ-USB chip to disconnect from the USB bus and again reconnect. Portuguese 0 characters edited Current translation 3 weeks ago
None String updated in the repository Documentation / books/arch-handbook/usb/_index — Portuguese	English The procedure followed is straightforward. The device identifies itself through a vendor and product Id. The first driver probes and attaches to it and downloads the firmware into it. After that the device soft resets itself and the driver is detached. After a short pause the device announces its presence on the bus. The device will have changed its vendor/product/revision Id to reflect the fact that it has been supplied with firmware and as a consequence a second driver will probe it and attach to it. Portuguese 0 characters edited Current translation 3 weeks ago
None String updated in the repository Documentation / books/arch-handbook/usb/_index — Portuguese	English Example: Firmware download Many devices that have been developed are based on a general purpose processor with an additional USB core added to it. Since the development of drivers and firmware for USB devices is still very new, many devices require the downloading of the firmware after they have been connected. Portuguese 0 characters edited Current translation 3 weeks ago
None String updated in the repository Documentation / books/arch-handbook/usb/_index — Portuguese	English For example audio speakers provide endpoints to the digital to analogue converters and possibly an extra pipe for a microphone. They also provide a HID endpoint in a separate interface for the buttons and dials on the front of the device. The same is true for the monitor control class. It is straightforward to build support for these interfaces through the available kernel and userland libraries together with the HID class driver or the generic driver. Another device that serves as an example for interfaces within one configuration driven by different device drivers is a cheap keyboard with built-in legacy mouse port. To avoid having the cost of including the hardware for a USB hub in the device, manufacturers combined the mouse data received from the PS/2 port on the back of the keyboard and the key presses from the keyboard into two separate interfaces in the same configuration. The mouse and keyboard drivers each attach to the appropriate interface and allocate the pipes to the two independent endpoints. Portuguese 0 characters edited Current translation 3 weeks ago

Browse all component changes