Documentation/books/arch-handbook/scsi/

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

Chinese (Simplified) (zh_CN) BSD-2-Clause	22%	278	7,507	55,903	203	22	0	0

Chinese (Traditional) (zh_TW) BSD-2-Clause	1%	356	8,562	62,236	356	1	0	0

Dutch (nl_NL) BSD-2-Clause	0%	358	8,564	62,246	358	0	0	0

French BSD-2-Clause	0%	358	8,564	62,246	358	0	0	0

French (fr_FR) BSD-2-Clause	0%	358	8,564	62,246	358	0	0	0

German (de_DE) BSD-2-Clause	0%	358	8,564	62,246	358	0	0	0

Greek BSD-2-Clause	1%	357	8,563	62,238	357	1	0	0

Indonesian BSD-2-Clause	0%	358	8,564	62,246	358	0	0	0

Italian (it_IT) BSD-2-Clause	1%	356	8,562	62,236	356	1	0	0

Korean BSD-2-Clause	1%	355	8,557	62,199	355	1	0	0

Norwegian Bokmål BSD-2-Clause	0%	358	8,564	62,246	358	0	0	0

Persian BSD-2-Clause	1%	356	8,562	62,236	356	1	0	0

Polish BSD-2-Clause	1%	357	8,563	62,238	357	1	0	0

Portuguese BSD-2-Clause	0%	358	8,564	62,246	358	0	0	0

Portuguese (Brazil) BSD-2-Clause	1%	356	8,562	62,236	339	13	0	0

Spanish BSD-2-Clause	1%	356	8,562	62,236	356	0	0	0

Turkish (tr_TR) BSD-2-Clause	0%	358	8,564	62,246	358	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/scsi/_index.po`

String statistics

	Strings percent	Hosted strings	Words percent	Hosted words	Characters percent	Hosted characters
Total		6,444		154,152		1,120,428
Source		358		8,564		62,246
Translated	7%	453	6%	9,640	6%	68,702
Needs editing	1%	92	2%	4,198	2%	28,925
Read-only	5%	358	5%	8,564	5%	62,246
Failing checks	1%	58	1%	1,389	1%	12,074
Strings with suggestions	0%	0	0%	0	0%	0
Untranslated strings	91%	5,899	91%	140,314	91%	1,022,801

Last 12 months Previous

Activity in last 12 months


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

Quick numbers

145 k

Hosted words

6,086

Hosted strings

Translated

Contributors

and previous 30 days

Trends of last 30 days

—

Hosted words

+100%

—

Hosted strings

+100%

—

Translated

+7%

—

Contributors

—

Search

Advanced query builder

Query examples

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

None Committed changes Documentation / books/arch-handbook/scsi/_index — French	Committed changes yesterday
None New strings to translate Documentation / books/arch-handbook/scsi/_index — French	358 new strings to translate appeared to the translation. yesterday
None Resource update Documentation / books/arch-handbook/scsi/_index — French	File `documentation/content/fr/books/arch-handbook/scsi/_index.po` was added. yesterday
None String updated in the repository Documentation / books/arch-handbook/scsi/_index — French	English When we abort a request all the other disconnected requests to the same target/LUN get aborted too. So there appears a question, should we return them with status CAM_REQ_ABORTED or CAM_CMD_TIMEOUT? The current drivers use CAM_CMD_TIMEOUT. This seems logical because if one request got timed out then probably something really bad is happening to the device, so if they would not be disturbed they would time out by themselves. French 0 characters edited Current translation yesterday
None String updated in the repository Documentation / books/arch-handbook/scsi/_index — French	English if (hcb->flags & HCB_BEING_ABORTED \|\| ccb_h->func_code == XPT_RESET_DEV) { xxx_reset_bus(softc); } else { xxx_abort_ccb(hcb->ccb, CAM_CMD_TIMEOUT); } } French 0 characters edited Current translation yesterday
None String updated in the repository Documentation / books/arch-handbook/scsi/_index — French	English softc = hcb->softc; ccb_h = &hcb->ccb->ccb_h; French 0 characters edited Current translation yesterday
None String updated in the repository Documentation / books/arch-handbook/scsi/_index — French	English static void xxx_timeout(void arg) { struct xxx_hcb hcb = (struct xxx_hcb )arg; struct xxx_softc softc; struct ccb_hdr *ccb_h; French 0 characters edited Current translation yesterday
None String updated in the repository Documentation / books/arch-handbook/scsi/_index — French	English When the timeout for an HCB expires that request should be aborted, just like with an XPT_ABORT request. The only difference is that the returned status of aborted request should be CAM_CMD_TIMEOUT instead of CAM_REQ_ABORTED (that is why implementation of the abort better be done as a function). But there is one more possible problem: what if the abort request itself will get stuck? In this case the SCSI bus should be reset, just like with an XPT_RESET_BUS request (and the idea about implementing it as a function called from both places applies here too). Also we should reset the whole SCSI bus if a device reset request got stuck. So after all the timeout function would look like: French 0 characters edited Current translation yesterday
None String updated in the repository Documentation / books/arch-handbook/scsi/_index — French	English Timeout Handling French 0 characters edited Current translation yesterday
None String updated in the repository Documentation / books/arch-handbook/scsi/_index — French	English _CAM_TID_INVALID_ - the target ID in the request is not supported by the SCSI controller French 0 characters edited Current translation yesterday

Browse all component changes