markdown: **Tim Teabagging** đến **Tince** [Tim Teabagging](/define.php?term=Tim%20Teabagging) [Tim Tebag-ged](/define.php?term=Tim%20Tebag-ged) [Tim Teblow](/define.php?term=Tim%20Teblow) [Tim Tebow](/define.php?term=Tim%20Tebow) [Tim Tebowed](/define.php?term=Tim%20Tebowed) [Tim Tebowing](/define.php?term=Tim%20Tebowing) [tim tebowism](/define.php?term=tim%20tebowism) [Tim Tebow-ner](/define.php?term=Tim%20Tebow-ner) [Tim Te-bro](/define.php?term=Tim%20Te-bro) [Tim the Enchanter](/define.php?term=Tim%20the%20Enchanter) [Tim Thibeault](/define.php?term=Tim%20Thibeault) [Tim Thomas](/define.php?term=Tim%20Thomas) [Tim Thomased](/define.php?term=Tim%20Thomased) [Tim Thomas (the white one that plays hockey)](/define.php?term=Tim%20Thomas%20%28the%20white%20one%20that%20plays%20hockey%29) [Tim-tim](/define.php?term=Tim-tim) [tim-tim land](/define.php?term=tim-tim%20land) [tim-ti's](/define.php?term=tim-ti%27s) [timtits](/define.php?term=timtits) [TIMTOWDI](/define.php?term=TIMTOWDI) [Tim Town](/define.php?term=Tim%20Town) [TIMTOWTDI](/define.php?term=TIMTOWTDI) [Tim Tranker](/define.php?term=Tim%20Tranker) [Tim Trees](/define.php?term=Tim%20Trees) [Timtron](/define.php?term=Timtron) [Timtrum](/define.php?term=Timtrum) [Timucin](/define.php?term=Timucin) [Timuik](/define.php?term=Timuik) [Timukizulu](/define.php?term=Timukizulu) [timulsameous](/define.php?term=timulsameous) [Tim Uppal](/define.php?term=Tim%20Uppal) [timur](/define.php?term=timur) [Timura](/define.php?term=Timura) [Tim Urban](/define.php?term=Tim%20Urban) [timur bekmambetov](/define.php?term=timur%20bekmambetov) [timuring](/define.php?term=timuring) [timus](/define.php?term=timus) [TimW](/define.php?term=TimW) [Timwad](/define.php?term=Timwad) [Tim Wakefield](/define.php?term=Tim%20Wakefield) [Tim Wallaced](/define.php?term=Tim%20Wallaced) [tim wheeler](/define.php?term=tim%20wheeler) [Timwhore](/define.php?term=Timwhore) [tim whoretons](/define.php?term=tim%20whoretons) [Tim Wiklund](/define.php?term=Tim%20Wiklund) [Tim willis](/define.php?term=Tim%20willis) [Tim Wilson](/define.php?term=Tim%20Wilson) [Tim Wolff](/define.php?term=Tim%20Wolff) [Tim Wong](/define.php?term=Tim%20Wong) [tim wood](/define.php?term=tim%20wood) [TIMWYKING](/define.php?term=TIMWYKING) [Timy](/define.php?term=Timy) [timya](/define.php?term=timya) [tim yadig](/define.php?term=tim%20yadig) [Tim Yap](/define.php?term=Tim%20Yap) [timycka](/define.php?term=timycka) [Timyka](/define.php?term=Timyka) [Timz](/define.php?term=Timz) [Tim Zukas](/define.php?term=Tim%20Zukas) [Tin](/define.php?term=Tin) [tina](/define.php?term=tina) [Tina B](/define.php?term=Tina%20B) [TinaBarb](/define.php?term=TinaBarb) [tina bing bong](/define.php?term=tina%20bing%20bong) [tinabock](/define.php?term=tinabock) [Tinaca'd](/define.php?term=Tinaca%27d) [tinactin](/define.php?term=tinactin) [Tina'D](/define.php?term=Tina%27D) [Tina Day](/define.php?term=Tina%20Day) [Tina dick](/define.php?term=Tina%20dick) [Tina Fey](/define.php?term=Tina%20Fey) [Tina Fey-cial](/define.php?term=Tina%20Fey-cial) [Tina Fey Effect](/define.php?term=Tina%20Fey%20Effect) [Tina Fey Glasses](/define.php?term=Tina%20Fey%20Glasses) [TINAFHHIAL](/define.php?term=TINAFHHIAL) [tina friendly](/define.php?term=tina%20friendly) [tinaglia](/define.php?term=tinaglia) [Tinahead](/define.php?term=Tinahead) [Tinaje](/define.php?term=Tinaje) [Tinajero](/define.php?term=Tinajero) [Tinajia](/define.php?term=Tinajia) [tinakins](/define.php?term=tinakins) [Tina Knowles](/define.php?term=Tina%20Knowles) [tina lambchop](/define.php?term=tina%20lambchop) [Tina Lansdell](/define.php?term=Tina%20Lansdell) [Tinaly](/define.php?term=Tinaly) [tinam](/define.php?term=tinam) [Tina Majorino](/define.php?term=Tina%20Majorino) [tin and stock](/define.php?term=tin%20and%20stock) [tinaness](/define.php?term=tinaness) [Tinant](/define.php?term=Tinant) [Tina or tommy turbine](/define.php?term=Tina%20or%20tommy%20turbine) [tinap](/define.php?term=tinap) [Tina Palin Syndrome](/define.php?term=Tina%20Palin%20Syndrome) [Tina Pham](/define.php?term=Tina%20Pham) [Tinara](/define.php?term=Tinara) [tina-rooneyed](/define.php?term=tina-rooneyed) [Tin-arse](/define.php?term=Tin-arse) [TINART](/define.php?term=TINART) [Tina Sanchez](/define.php?term=Tina%20Sanchez) [Tina's and Larry's](/define.php?term=Tina%27s%20and%20Larry%27s) [Tinasaur](/define.php?term=Tinasaur) [Tina's Cookies](/define.php?term=Tina%27s%20Cookies) [Tinashe](/define.php?term=Tinashe) [tin ass](/define.php?term=tin%20ass) [tina terror](/define.php?term=tina%20terror) [tinatinaland](/define.php?term=tinatinaland) [Tina tits](/define.php?term=Tina%20tits) [Tina Tornado](/define.php?term=Tina%20Tornado) [Tina Tough Tits](/define.php?term=Tina%20Tough%20Tits) [Tinatounge](/define.php?term=Tinatounge) [Tina towel party](/define.php?term=Tina%20towel%20party) [TINA TRAN](/define.php?term=TINA%20TRAN) [Tina tummy ache](/define.php?term=Tina%20tummy%20ache) [Tina Turner](/define.php?term=Tina%20Turner) [tina turnup](/define.php?term=tina%20turnup) [Tina Twink](/define.php?term=Tina%20Twink) [Tina Weymouth](/define.php?term=Tina%20Weymouth) [tina whore](/define.php?term=tina%20whore) [Tinawky](/define.php?term=Tinawky) [Tina Wong](/define.php?term=Tina%20Wong) [Tinaz](/define.php?term=Tinaz) [Tinball Wizard](/define.php?term=Tinball%20Wizard) [tin banana](/define.php?term=tin%20banana) [Tinbang](/define.php?term=Tinbang) [Tin banger](/define.php?term=Tin%20banger) [tin bed](/define.php?term=tin%20bed) [Tinbeef](/define.php?term=Tinbeef) [Tin Bin](/define.php?term=Tin%20Bin) [tin bitch](/define.php?term=tin%20bitch) [t'in b's](/define.php?term=t%27in%20b%27s) [Tin Bucketing](/define.php?term=Tin%20Bucketing) [tinc](/define.php?term=tinc) [Tin Can](/define.php?term=Tin%20Can) [Tin Can Bay](/define.php?term=Tin%20Can%20Bay) [Tincanian](/define.php?term=Tincanian) [tincanned](/define.php?term=tincanned) [Tin Canoe](/define.php?term=Tin%20Canoe) [tin can sluttery](/define.php?term=tin%20can%20sluttery) [Tin Cap](/define.php?term=Tin%20Cap) [Tince](/define.php?term=Tince)

X-Frame-Options: SAMEORIGIN

Cache-Control: max-age=3600, public

X-Powered-By: Phusion Passenger 4.0.37

Server: nginx/1.4.4 + Phusion Passenger 4.0.37

Via: 1.1 varnish

X-Served-By: cache-iad2128-IAD, cache-at51-ATL

X-Cache: MISS, MISS


markdown:
A cardigan designed for men. Combination of the two words 'man' and 'cardigan'.
Can be referred to as 'mandy'.
Can be referred to as 'mandy'.
[Check out](/define.php?term=Check%20out)my new mandigan - do I look cool in it?
viết bởi
[smurray444](/author.php?author=smurray444)07 Tháng ba, 2007
A woolen garment, similar to a
[Cardigan](/define.php?term=Cardigan), but worn by Men in their twenties. Unlike a normal button fronted Cardigan, favoured by Men in their middle ages, a Mandigan is a garment for young, [fashion](/define.php?term=fashion)concious, confident Men who care deeply about their appearance but do not wish to suffer the cold.
I am both warm and stylish, wearing my Mandigan
viết bởi

WARC-Type: response

Content-Type: application/http; msgtype=response

Content-Type: text/html; charset=utf-8

X-Xss-Protection: 1; mode=block

X-Content-Type-Options: nosniff

Content-Encoding: gzip

Accept-Ranges: bytes

Connection: close

X-Served-By: cache-iad2120-IAD, cache-jfk1024-JFK

Vary: Accept-Encoding


markdown: 1896: John Pius Boland • 1900: Lawrence Doherty • 1904: Beals Wright • 1908: Josiah Ritchie, Arthur Gore (sân trong nhà) • 1912: Charles Winslow, André Gobert (sân trong nhà) • 1920: Louis Raymond • 1924: Vincent Richards • 1988: Miloslav Mečíř • 1992: Marc Rosset • 1996 Andre Agassi • 2000 Yevgeny Kafelnikov • 2004: Nicolás Massú • 2008: Rafael Nadal• 2012: Andy Murray

Server: Apache

Content-language: vi

X-UA-Compatible: IE=Edge

Vary: Accept-Encoding,Cookie

Content-Type: text/html; charset=UTF-8

Via: 1.1 varnish, 1.1 varnish

X-Cache: cp1052 hit (1), cp1052 frontend miss (0)

Cache-Control: private, s-maxage=0, max-age=0, must-revalidate


markdown:
*Ectoedemia gilvipennella*
Bách khoa toàn thư mở Wikipedia
|Ectoedemia gilvipennella|
|
|[Giới](/wiki/Gi%E1%BB%9Bi_(sinh_h%E1%BB%8Dc))( *regnum*) [Animalia](/wiki/%C4%90%E1%BB%99ng_v%E1%BA%ADt) [Ngành](/wiki/Ng%C3%A0nh_(sinh_h%E1%BB%8Dc))( *phylum*) [Arthropoda](/wiki/%C4%90%E1%BB%99ng_v%E1%BA%ADt_Ch%C3%A2n_kh%E1%BB%9Bp) [Lớp](/wiki/L%E1%BB%9Bp_(sinh_h%E1%BB%8Dc))( *class*) [Insecta](/wiki/C%C3%B4n_tr%C3%B9ng) [Liên bộ](/wiki/Li%C3%AAn_b%E1%BB%99)( *superordo*) [Amphiesmenoptera](/w/index.php?title=Amphiesmenoptera&action=edit&redlink=1) [Bộ](/wiki/B%E1%BB%99_(sinh_h%E1%BB%8Dc))( *ordo*) [Lepidoptera](/wiki/B%E1%BB%99_C%C3%A1nh_v%E1%BA%A9y) [Phân bộ](/wiki/Ph%C3%A2n_b%E1%BB%99)( *subordo*) [Glossata](/wiki/Glossata) [Phân thứ bộ](/wiki/Ph%C3%A2n_th%E1%BB%A9_b%E1%BB%99)( *infraordo*) [Heteroneura](/wiki/Heteroneura) [Liên họ](/wiki/Li%C3%AAn_h%E1%BB%8D)( *superfamilia*) [Nepticuloidea](/wiki/Nepticuloidea) [Họ](/wiki/H%E1%BB%8D_(sinh_h%E1%BB%8Dc))( *familia*) [Nepticulidae](/wiki/Nepticulidae) [Chi](/wiki/Chi_(sinh_h%E1%BB%8Dc))( *genus*) [Ectoedemia](/wiki/Ectoedemia) [Loài](/wiki/Lo%C3%A0i)( *species*) **E. gilvipennella** [Danh pháp hai phần](/wiki/Danh_ph%C3%A1p_hai_ph%E1%BA%A7n) *Ectoedemia gilvipennella*
(Klimesch, 1946)
[Danh pháp đồng nghĩa](/wiki/T%C3%AAn_%C4%91%E1%BB%93ng_ngh%C4%A9a_(sinh_v%E1%BA%ADt_h%E1%BB%8Dc)) *Stigmella gilvipennella*Klimesch, 1946 * là một loài Ectoedemia gilvipennella* [bướm đêm](/wiki/B%C6%B0%E1%BB%9Bm_%C4%91%C3%AAm)thuộc họ [Nepticulidae](/wiki/Nepticulidae). Nó được tìm thấy ở [Cộng hòa Séc](/wiki/C%E1%BB%99ng_h%C3%B2a_S%C3%A9c)và [Slovakia](/wiki/Slovakia)to [Italy](/wiki/%C3%9D)và [Hy Lạp](/wiki/Hy_L%E1%BA%A1p). [Sải cánh](/wiki/S%E1%BA%A3i_c%C3%A1nh) dài 4.4-5.4 mm. Con trưởng thành bay từ tháng 4 đến tháng 6. Có một lứa một năm. [Ấu trùng](/wiki/%E1%BA%A4u_tr%C3%B9ng) ăn * và Quercus cerris* *. Chúng* [Quercus trojana](/wiki/Quercus_trojana) [ăn lá](/w/index.php?title=S%C3%A2u_%C4%83n_l%C3%A1&action=edit&redlink=1)nơi chúng làm tổ.
## Tham khảo[
[sửa](/w/index.php?title=Ectoedemia_gilvipennella&veaction=edit&vesection=1) | [sửa mã nguồn](/w/index.php?title=Ectoedemia_gilvipennella&action=edit§ion=1)]
## Liên kết ngoài[
[sửa](/w/index.php?title=Ectoedemia_gilvipennella&veaction=edit&vesection=2) | [sửa mã nguồn](/w/index.php?title=Ectoedemia_gilvipennella&action=edit§ion=2)] [Fauna Europaea](http://www.faunaeur.org/full_results.php?id=357521) [bladmineerders.nl](http://www.bladmineerders.nl/minersf/lepidopteramin/ectoedemia/gilvipennella/gilvipennella.htm) [A Taxonomic Revision Of The Western Palaearctic Species Of The Subgenera Zimmermannia Hering And Ectoedemia Busck s.str. (Lepidoptera, Nepticulidae), With Notes On Their Phylogeny](http://www.repository.naturalis.nl/document/50162)

X-Cache: cp1066 miss (0), cp1068 frontend miss (0)


markdown:
# Leoben
Bách khoa toàn thư mở Wikipedia
|
|Leoben
|
|Huy hiệu |
|Vị trí
|
|Hành chính
|
|![ ](http://upload.wikimedia.org/wikipedia/commons/thumb/4/41/Flag_of_Austria.svg/22px-Flag_of_Austria.svg.png)
[Áo](/wiki/%C3%81o) [Bang](/wiki/Bang_c%E1%BB%A7a_%C3%81o) [Styria](/wiki/Styria) [Huyện](/w/index.php?title=Huy%E1%BB%87n_c%E1%BB%A7a_%C3%81o&action=edit&redlink=1) **Leoben** [Thị trưởng](/wiki/Burgomaster) **Dữ liệu thống kê cơ bản** [Diện tích](/wiki/Di%E1%BB%87n_t%C3%ADch) [Độ cao](/wiki/%C4%90%E1%BB%99_cao) [Dân số](/wiki/D%C3%A2n_s%E1%BB%91) *(31 tháng 12 2006)* [Mật độ](/wiki/M%E1%BA%ADt_%C4%91%E1%BB%99_d%C3%A2n_s%E1%BB%91) **Thông tin khác** [Múi giờ](/wiki/M%C3%BAi_gi%E1%BB%9D) [CET](/wiki/M%C3%BAi_gi%E1%BB%9D_Trung_%C3%82u)/ [CEST](/wiki/Gi%E1%BB%9D_m%C3%B9a_H%C3%A8_Trung_%C3%82u)( [UTC+1](/wiki/UTC%2B1)/ [+2](/wiki/UTC%2B2)) [Biển số xe](/w/index.php?title=Bi%E1%BB%83n_s%E1%BB%91_xe_%E1%BB%9F_%C3%81o&action=edit&redlink=1) [Mã bưu chính](/w/index.php?title=M%C3%A3_b%C6%B0u_ch%C3%ADnh_%E1%BB%9F_%C3%81o&action=edit&redlink=1) [Mã vùng](/w/index.php?title=M%C3%A3_v%C3%B9ng_%C4%91i%E1%BB%87n_tho%E1%BA%A1i_%E1%BB%9F_%C3%81o&action=edit&redlink=1) [Website](/wiki/Website) [www.leoben.at](http://www.leoben.at), [www.leoben.cc](http://www.leoben.cc) **Leoben** là một thành phố ở bang [Steiermark](/wiki/Steiermark), [Áo](/wiki/%C3%81o), nằm bên sông [Mur](/w/index.php?title=Mura&action=edit&redlink=1). Thành phố có dân số hơn 25.000 người, là một trung tâm công nghiệp và có [Đại học Leoben](/w/index.php?title=%C4%90%E1%BA%A1i_h%E1%BB%8Dc_Leoben&action=edit&redlink=1) chuyên về khai khoáng. [Hoà ước Leoben](/w/index.php?title=Ho%C3%A0_%C6%B0%E1%BB%9Bc_Leoben&action=edit&redlink=1), là một hoà ước sơ bộ cho [Hiệp ước Campo Formio](/w/index.php?title=Hi%E1%BB%87p_%C6%B0%E1%BB%9Bc_Campo_Formio&action=edit&redlink=1), đã được ký tại Leoben năm 1797.
## Người nổi tiếng[
[sửa](/w/index.php?title=Leoben&veaction=edit&vesection=1) | [sửa mã nguồn](/w/index.php?title=Leoben&action=edit§ion=1)]
## Tham khảo[
[sửa](/w/index.php?title=Leoben&veaction=edit&vesection=2) | [sửa mã nguồn](/w/index.php?title=Leoben&action=edit§ion=2)]
## Liên kết ngoài[
[sửa](/w/index.php?title=Leoben&veaction=edit&vesection=3) | [sửa mã nguồn](/w/index.php?title=Leoben&action=edit§ion=3)]
|
|![]()
[Leoben](//commons.wikimedia.org/wiki/Category:Leoben?uselang=vi)
|
|
|
|Bài này còn
Chúng ta đang có những nỗ lực để hoàn thiện bài này.
Nếu bạn biết về vấn đề này, bạn có thể giúp đỡ bằng cách

X-Cache: cp1052 miss (0), cp1065 frontend miss (0)


markdown:
Ngày nay phụ nữ ngày càng tự khẳng
định bản thân trong cuộc sống cũng như trong công việc. Trong nền kinh
tế hội nhập và phát triển có nhiều công việc tốt hơn cho phụ nữ.Theo khảo sát và thống kê của website Việc làm – Tuyển dụng nhanh số 1 Việt Nam
[ trong thời gian gần đây (6 tháng đầu năm 2009) những công việc được quan tâm nhiều nhất là...](http://www.timviecnhanh.com/)
# Việc làm An Giang
## Việc làm phù hợp với phụ nữ ngày nay
[Đọc thêm...](/viec-lam-an-giang/154-viec-lam-phu-hop-voi-phu-nu-ngay-nay.html)
JPAGE_CURRENT_OF_TOTAL

P3P: CP="NOI ADM DEV PSAi COM NAV OUR OTRo STP IND DEM"

Cache-Control: post-check=0, pre-check=0

Pragma: no-cache

Set-Cookie: ja_kyanite_tpl=ja_kyanite; expires=Mon, 10-Aug-2015 16:34:24 GMT; path=/


markdown:
|
|
Theo ông Nguyễn Quốc Cẩm (xã Phúc Thắng, huyện Mê Linh, Vĩnh Phúc), phụ huynh của một thí sinh thi vào trường, rất dễ chạy điểm vào trường này. Chỉ cần chi 40 triệu đồng cho "chân gỗ" là có một suất học tại đây.
Trên thực tế, dư luận cho rằng việc chấm thi vào ĐH Kiến Trúc HN có nhiều điểm chưa rõ ràng, đặc biệt là môn vẽ. Vì đây là môn năng khiếu nghệ thuật nên cách chấm còn tuỳ hứng. Nhiều thí sinh vẽ xấu lại được điểm cao, thí sinh vẽ tốt lại bị điểm liệt. Trong khi đó, môn vẽ lại tính hệ số 2...
Một số giáo viên thuộc Trường ĐH Kiến trúc HN cũng khẳng định môn vẽ là một "lãnh địa" riêng. Chỉ có một nhóm giáo viên được giao chấm môn thi này. Đây là môn thi dễ nâng điểm nhất. Ví dụ như năm nay, điểm đỗ vào trường là 21 điểm, thí sinh chỉ cần được 7,5 môn vẽ là được 15 điểm. 2 môn còn lại chỉ cần 6 điểm là đương nhiên vào trường... Phó hiệu trưởng của trường Uông Đình Chất, Trưởng ban chấm thi của kỳ thi tuyển sinh ĐH, CĐ năm nay, thừa nhận: "Năm nào chúng tôi cũng bị kêu ca về môn này. Bản thân thẩm mỹ của mỗi thầy đã khác nhau, nên rất khó đánh giá".
Ông Chất lý giải: "Do môn vẽ rất khó định lượng như toán, lý, hoá nên nhiều phụ huynh không hiểu, hay chất vấn... Trường đã chỉ đạo xây dựng thang điểm. Có tới 5-7 thầy chấm theo vòng tròn... Chúng tôi muốn tổ chức chấm thi như vậy để tránh thiên vị, tiêu cực. Riêng những giáo viên có con, em thi trong năm nay cũng bị "loại" khỏi danh sách chấm thi... Tuy nhiên, năm nào cũng nghe nói để lọt vài trường hợp người nhà của giáo viên. Nhưng chúng tôi không giải quyết được vì không
Cũng theo ông Chất, giáo viên chấm thi do Chủ tịch Hội đồng tuyển sinh (cụ thể là hiệu trưởng) tuyển chọn. Và vì thế, cần phải tin hiệu trưởng bởi đó là người chịu trách nhiệm cao nhất.
(Theo
|
|
TIN
![]()
Bạn có thể gửi nhận xét, góp ý hay liên hệ về bài viết
** bằng cách gửi thư điện tử tới Cách chấm điểm của ĐH Kiến trúc HN dễ gây tiêu cực**
Người Việt ở tâm dịch Ebola không dám ra đường; Hé lộ nhiều thông tin về vụ 2 người chết trong ô tô; Con gái đại gia Minh 'sâm' cũng bị khởi tố; Hiện trường vụ thi thể bị nhiều xe chèn trên cao tốc...
Rút phương án nâng tuổi hưu; Phó phòng ngoại vụ ở lại Mỹ để học tiến sĩ?; Hơn 100 chiến sĩ bắt giám đốc trùm xã hội đen; Đôi nam nữ chết trong ô tô, tay vẫn cầm súng
Thảm kịch tâm dịch Ebola qua lời kể người Việt; Đôi nam nữ chết trong ô tô, tay vẫn cầm súng; Phạt 207 triệu, đình bản báo điện tử Trí Thức Trẻ; Ông Chấn lên Thủ đô chuẩn bị đòi bồi thường 10 tỷ...
Hơn 100 chiến sĩ bắt giám đốc trùm xã hội đen; Gia đình ông Trần Trọng Tân tặng từ thiện 1,25 tỷ tiền phúng viếng; Hồ Ngọc Hà gọi Cường Đô la về 'chăm con'; Nguyên phó trưởng CA TP. Thanh Hóa bị dọa giết cả nhà
Rút phương án nâng tuổi hưu; Tình tiết mới vụ ĐH Tôn Đức Thắng kiện GS Nguyễn Đăng Hưng; Phó ban tổ chức quận ủy 'dính' vụ giết người như thế nào?; Bố bắt quả tang con gái 'yêu' 2 người cùng lúc
Có ông quan tỉnh giấu dưới gầm giường 65 cây vàng, cán bộ thuế lộ 12 sổ tiết kiệm trị giá 5 tỷ đồng... Tất cả bị trộm khoắng sạch.
Hình ảnh của con người Việt Nam đẹp hay xấu được thể hiện từ mỗi một cá nhân chúng ta
Nhiều nghiên cứu hiện nay cho thấy, trong kem đánh răng Colgate Total có thể chứa thành phần hoạt chất gây hại cho người tiêu dùng, thậm chí dẫn đến ung thư.
Căn bệnh chết người không có thuốc chữa này đang lan tràn từ châu Phi sang châu Mỹ, khiến người dân toàn thế giới kinh hãi.
Nhìn về câu chuyện của chùa Bồ Đề, xin hãy xem đó như là một vết thương của thời lỗi đời lỗi đạo.
Tổng thổng Mỹ, Obama cho phép không kích quân nổi dậy ở Iraq, kết quả các cuộc bầu cử Tổng thống ở Thổ Nhĩ Kỳ và Iran, Trung Quốc bác bỏ đề xuất giải quyết tranh chấp ở Biển Đông của Philippines... là những tin tức đáng chú ý trong tuần qua.
Thông tin TQ phát hành sách phi pháp về đường chín đoạn; Ngày 19/8 chính thức công bố kết luận thanh tra chùa Bồ Đề; Chống trượt cao học, 40 người lót tay hơn 1 tỷ đồng; hay Công điện khẩn về tăng cường phòng chống virus cúm A/H5N6 ..... là những tin tức nổi bật được dư luận quan tâm trong tuần qua (10/08 - 16/08)
Chuyện tình yêu đầy sóng gió của các mỹ nhân Phi Thanh Vân, Hồ Ngọc Hà, DJ Oxy, chiêu trò mới gây chú ý của Ngọc Trinh, Đàm Vĩnh Hưng, nhóm nhạc Hàn Quốc 2NE1 gây "bão" ở Việt Nam, vấn đề thu tiền tác quyền âm nhạc lại nóng, tài tử Robin Williams qua đời, diễn viên "Thiên long bát bộ" bị bắt vì dùng ma túylà những thông tin nổi bật tuần qua.
Kem đánh răng Colgate chứa chất gây ung thư khiến người tiêu dùng hoang mang, sau khi giảm giá xăng, Petrolimex lại than ít lãi, Thanh Long được mùa mất giá khiến người nông dân điều đứng, lãi khủng của Vietnam Airlines, đủ chiêu "né trần" giá sữa của doanh nghiệp... là những tin tức, sự kiện kinh tế nóng hổi trong tuần vừa qua.
Đám cưới của cô dâu bị ung thư, tình yêu trái ngọt của chàng trai tật nguyền và rất nhiều câu chuyện tình yêu gây xúc động; Nuôi dạy con - Những câu chuyện hy sinh và cả những sự việc tàn ác; Chuyện gia đình của những mối tình đồng tính; Nhiều tin tức thực phẩm độc hại nên lưu ý; cùng với đó là những bài viết đáng suy ngẫm về thực trạng cuộc sống quanh ta...
Ý kiến bạn đọc
Viết phản hồi

WARC-Truncated: length

Cache-Control: max-age=280, public


markdown:
CHÀO MỪNG TẤT CẢ CÁC BẠN ĐẾN VỚI VIETCHESS
09042.73370 - 0988.522.908
Hỗ trợ trực tuyến
(vietchess) Ngày 14-8 (giờ Na Uy), Nguyễn Ngọc Trường Sơn (Elo 2634) đã giành HCV bàn 2 Olympiad cờ vua thế giới 2014 diễn ra tại Tromso (Na Uy).
(vietchess) Một kỳ thủ 67 tuổi đã đột quỵ ngay trên bàn cờ trong ngày thi cuối cùng, trong khi một người khác bị phát hiện đã chết trong phòng khách sạn tại giải vô địch cờ vua Olympiad 2014.
(vietchess) Đội tuyển cờ vua nữ Việt Nam đã giành hạng 19 chung cuộc, thành tích đầy ấn tượng trong các kỳ tham dự Giải cờ vua đồng đội thế giới - Olympiad của mình, khi giành chiến thắng tuyệt đối 4-0 trước El Salvaldor vào tối 14-8.
(vietchess) Ngày 14-8 (giờ Na Uy), Nguyễn Ngọc Trường Sơn đã giành HCV bàn 2 với thành tích bất bại ở Olympiad cờ vua thế giới 2014 diễn ra tại Tromso (Na Uy).
(vietchess) Dù thi đấu rất cố gắng nhưng các cô gái Việt Nam đã không thể làm nên bất ngờ trước hạt giống số 6 Romani tại ván 9 giải cờ vua đồng đội thế giới (Olympiad Tromso 2014) kết thúc vào sáng 12/8.
(vietchess) Alexandra Botez, 19 tuổi, được cho là nữ sinh xinh đẹp nhất trong làng cờ ở Canada nói riêng và thế giới nói chung. Gương mặt lạnh lùng "chết người" của cô gái này luôn khiến các đối thủ phải e ngại.
Bản quyền của vietchess.vn
Mọi thông tin vui lòng liên hệ: luong_trminh@yahoo.com

Server: nginx

Content-Type: text/html

Vary: Accept-Encoding,User-Agent


markdown:
University of Minnesota. Driven to Discover.
Bovine spongiform encephalopathy
An abnormal protein linked to vCJD may be more common than expected in the UK.
Gill ON, Spencer Y, Richard-Leondt A, et al. Prevalent abnormal prion protein in human appendixes after bovine spongiform encephalopathy epizootic: large scale survey. BMJ 2013 (published online Oct 15)
Jackson GS, Burk-Rafel J, Edgeworth JA, et al. Population screening for variant Creutzfeldt-Jakob disease using a novel blood test. JAMA Neurol 2014 (published online Mar 3)
Race B, Meade-White KD, Phillips K, et al. Chronic wasting disease agents in nonhuman primates. Emerg Infect Dis 2014 (published online Mar 25)
Get news & practices.
Sign up now»
Unrestricted financial support provided by
Become an underwriter»
CIDRAP - Center for Infectious Disease Research and PolicyAcademic Health Center, University of Minnesota, Minneapolis, MN
© 2013 Regents of the University of Minnesota. All rights reserved.The University of Minnesota is an equal opportunity educator and employer.
CIDRAP | Academic Health Center | Contact U of M | Privacy Policy

X-Drupal-Cache: MISS

Cache-Control: public, max-age=3600

Content-Language: en

X-Generator: Drupal 7 (http://drupal.org)

Vary: Cookie,Accept-Encoding


markdown:
**Congthuonghcm.vn - Sáng 29/6/2011, Trung tâm Khuyến công và Tư vấn phát triển công nghiệp (Sở Công Thương) Thái Nguyên phối hợp với Công ty TNHH Quang Trung tổ chức Hội nghị giới thiệu mô hình trình diễn kỹ thuật sản xuất gạch tuynel tại Nhà máy gạch tuynel Phú Lộc, xã Cổ Lũng (Phú Lương).
**
Mô hình trình diễn kĩ thuật sản xuất gạch tuynel được Công ty TNHH Quang Trung đầu tư với tổng số vốn trên 43,3 tỷ đồng, từ nguồn vốn tự có, vốn vay và kinh phí khuyến công địa phương. Công nghệ sản xuất gạch mà Công ty áp dụng là công nghệ lò nung tuynel dạng đường hầm thẳng, có chiều dài 107m, gồm 2 lò nung và sấy đặt song song nhau. Tiếp liệu cho lò là hệ thống đường ray, kích đẩy thủy lực và xe phà. Nhiên liệu được cung cấp cho lò đốt là bột than, được tra từ nóc lò xuống và cháy trong nhiệt độ sẵn có là 800-10500C. Đây là môi trường tốt để nhiên liệu cháy triệt để. Trong quá trình nung, nhiệt khí thải lò nung được tái sử dụng cho lò sấy qua hệ thống quạt và kênh dẫn khí nóng được hút từ hai đầu lò. Đặc tính này làm hiệu suất sử dụng năng lượng của lò tăng cao, góp phần cải thiện môi trường trong lò nung công nghiệp. Ngoài ra, hệ thống kết cầu của lò cũng tương đối vững chắc, vùng chịu lửa ở chế độ tĩnh tại và ổn định không có dao động nhiệt, giúp tăng tuổi thọ của lò (trung bình khoảng 40 năm). Bên cạnh đó, lò nung tuynel của Nhà máy tuynel Phú Lộc gần như được tự động hóa với công suất 40 triệu viên/năm, góp phần nâng cao năng suất, đa đạng hóa sản phẩm, giúp giảm tỷ lệ lao động trực tiếp ở một số công đoạn. Lò còn được trang bị thêm buồng thu hồi xỉ than, giúp cải thiện môi trường. Quá trình sản xuất cũng không bị ảnh hưởng bởi thời tiết vì tất cả các công đoạn đều có mái che.
Đây là mô hình hiện đại đầu tiên trên địa bàn huyện Phú Lương, góp phần giải quyết việc làm cho 150 lao động tại địa phương với thu nhập ổn định…
**Theo báo Công Nghiệp Online**

Cache-control: private


markdown:
Chiều ngày 29/11/2012, Ban chấp hành Công đoàn CSTV tổ chức tổng kết phong trào CNVC và hoạt động Công đoàn năm 2012. Hội nghị mở rộng đến các thành phần : Tổ trưởng, tổ phó Công đoàn trực thuộc và các ATVSV trong đơn vị . Đến dự và chỉ đạo hội nghị có đồng chí Nguyễn Ngọc Tâm-Bí thư Chi bộ, Giám đốc Điện lực và các Trưởng phòng, Tổ trưởng chuyên môn cùng tham dự.
Về đầu trang Sơ đồ trang
Trụ sở chính: 102 Nguyễn Huệ, Thành phố Huế • Giấy phép số: 2222/GP-BCN, cấp ngày 05/09/2003
© Công ty Điện Lực Thừa Thiên Huế, All rights reserved • Điện thoại: (84-054) 2211222 - 2220220 • Fax: (84-054) 2220330 • Email: dltth@dienluctth.com.vn


markdown:
# FreeBSD Man Pages
[home](/cgi/man.cgi?manpath=FreeBSD+9.2-RELEASE)| [help](/cgi/man.cgi/help.html)
GROFF_MDOC(7) FreeBSD Miscellaneous Information Manual GROFF_MDOC(7)
NAME groff_mdoc-- reference for groff's mdoc implementation SYNOPSIS groff -mdoc file ... [A complete reference for writing UNIX manual pages with the] DESCRIPTION -mdocmacro package; a content-based and domain-based formatting package for GNU [troff(1)]. Its predecessor, the [-man(7)]package, addressed page layout leaving the manipulation of fonts and other typesetting details to the individual author. In -mdoc, page layout macros make up the page structure domainwhich consists of macros for titles, section headers, displays and lists - essentially items which affect the physical position of text on a formatted page. In addition to the page structure domain, there are two more domains, the manualdomain and the generaltext domain. The general text domain is defined as macros which perform tasks such as quoting or emphasizing pieces of text. The manual domain is defined as macros that are a subset of the day to day informal language used to describe commands, routines and related UNIX files. Macros in the manual domain handle command names, command line arguments and options, function names, function parameters, pathnames, variables, cross references to other manual pages, and so on. These domain items have value for both the author and the future user of the manual page. Hope- fully, the consistency gained across the manual set will provide easier translation to future documentation tools. Throughout the UNIX manual pages, a manual entry is simply referred to as a man page, regardless of actual length and without sexist intention. [The material presented in the remainder of this document is outlined as follows: 1. TROFF IDIOSYNCRASIES Macro Usage Passing Space Characters in an Argument Trailing Blank Space Characters Escaping Special Characters Other Possible Pitfalls 2. A MANUAL PAGE TEMPLATE 3. CONVENTIONS 4. TITLE MACROS 5. INTRODUCTION OF MANUAL AND GENERAL TEXT DOMAINS What's in a Name... General Syntax 6. MANUAL DOMAIN Addresses Author Name Arguments Configuration Declarations (Section Four Only) Command Modifiers Defined Variables Errno's Environment Variables Flags Function Declarations Function Types Functions (Library Routines) Function Arguments Return Values Exit Status Interactive Commands Library Names Literals Names Options Pathnames Standards Variable Types Variables Manual Page Cross References 7. GENERAL TEXT DOMAIN AT&T Macro BSD Macro NetBSD Macro FreeBSD Macro DragonFly Macro OpenBSD Macro BSD/OS Macro UNIX Macro Emphasis Macro Font Mode Enclosure and Quoting Macros No-Op or Normal Text Macro No-Space Macro Section Cross References Symbolics Mathematical Symbols References and Citations Trade Names (or Acronyms and Type Names) Extended Arguments 8. PAGE STRUCTURE DOMAIN Section Headers Subsection Headers Paragraphs and Line Spacing Keeps Examples and Displays Lists and Columns 9. MISCELLANEOUS MACROS 10. PREDEFINED STRINGS 11. DIAGNOSTICS 12. FORMATTING WITH GROFF, TROFF, AND NROFF 13. FILES 14. SEE ALSO 15. BUGS] GETTING STARTED [The] TROFF IDIOSYNCRASIES -mdocpackage attempts to simplify the process of writing a man page. Theoretically, one should not have to learn the tricky details of GNU [troff(1)]to use -mdoc; however, there are a few limitations which are unavoidable and best gotten out of the way. And, too, be forewarned, this package is notfast. Macro UsageAs in GNU [troff(1)], a macro is called by placing a `.' (dot character) at the beginning of a line followed by the two-character (or three-charac- ter) name for the macro. There can be space or tab characters between the dot and the macro name. Arguments may follow the macro separated by spaces (but notabs). It is the dot character at the beginning of the line which causes GNU [troff(1)]to interpret the next two (or more) char- acters as a macro name. A single starting dot followed by nothing is ignored. To place a `.' (dot character) at the beginning of an input line in some context other than a macro invocation, precede the `.' (dot) with the `\&' escape sequence which translates literally to a zero-width space, and is never displayed in the output. In general, GNU [troff(1)]macros accept an unlimited number of arguments (contrary to other versions of troff which can't handle more than nine arguments). In limited cases, arguments may be continued or extended on the next line (See Extended Argumentsbelow). Almost all macros handle quoted arguments (see Passing Space Characters in an Argumentbelow). Most of the -mdocgeneral text domain and manual domain macros are spe- cial in that their argument lists are parsedfor callable macro names. This means an argument on the argument list which matches a general text or manual domain macro name (and which is defined to be callable) will be executed or called when it is processed. In this case the argument, although the name of a macro, is not preceded by a `.' (dot). This makes it possible to nest macros; for example the option macro, `.Op', may callthe flag and argument macros, `Fl' and `Ar', to specify an optional flag with an argument: [ -s bytes] is produced by `.Op Fl s Ar bytes' To prevent a string from being interpreted as a macro name, precede the string with the escape sequence `\&': [Fl s Ar bytes] is produced by `.Op \&Fl s \&Ar bytes' Here the strings `Fl' and `Ar' are not interpreted as macros. Macros whose argument lists are parsed for callable arguments are referred to as parsedand macros which may be called from an argument list are referred to as callablethroughout this document. This is a technical faux pasas almost all of the macros in -mdocare parsed, but as it was cumbersome to constantly refer to macros as being callable and being able to call other macros, the term parsed has been used. In the following, we call an -mdocmacro which starts a line (with a leading dot) a commandif this distinction is necessary. Passing Space Characters in an ArgumentSometimes it is desirable to give as an argument a string containing one or more blank space characters, say, to specify arguments to commands which expect particular arrangement of items in the argument list. Addi- tionally, it makes -mdocworking faster. For example, the function com- mand `.Fn' expects the first argument to be the name of a function and any remaining arguments to be function parameters. As ANSI C stipulates the declaration of function parameters in the parenthesized parameter list, each parameter is guaranteed to be at minimum a two word string. For example, int foo. There are two possible ways to pass an argument which contains an embed- ded space. One way of passing a string containing blank spaces is to use the hard or unpaddable space character `\ ', that is, a blank space pre- ceded by the escape character `\'. This method may be used with any macro but has the side effect of interfering with the adjustment of text over the length of a line. Troff sees the hard space as if it were any other printable character and cannot split the string into blank or new- line separated pieces as one would expect. This method is useful for strings which are not expected to overlap a line boundary. An alterna- tive is to use `\~', a paddable (i.e. stretchable), unbreakable space (this is a GNU [troff(1)]extension). The second method is to enclose the string with double quotes. For example: fetch( char *str) is created by `.Fn fetch char\ *str' fetch( char *str) can also be created by `.Fn fetch "char *str"' If the `\' before the space in the first example or double quotes in the second example were omitted, `.Fn' would see three arguments, and the result would be: fetch( char, *str) Trailing Blank Space CharactersTroff can be confused by blank space characters at the end of a line. It is a wise preventive measure to globally remove all blank spaces from <blank-space><end-of-line> character sequences. Should the need arise to use a blank character at the end of a line, it may be forced with an unpaddable space and the `\&' escape character. For example, `string\ \&'. Escaping Special CharactersSpecial characters like the newline character `\n' are handled by replac- ing the `\' with `\e' (e.g. `\en') to preserve the backslash. Other Possible PitfallsA warning is emitted when an empty input line is found outside of dis- plays (see below). Use `.sp' instead. (Well, it is even better to use -mdocmacros to avoid the usage of low-level commands.) Leading spaces will cause a break and are output directly. Avoid this behaviour if possible. Similarly, do not use more than one space charac- ter between words in an ordinary text line; contrary to other text for- matters, they are notreplaced with a single space. You can't pass `"' directly as an argument. Use `\*[q]' (or `\*q') instead. By default, [troff(1)]inserts two space characters after a punctuation mark closing a sentence; characters like `)' or `'' are treated transpar- ently, not influencing the sentence-ending behaviour. To change this, insert `\&' before or after the dot: The .Ql . character. .Pp The .Ql \&. character. .Pp .No test . test .Pp .No test. test gives The `'. character The `.' character. test. test test. test As can be seen in the first and third line, -mdochandles punctuation characters specially in macro arguments. This will be explained in sec- tion General Syntaxbelow. In the same way, you have to protect trailing full stops of abbreviations with a trailing zero-width space: `e.g.\&'. A comment in the source file of a man page can be either started with `.\"' on a single line, `\"' after some input, or `\#' anywhere (the lat- ter is a GNU [troff(1)]extension); the rest of such a line is ignored. [The body of a man page is easily constructed from a basic template: .\" The following commands are required for all man pages. .Dd Month day, year .Dt DOCUMENT_TITLE [section number] [architecture/volume] .Os [OPERATING_SYSTEM] [version/release] .Sh NAME .Nm name .Nd one line description of name .\" This next command is for sections 2 and 3 only. .\" .Sh LIBRARY .Sh SYNOPSIS .Sh DESCRIPTION .\" The following commands should be uncommented and .\" used where appropriate. .\" .Sh IMPLEMENTATION NOTES .\" This next command is for sections 2, 3 and 9 function .\" return values only. .\" .Sh RETURN VALUES .\" This next command is for sections 1, 6, 7 and 8 only. .\" .Sh ENVIRONMENT .\" .Sh FILES .\" .Sh EXAMPLES .\" This next command is for sections 1, 6, 7, 8 and 9 only .\" (command return values (to shell) and .\" fprintf/stderr type diagnostics). .\" .Sh DIAGNOSTICS .\" .Sh COMPATIBILITY .\" This next command is for sections 2, 3 and 9 error .\" and signal handling only. .\" .Sh ERRORS .\" .Sh SEE ALSO .\" .Sh STANDARDS .\" .Sh HISTORY .\" .Sh AUTHORS .\" .Sh BUGS The first items in the template are the commands `.Dd', `.Dt', and `.Os'; the document date, the operating system the man page or subject source is developed or modified for, and the man page title (in] A MANUAL PAGE TEMPLATE upper case) along with the section of the manual the page belongs in. These commands iden- tify the page and are discussed below in TITLE MACROS. The remaining items in the template are section headers (.Sh); of which NAME, SYNOPSIS, and DESCRIPTIONare mandatory. The headers are discussed in PAGE STRUCTURE DOMAIN, after presentation of MANUAL DOMAIN. Several content macros are used to demonstrate page layout macros; reading about content macros before page layout macros is recommended. [In the description of all macros below, optional arguments are put into brackets. An ellipsis (`...') represents zero or more additional argu- ments. Alternative values for a parameter are separated with `|'. If there are alternative values for a mandatory parameter, braces are used (together with `|') to enclose the value set. Meta-variables are speci- fied within angles. Example: .Xx <foo> {bar1 | bar2} [-test1 [-test2 | -test3]] ... Except stated explicitly, all macros are parsed and callable. Note that a macro takes effect up to the next nested macro. For example, `.Ic foo Aq bar' doesn't produce `] CONVENTIONS foo< bar>' but ` foo<bar>'. Conse- quently, a warning message is emitted for most commands if the first argument is a macro itself since it cancels the effect of the calling command completely. Another consequence is that quoting macros never insert literal quotes; ` foo< bar>' has been produced by `.Ic "foo <bar>"'. Most macros have a default width value which can be used to specify a label width ( -width) or offset ( -offset) for the `.Bl' and `.Bd' macros. It is recommended not to use this rather obscure feature to avoid depen- dencies on local modifications of the -mdocpackage. [The title macros are part of the page structure domain but are presented first and separately for someone who wishes to start writing a man page yesterday. Three header macros designate the document title or manual page title, the operating system, and the date of authorship. These macros are called once at the very beginning of the document and are used to construct headers and footers only. .Dt [<document title>] [<section number>] [<volume>] The document title is the subject of the man page and must be in CAPITALS due to troff limitations. If omitted, `UNTITLED' is used. The section number may be a number in the range 1, ..., 9 or `unass', `draft', or `paper'. If it is specified, and no vol- ume name is given, a default volume name is used. Under FreeBSD 9.3, the following sections are defined: 1 FreeBSD General Commands Manual 2 FreeBSD System Calls Manual 3 FreeBSD Library Functions Manual 4 FreeBSD Kernel Interfaces Manual 5 FreeBSD File Formats Manual 6 FreeBSD Games Manual 7 FreeBSD Miscellaneous Information Manual 8 FreeBSD System Manager's Manual 9 FreeBSD Kernel Developer's Manual A volume name may be arbitrary or one of the following: USD User's Supplementary Documents PS1 Programmer's Supplementary Documents AMD Ancestral Manual Documents SMM System Manager's Manual URM User's Reference Manual PRM Programmer's Manual KM Kernel Manual IND Manual Master Index LOCAL Local Manual CON Contributed Software Manual For compatibility, `MMI' can be used for `IND', and `LOC' for `LOCAL'. Values from the previous table will specify a new vol- ume name. If the third parameter is a keyword designating a com- puter architecture, its value is prepended to the default volume name as specified by the second parameter. By default, the fol- lowing architecture keywords are defined: acorn26, acorn32, algor, alpha, amd64, amiga, amigappc, arc, arm, arm26, arm32, armish, atari, aviion, beagle, bebox, cats, cesfic, cobalt, dreamcast, emips, evbarm, evbmips, evbppc, evbsh3, ews4800mips, hp300, hp700, hpcarm, hpcmips, hpcsh, hppa, hppa64, i386, ia64, ibmnws, iyonix, landisk, loongson, luna68k, luna88k, m68k, mac68k, macppc, mips, mips64, mipsco, mmeye, mvme68k, mvme88k, mvmeppc, netwinder, news68k, newsmips, next68k, ofppc, palm, pc532, playstation2, pmax, pmppc, powerpc, prep, rs6000, sandpoint, sbmips, sgi, sgimips, sh3, shark, socppc, solbourne, sparc, sparc64, sun2, sun3, tahoe, vax, x68k, x86_64, xen, zaurus If the section number is neither a numeric expression in the range 1 to 9 nor one of the above described keywords, the third parameter is used verbatim as the volume name. In the following examples, the left (which is identical to the right) and the middle part of the manual page header strings are shown. Note how `\&' prevents the digit 7 from being a valid numeric expression. .Dt FOO 7 `] TITLE MACROS [FOO(7)]' `FreeBSD Miscellaneous Information Manual' .Dt FOO 7 bar ` [FOO(7)]' `FreeBSD Miscellaneous Information Manual' .Dt FOO \&7 bar ` [FOO(7)]' `bar' .Dt FOO 2 i386 ` [FOO(2)]' `FreeBSD/i386 System Calls Manual' .Dt FOO "" bar `FOO' `bar' Local, OS-specific additions might be found in the file mdoc.local; look for strings named `volume-ds-XXX' (for the for- mer type) and `volume-as-XXX' (for the latter type); `XXX' then denotes the keyword to be used with the `.Dt' macro. This macro is neither callable nor parsed. .Os [<operating system>] [<release>] If the first parameter is empty, the default `FreeBSD 9.3' is used. This may be overridden in the local configuration file, mdoc.local. In general, the name of the operating system should be the common acronym, e.g. BSD or ATT. The release should be the standard release nomenclature for the system specified. In the following table, the possible second arguments for some pre- defined operating systems are listed. Similar to `.Dt', local additions might be defined in mdoc.local; look for strings named `operating-system-XXX-YYY', where `XXX' is the acronym for the operating system and `YYY' the release ID. ATT 7th, 7, III, 3, V, V.2, V.3, V.4 BSD 3, 4, 4.1, 4.2, 4.3, 4.3t, 4.3T, 4.3r, 4.3R, 4.4 NetBSD 0.8, 0.8a, 0.9, 0.9a, 1.0, 1.0a, 1.1, 1.2, 1.2a, 1.2b, 1.2c, 1.2d, 1.2e, 1.3, 1.3a, 1.4, 1.4.1, 1.4.2, 1.4.3, 1.5, 1.5.1, 1.5.2, 1.5.3, 1.6, 1.6.1, 1.6.2, 1.6.3, 2.0, 2.0.1, 2.0.2, 2.0.3, 2.1, 3.0, 3.0.1, 3.0.2, 3.0.3, 3.1, 3.1.1, 4.0, 4.0.1, 5.0, 5.0.1, 5.0.2, 5.1, 6.0 FreeBSD 1.0, 1.1, 1.1.5, 1.1.5.1, 2.0, 2.0.5, 2.1, 2.1.5, 2.1.6, 2.1.7, 2.2, 2.2.1, 2.2.2, 2.2.5, 2.2.6, 2.2.7, 2.2.8, 3.0, 3.1, 3.2, 3.3, 3.4, 3.5, 4.0, 4.1, 4.1.1, 4.2, 4.3, 4.4, 4.5, 4.6, 4.6.2, 4.7, 4.8, 4.9, 4.10, 4.11, 5.0, 5.1, 5.2, 5.2.1, 5.3, 5.4, 5.5, 6.0, 6.1, 6.2, 6.3, 6.4, 7.0, 7.1, 7.2, 7.3, 8.0, 8.1, 8.2, 9.0 OpenBSD 2.0, 2.1, 2.2, 2.3, 2.4, 2.5, 2.6, 2.7, 2.8, 2.9, 3.0, 3.1, 3.2, 3.3, 3.4, 3.5, 3.6, 3.7, 3.8, 3.9, 4.0, 4.1, 4.2, 4.3, 4.4, 4.5, 4.6, 4.7, 4.8, 4.9, 5.0 DragonFly 1.0, 1.1, 1.2, 1.3, 1.4, 1.5, 1.6, 1.8, 1.8.1, 1.10, 1.12, 1.12.2, 2.0, 2.2, 2.4, 2.6, 2.8, 2.9, 2.9.1, 2.10, 2.10.1, 2.11 Darwin 8.0.0, 8.1.0, 8.2.0, 8.3.0, 8.4.0, 8.5.0, 8.6.0, 8.7.0, 8.8.0, 8.9.0, 8.10.0, 8.11.0, 9.0.0, 9.1.0, 9.2.0, 9.3.0, 9.4.0, 9.5.0, 9.6.0, 9.7.0, 9.8.0, 10.1.0, 10.2.0, 10.3.0, 10.4.0, 10.5.0, 10.6.0, 10.7.0, 11.0.0 For ATT, an unknown second parameter will be replaced with the string UNIX; for the other predefined acronyms it will be ignored and a warning message emitted. Unrecognized arguments are dis- played as given in the page footer. For instance, a typical footer might be: .Os BSD 4.3 giving `4.3 Berkeley Distribution', or for a locally produced set .Os CS Department which will produce `CS Department'. If the `.Os' macro is not present, the bottom left corner of the manual page will be ugly. This macro is neither callable nor parsed. .Dd [<month> <day>, <year>] If `Dd' has no arguments, `Epoch' is used for the date string. If it has exactly three arguments, they are concatenated, sepa- rated with unbreakable space: .Dd January 25, 2001 The month's name shall not be abbreviated. With any other number of arguments, the current date is used, ignoring the parameters. This macro is neither callable nor parsed. INTRODUCTION OF MANUAL AND GENERAL TEXT DOMAINS What's in a Name... The manual domain macro names are derived from the day to day informal language used to describe commands, subroutines and related files. Slightly different variations of this language are used to describe the three different aspects of writing a man page. First, there is the description of -mdocmacro command usage. Second is the description of a UNIX command with -mdocmacros, and third, the description of a command to a user in the verbal sense; that is, discussion of a command in the text of a man page. In the first case, [troff(1)]macros are themselves a type of command; the general syntax for a troff command is: .Xx argument1 argument2 ... `.Xx' is a macro command, and anything following it are arguments to be processed. In the second case, the description of a UNIX command using the content macros is a bit more involved; a typical SYNOPSIScommand line might be displayed as: filter[ -flag] < infile> < outfile> Here, filteris the command name and the bracketed string -flagis a flagargument designated as optional by the option brackets. In -mdocterms, < infile> and < outfile> are called meta arguments; in this example, the user has to replace the meta expressions given in angle brackets with real file names. Note that in this document meta arguments are used to describe -mdoccommands; in most man pages, meta variables are not specifically written with angle brackets. The macros which formatted the above example: .Nm filter .Op Fl flag .Ao Ar infile Ac Ao Ar outfile Ac In the third case, discussion of commands and command syntax includes both examples above, but may add more detail. The arguments < infile> and < outfile> from the example above might be referred to as operandsor file arguments. Some command line argument lists are quite long: make[ -eiknqrstv] [ -D variable] [ -d flags] [ -f makefile] [ -I directory] [ -j max _ jobs] [ variable= value] [ target ...] Here one might talk about the command makeand qualify the argument, makefile, as an argument to the flag, -f, or discuss the optional file operand target. In the verbal context, such detail can prevent confu- sion, however the -mdocpackage does not have a macro for an argument toa flag. Instead the `Ar' argument macro is used for an operand or file argument like targetas well as an argument to a flag like variable. The make command line was produced from: .Nm make .Op Fl eiknqrstv .Op Fl D Ar variable .Op Fl d Ar flags .Op Fl f Ar makefile .Op Fl I Ar directory .Op Fl j Ar max_jobs .Op Ar variable Ns = Ns Ar value .Bk .Op Ar target ... .Ek The `.Bk' and `.Ek' macros are explained in Keeps. General SyntaxThe manual domain and general text domain macros share a similar syntax with a few minor deviations; most notably, `.Ar', `.Fl', `.Nm', and `.Pa' differ only when called without arguments; and `.Fn' and `.Xr' impose an order on their argument lists. All content macros are capable of recog- nizing and properly handling punctuation, provided each punctuation char- acter is separated by a leading space. If a command is given: .Ar sptr, ptr), The result is: sptr, ptr),The punctuation is not recognized and all is output in the font used by `.Ar'. If the punctuation is separated by a leading white space: .Ar sptr , ptr ) , The result is: sptr, ptr), The punctuation is now recognized and output in the default font distin- guishing it from the argument strings. To remove the special meaning from a punctuation character escape it with `\&'. The following punctuation characters are recognized by -mdoc: . , : ; ( ) [ ] ? ! Troff is limited as a macro language, and has difficulty when presented with a string containing a member of the mathematical, logical or quota- tion set: {+,-,/,*,%,<,>,<=,>=,=,==,&,`,',"} The problem is that troff may assume it is supposed to actually perform the operation or evaluation suggested by the characters. To prevent the accidental evaluation of these characters, escape them with `\&'. Typi- cal syntax is shown in the first content macro displayed below, `.Ad'. MANUAL DOMAIN AddressesThe address macro identifies an address construct. Usage: .Ad <address> ... .Ad addr1 addr1.Ad addr1 . addr1. .Ad addr1 , file2 addr1, file2.Ad f1 , f2 , f3 : f1, f2, f3: .Ad addr ) ) , addr)), The default width is 12n. Author NameThe `.An' macro is used to specify the name of the author of the item being documented, or the name of the author of the actual manual page. Usage: .An <author name> ... .An "Joe Author" Joe Author .An "Joe Author" , Joe Author, .An "Joe Author" Aq nobody@FreeBSD.org Joe Author <nobody@FreeBSD.org> .An "Joe Author" ) ) , Joe Author)), The default width is 12n. In the AUTHORSsection, the `.An' command causes a line break allowing each new name to appear on its own line. If this is not desirable, .An -nosplit call will turn this off. To turn splitting back on, write .An -split ArgumentsThe .Ar argument macro may be used whenever an argument is referenced. If called without arguments, the ` file ...' string is output. Usage: .Ar [<argument>] ... .Ar file ....Ar file1 file1.Ar file1 . file1. .Ar file1 file2 file1 file2.Ar f1 f2 f3 : f1 f2 f3: .Ar file ) ) , file)), The default width is 12n. Configuration Declaration (Section Four Only)The `.Cd' macro is used to demonstrate a [config(8)]declaration for a device interface in a section four manual. Usage: .Cd <argument> ... .Cd "device le0 at scode?" device le0 at scode?In the SYNOPSISsection a `.Cd' command causes a line break before and after its arguments are printed. The default width is 12n. Command ModifiersThe command modifier is identical to the `.Fl' (flag) command with the exception that the `.Cm' macro does not assert a dash in front of every argument. Traditionally flags are marked by the preceding dash, however, some commands or subsets of commands do not use them. Command modifiers may also be specified in conjunction with interactive commands such as editor commands. See Flags. The default width is 10n. Defined VariablesA variable (or constant) which is defined in an include file is specified by the macro `.Dv'. Usage: .Dv <defined variable> ... .Dv MAXHOSTNAMELEN MAXHOSTNAMELEN .Dv TIOCGPGRP ) TIOCGPGRP) The default width is 12n. Errno'sThe `.Er' errno macro specifies the error return value for section 2, 3, and 9 library routines. The second example below shows `.Er' used with the `.Bq' general text domain macro, as it would be used in a section two manual page. Usage: .Er <errno type> ... .Er ENOENT ENOENT .Er ENOENT ) ; ENOENT); .Bq Er ENOTDIR [ENOTDIR] The default width is 17n. Environment VariablesThe `.Ev' macro specifies an environment variable. Usage: .Ev <argument> ... .Ev DISPLAY DISPLAY .Ev PATH . PATH. .Ev PRINTER ) ) , PRINTER)), The default width is 15n. FlagsThe `.Fl' macro handles command line flags. It prepends a dash, `-', to the flag. For interactive command flags, which are not prepended with a dash, the `.Cm' (command modifier) macro is identical, but without the dash. Usage: .Fl <argument> ... .Fl -.Fl cfv -cfv.Fl cfv . -cfv. .Cm cfv . cfv. .Fl s v t -s -v -t.Fl - , --, .Fl xyz ) , -xyz), .Fl | -| The `.Fl' macro without any arguments results in a dash representing stdin/stdout. Note that giving `.Fl' a single dash will result in two dashes. The default width is 12n. Function DeclarationsThe `.Fd' macro is used in the SYNOPSISsection with section two or three functions. It is neither callable nor parsed. Usage: .Fd <argument> ... .Fd "#include <sys/types.h>" #include< sys/types.h> In the SYNOPSISsection a `.Fd' command causes a line break if a function has already been presented and a break has not occurred. This leaves a nice vertical space in between the previous function call and the decla- ration for the next function. The `.In' macro, while in the SYNOPSISsection, represents the #include statement, and is the short form of the above example. It specifies the C header file as being included in a C program. It also causes a line break. While not in the SYNOPSISsection, it represents the header file enclosed in angle brackets. Usage: .In <header file> .In stdio.h #include< stdio.h> .In stdio.h < stdio.h> Function TypesThis macro is intended for the SYNOPSISsection. It may be used anywhere else in the man page without problems, but its main purpose is to present the function type in kernel normal form for the SYNOPSISof sections two and three (it causes a line break, allowing the function name to appear on the next line). Usage: .Ft <type> ... .Ft struct stat struct stat Functions (Library Routines)The `.Fn' macro is modeled on ANSI C conventions. Usage: .Fn <function> [<parameter>] ... .Fn getchar getchar() .Fn strlen ) , strlen()), .Fn align "char *ptr" , align( char *ptr), Note that any call to another macro signals the end of the `.Fn' call (it will insert a closing parenthesis at that point). For functions with many parameters (which is rare), the macros `.Fo' (function open) and `.Fc' (function close) may be used with `.Fa' (func- tion argument). Example: .Ft int .Fo res_mkquery .Fa "int op" .Fa "char *dname" .Fa "int class" .Fa "int type" .Fa "char *data" .Fa "int datalen" .Fa "struct rrec *newrr" .Fa "char *buf" .Fa "int buflen" .Fc Produces: int res_mkquery( int op, char *dname, int class, int type, char *data, int datalen, struct rrec *newrr, char *buf, int buflen) In the SYNOPSISsection, the function will always begin at the beginning of line. If there is more than one function presented in the SYNOPSISsection and a function type has not been given, a line break will occur, leaving a nice vertical space between the current function name and the one prior. The default width values of `.Fn' and `.Fo' are 12n and 16n, respec- tively. Function ArgumentsThe `.Fa' macro is used to refer to function arguments (parameters) out- side of the SYNOPSISsection of the manual or inside the SYNOPSISsection if the enclosure macros `.Fo' and `.Fc' instead of `.Fn' are used. `.Fa' may also be used to refer to structure members. Usage: .Fa <function argument> ... .Fa d_namlen ) ) , d _ namlen)), .Fa iov_len iov _ lenThe default width is 12n. Return ValuesThe `.Rv' macro generates text for use in the RETURN VALUESsection. Usage: .Rv [-std] [<function> ...] For example, `.Rv -std atexit' produces: The atexit() function returns the value 0 if successful; otherwise the value -1 is returned and the global variable errnois set to indicate the error. The -stdoption is valid only for manual page sections 2 and 3. Cur- rently, this macro does nothing if used without the -stdflag. Exit StatusThe `.Ex' macro generates text for use in the DIAGNOSTICSsection. Usage: .Ex [-std] [<utility> ...] For example, `.Ex -std cat' produces: The catutility exits 0 on success, and >0 if an error occurs. The -stdoption is valid only for manual page sections 1, 6 and 8. Cur- rently, this macro does nothing if used without the -stdflag. Interactive CommandsThe `.Ic' macro designates an interactive or internal command. Usage: .Ic <argument> ... .Ic :wq :wq.Ic "do while {...}" do while {...}.Ic setenv , unsetenv setenv, unsetenvThe default width is 12n. Library NamesThe `.Lb' macro is used to specify the library where a particular func- tion is compiled in. Usage: .Lb <argument> ... Available arguments to `.Lb' and their results are: libarchive Streaming Archive Library (libarchive, -larchive) libarm ARM Architecture Library (libarm, -larm) libarm32 ARM32 Architecture Library (libarm32, -larm32) libbluetooth Bluetooth User Library (libbluetooth, -lbluetooth) libbsm Basic Security Module Library (libbsm, -lbsm) libc Standard C Library (libc, -lc) libc_r Reentrant C Library (libc_r, -lc_r) libcalendar Calendar Arithmetic Library (libcalendar, -lcalendar) libcam Common Access Method User Library (libcam, -lcam) libcdk Curses Development Kit Library (libcdk, -lcdk) libcipher FreeSec Crypt Library (libcipher, -lcipher) libcompat Compatibility Library (libcompat, -lcompat) libcrypt Crypt Library (libcrypt, -lcrypt) libcurses Curses Library (libcurses, -lcurses) libdevinfo Device and Resource Information Utility Library (libdevinfo, -ldevinfo) libdevstat Device Statistics Library (libdevstat, -ldevstat) libdisk Interface to Slice and Partition Labels Library (libdisk, -ldisk) libdwarf DWARF Access Library (libdwarf, -ldwarf) libedit Line Editor and History Library (libedit, -ledit) libelf ELF Parsing Library (libelf, -lelf) libevent Event Notification Library (libevent, -levent) libfetch File Transfer Library (libfetch, -lfetch) libform Curses Form Library (libform, -lform) libgeom Userland API Library for kernel GEOM subsystem (libgeom, -lgeom) libgpib General-Purpose Instrument Bus (GPIB) library (libgpib, -lgpib) libi386 i386 Architecture Library (libi386, -li386) libintl Internationalized Message Handling Library (libintl, -lintl) libipsec IPsec Policy Control Library (libipsec, -lipsec) libipx IPX Address Conversion Support Library (libipx, -lipx) libiscsi iSCSI protocol library (libiscsi, -liscsi) libjail Jail Library (libjail, -ljail) libkiconv Kernel side iconv library (libkiconv, -lkiconv) libkse N:M Threading Library (libkse, -lkse) libkvm Kernel Data Access Library (libkvm, -lkvm) libm Math Library (libm, -lm) libm68k m68k Architecture Library (libm68k, -lm68k) libmagic Magic Number Recognition Library (libmagic, -lmagic) libmd Message Digest (MD4, MD5, etc.) Support Library (libmd, -lmd) libmemstat Kernel Memory Allocator Statistics Library (libmemstat, -lmemstat) libmenu Curses Menu Library (libmenu, -lmenu) libnetgraph Netgraph User Library (libnetgraph, -lnetgraph) libnetpgp Netpgp signing, verification, encryption and decryption (libnetpgp, -lnetpgp) libossaudio OSS Audio Emulation Library (libossaudio, -lossaudio) libpam Pluggable Authentication Module Library (libpam, -lpam) libpcap Packet Capture Library (libpcap, -lpcap) libpci PCI Bus Access Library (libpci, -lpci) libpmc Performance Monitoring Counters Interface Library (libpmc, -lpmc) libposix POSIX Compatibility Library (libposix, -lposix) libprop Property Container Object Library (libprop, -lprop) libpthread POSIX Threads Library (libpthread, -lpthread) libpuffs puffs Convenience Library (libpuffs, -lpuffs) librefuse File System in Userspace Convenience Library (librefuse, -lrefuse) libresolv DNS Resolver Library (libresolv, -lresolv) librpcsec_gss RPC GSS-API Authentication Library (librpcsec_gss, -lrpcsec_gss) librpcsvc RPC Service Library (librpcsvc, -lrpcsvc) librt POSIX Real-time Library (librt, -lrt) libsdp Bluetooth Service Discovery Protocol User Library (libsdp, -lsdp) libssp Buffer Overflow Protection Library (libssp, -lssp) libSystem System Library (libSystem, -lSystem) libtermcap Termcap Access Library (libtermcap, -ltermcap) libterminfo Terminal Information Library (libterminfo, -lterminfo) libthr 1:1 Threading Library (libthr, -lthr) libufs UFS File System Access Library (libufs, -lufs) libugidfw File System Firewall Interface Library (libugidfw, -lugidfw) libulog User Login Record Library (libulog, -lulog) libusbhid USB Human Interface Devices Library (libusbhid, -lusbhid) libutil System Utilities Library (libutil, -lutil) libvgl Video Graphics Library (libvgl, -lvgl) libx86_64 x86_64 Architecture Library (libx86_64, -lx86_64) libz Compression Library (libz, -lz) Local, OS-specific additions might be found in the file mdoc.local; look for strings named `str-Lb-XXX'. `XXX' then denotes the keyword to be used with the `.Lb' macro. In the LIBRARYsection an `.Lb' command causes a line break before and after its arguments are printed. LiteralsThe `.Li' literal macro may be used for special characters, variable con- stants, etc. - anything which should be displayed as it would be typed. Usage: .Li <argument> ... .Li \en \n .Li M1 M2 M3 ; M1 M2 M3; .Li cntrl-D ) , cntrl-D), .Li 1024 ... 1024 ... The default width is 16n. NamesThe `.Nm' macro is used for the document title or subject name. It has the peculiarity of remembering the first argument it was called with, which should always be the subject name of the page. When called without arguments, `.Nm' regurgitates this initial name for the sole purpose of making less work for the author. `.Nm' causes a line break within the SYNOPSISsection. Note: A section two or three document function name is addressed with the `.Nm' in the NAMEsection, and with `.Fn' in the SYNOPSISand remaining sections. For interactive commands, such as the `while' command keyword in [csh(1)], the `.Ic' macro should be used. While `.Ic' is nearly identi- cal to `.Nm', it can not recall the first argument it was invoked with. Usage: .Nm [<argument>] ... .Nm groff_mdoc groff_mdoc.Nm \-mdoc -mdoc.Nm foo ) ) , foo)), .Nm : groff_mdoc: The default width is 10n. OptionsThe `.Op' macro places option brackets around any remaining arguments on the command line, and places any trailing punctuation outside the brack- ets. The macros `.Oo' and `.Oc' (which produce an opening and a closing option bracket respectively) may be used across one or more lines or to specify the exact position of the closing parenthesis. Usage: .Op [<option>] ... .Op [] .Op Fl k [ -k] .Op Fl k ) . [ -k]). .Op Fl k Ar kookfile [ -k kookfile] .Op Fl k Ar kookfile , [ -k kookfile], .Op Ar objfil Op Ar corfil [ objfil[ corfil]] .Op Fl c Ar objfil Op Ar corfil , [ -c objfil[ corfil]], .Op word1 word2 [word1 word2] .Li .Op Oo Ao option Ac Oc ... .Op [<option>] ... Here a typical example of the `.Oo' and `.Oc' macros: .Oo .Op Fl k Ar kilobytes .Op Fl i Ar interval .Op Fl c Ar count .Oc Produces: [[ -k kilobytes] [ -i interval] [ -c count]] The default width values of `.Op' and `.Oo' are 14n and 10n, respec- tively. PathnamesThe `.Pa' macro formats path or file names. If called without arguments, the ` ~' string is output, which represents the current user's home direc- tory. Usage: .Pa [<pathname>] ... .Pa ~.Pa /usr/share /usr/share.Pa /tmp/fooXXXXX ) . /tmp/fooXXXXX). The default width is 32n. StandardsThe `.St' macro replaces standard abbreviations with their formal names. Usage: .St <abbreviation> ... Available pairs for ``Abbreviation/Formal Name'' are: ANSI/ISO C -ansiC ANSI X3.159-1989 (``ANSI C89'') -ansiC-89 ANSI X3.159-1989 (``ANSI C89'') -isoC ISO/IEC 9899:1990 (``ISO C90'') -isoC-90 ISO/IEC 9899:1990 (``ISO C90'') -isoC-99 ISO/IEC 9899:1999 (``ISO C99'') -isoC-2011 ISO/IEC 9899:2011 (``ISO C11'') POSIX Part 1: System API -iso9945-1-90 ISO/IEC 9945-1:1990 (``POSIX.1'') -iso9945-1-96 ISO/IEC 9945-1:1996 (``POSIX.1'') -p1003.1 IEEE Std 1003.1 (``POSIX.1'') -p1003.1-88 IEEE Std 1003.1-1988 (``POSIX.1'') -p1003.1-90 ISO/IEC 9945-1:1990 (``POSIX.1'') -p1003.1-96 ISO/IEC 9945-1:1996 (``POSIX.1'') -p1003.1b-93 IEEE Std 1003.1b-1993 (``POSIX.1'') -p1003.1c-95 IEEE Std 1003.1c-1995 (``POSIX.1'') -p1003.1g-2000 IEEE Std 1003.1g-2000 (``POSIX.1'') -p1003.1i-95 IEEE Std 1003.1i-1995 (``POSIX.1'') -p1003.1-2001 IEEE Std 1003.1-2001 (``POSIX.1'') -p1003.1-2004 IEEE Std 1003.1-2004 (``POSIX.1'') -p1003.1-2008 IEEE Std 1003.1-2008 (``POSIX.1'') POSIX Part 2: Shell and Utilities -iso9945-2-93 ISO/IEC 9945-2:1993 (``POSIX.2'') -p1003.2 IEEE Std 1003.2 (``POSIX.2'') -p1003.2-92 IEEE Std 1003.2-1992 (``POSIX.2'') -p1003.2a-92 IEEE Std 1003.2a-1992 (``POSIX.2'') X/Open -susv2 Version 2 of the Single UNIX Specification (``SUSv2'') -susv3 Version 3 of the Single UNIX Specification (``SUSv3'') -svid4 System V Interface Definition, Fourth Edition (``SVID4'') -xbd5 X/Open Base Definitions Issue 5 (``XBD5'') -xcu5 X/Open Commands and Utilities Issue 5 (``XCU5'') -xcurses4.2 X/Open Curses Issue 4, Version 2 (``XCURSES4.2'') -xns5 X/Open Networking Services Issue 5 (``XNS5'') -xns5.2 X/Open Networking Services Issue 5.2 (``XNS5.2'') -xpg3 X/Open Portability Guide Issue 3 (``XPG3'') -xpg4 X/Open Portability Guide Issue 4 (``XPG4'') -xpg4.2 X/Open Portability Guide Issue 4, Version 2 (``XPG4.2'') -xsh5 X/Open System Interfaces and Headers Issue 5 (``XSH5'') Miscellaneous -ieee754 IEEE Std 754-1985 -iso8802-3 ISO/IEC 8802-3:1989 Variable TypesThe `.Vt' macro may be used whenever a type is referenced. In the SYNOPSISsection, it causes a line break (useful for old style variable declarations). Usage: .Vt <type> ... .Vt extern char *optarg ; extern char *optarg; .Vt FILE * FILE * VariablesGeneric variable reference. Usage: .Va <variable> ... .Va count count.Va settimer , settimer, .Va "int *prt" ) : int *prt): .Va "char s" ] ) ) , char s])), The default width is 12n. Manual Page Cross ReferencesThe `.Xr' macro expects the first argument to be a manual page name. The optional second argument, if a string (defining the manual section), is put into parentheses. Usage: .Xr <man page name> [<section>] ... .Xr mdoc mdoc .Xr mdoc , mdoc, .Xr mdoc 7 [mdoc(7)].Xr xinit 1x ; [xinit(1x)]; The default width is 10n. GENERAL TEXT DOMAIN AT& T MacroUsage: .At [<version>] ... .At AT&T UNIX .At v6 . Version 6 AT&T UNIX. The following values for <version> are possible: 32v, v1, v2, v3, v4, v5, v6, v7, V, V.1, V.2, V.3, V.4 BSD MacroUsage: .Bx {-alpha | -beta | -devel} ... .Bx [<version> [<release>]] ... .Bx BSD .Bx 4.3 . 4.3BSD. .Bx -devel BSD (currently under development) <version> will be prepended to the string `BSD'. The following values for <release> are possible: Reno, reno, Tahoe, tahoe, Lite, lite, Lite2, lite2 NetBSD MacroUsage: .Nx [<version>] ... .Nx NetBSD .Nx 1.4 . NetBSD 1.4. For possible values of <version> see the description of the `.Os' command above in section TITLE MACROS. FreeBSD MacroUsage: .Fx [<version>] ... .Fx FreeBSD .Fx 2.2 . FreeBSD 2.2. For possible values of <version> see the description of the `.Os' command above in section TITLE MACROS. DragonFly MacroUsage: .Dx [<version>] ... .Dx DragonFly .Dx 1.4 . DragonFly 1.4. For possible values of <version> see the description of the `.Os' command above in section TITLE MACROS. OpenBSD MacroUsage: .Ox [<version>] ... .Ox 1.0 OpenBSD 1.0 BSD/OS MacroUsage: .Bsx [<version>] ... .Bsx 1.0 BSD/OS 1.0 UNIX MacroUsage: .Ux ... .Ux UNIX Emphasis MacroText may be stressed or emphasized with the `.Em' macro. The usual font for emphasis is italic. Usage: .Em <argument> ... .Em does not does not.Em exceed 1024 . exceed 1024. .Em vide infra ) ) , vide infra)), The default width is 10n. Font ModeThe `.Bf' font mode must be ended with the `.Ef' macro (the latter takes no arguments). Font modes may be nested within other font modes. `.Bf' has the following syntax: .Bf <font mode> <font mode> must be one of the following three types: Em| -emphasisSame as if the `.Em' macro was used for the entire block of text. Li| -literalSame as if the `.Li' macro was used for the entire block of text. Sy| -symbolicSame as if the `.Sy' macro was used for the entire block of text. Both macros are neither callable nor parsed. Enclosure and Quoting MacrosThe concept of enclosure is similar to quoting. The object being to enclose one or more strings between a pair of characters like quotes or parentheses. The terms quoting and enclosure are used interchangeably throughout this document. Most of the one-line enclosure macros end in small letter `q' to give a hint of quoting, but there are a few irregu- larities. For each enclosure macro there is also a pair of open and close macros which end in small letters `o' and `c' respectively. Quote Open Close Function Result.Aq .Ao .Ac Angle Bracket Enclosure <string> .Bq .Bo .Bc Bracket Enclosure [string] .Brq .Bro .Brc Brace Enclosure {string} .Dq .Do .Dc Double Quote ``string'' .Eq .Eo .Ec Enclose String (in XX) XXstringXX .Pq .Po .Pc Parenthesis Enclosure (string) .Ql Quoted Literal `string' or string .Qq .Qo .Qc Straight Double Quote "string" .Sq .So .Sc Single Quote `string' All macros ending with `q' and `o' have a default width value of 12n. .Eo, .Ec These macros expect the first argument to be the opening and closing strings respectively. .Es, .En Due to the nine-argument limit in the original troff program two other macros have been implemented which are now rather obsolete: `.Es' takes the first and second parameter as the left and right enclosure string, which are then used to enclose the arguments of `.En'. The default width value is 12n for both macros. .Eq The first and second arguments of this macro are the opening and closing strings respectively, followed by the arguments to be enclosed. .Ql The quoted literal macro behaves differently in troff and nroff mode. If formatted with nroff, a quoted literal is always quoted. If formatted with troff, an item is only quoted if the width of the item is less than three constant width characters. This is to make short strings more visible where the font change to literal (constant width) is less noticeable. The default width is 16n. .Pf The prefix macro suppresses the whitespace between its first and second argument: .Pf ( Fa name2 ( name2The default width is 12n. The `.Ns' macro (see below) performs the analogous suffix func- tion. .Ap The `.Ap' macro inserts an apostrophe and exits any special text modes, continuing in `.No' mode. Examples of quoting: .Aq <> .Aq Pa ctype.h ) , < ctype.h>), .Bq [] .Bq Em Greek , French . [ Greek, French]. .Dq ``'' .Dq string abc . ``string abc''. .Dq '^[A-Z]' ``'^[A-Z]''' .Ql man mdoc `man mdoc' .Qq "" .Qq string ) , "string"), .Qq string Ns ), "string)," .Sq `' .Sq string `string' .Em or Ap ing or'ing For a good example of nested enclosure macros, see the `.Op' option macro. It was created from the same underlying enclosure macros as those presented in the list above. The `.Xo' and `.Xc' extended argument list macros are discussed below. No-Op or Normal Text MacroThe `.No' macro can be used in a macro command line for parameters which should notbe formatted. Be careful to add `\&' to the word `No' if you really want that English word (and not the macro) as a parameter. Usage: .No <argument> ... .No test Ta with Ta tabs test with tabs The default width is 12n. No-Space MacroThe `.Ns' macro suppresses insertion of a space between the current posi- tion and its first parameter. For example, it is useful for old style argument lists where there is no space between the flag and argument: Usage: ... <argument> Ns [<argument>] ... .Ns <argument> ... .Op Fl I Ns Ar directory [ -I directory] Note: The `.Ns' macro always invokes the `.No' macro after eliminating the space unless another macro name follows it. If used as a command (i.e., the second form above in the `Usage' line), `.Ns' is identical to `.No'. Section Cross ReferencesThe `.Sx' macro designates a reference to a section header within the same document. Usage: .Sx <section reference> ... .Sx FILES FILESThe default width is 16n. SymbolicsThe symbolic emphasis macro is generally a boldface macro in either the symbolic sense or the traditional English usage. Usage: .Sy <symbol> ... .Sy Important Notice Important NoticeThe default width is 6n. Mathematical SymbolsUse this macro for mathematical symbols and similar things. Usage: .Ms <math symbol> ... .Ms sigma sigmaThe default width is 6n. References and CitationsThe following macros make a modest attempt to handle references. At best, the macros make it convenient to manually drop in a subset of [refer(1)]style references. .Rs Reference start (does not take arguments). Causes a line break in the SEE ALSOsection and begins collection of ref- erence information until the reference end macro is read. .Re Reference end (does not take arguments). The reference is printed. .%A Reference author name; one name per invocation. .%B Book title. .%C City/place (not implemented yet). .%D Date. .%I Issuer/publisher name. .%J Journal name. .%N Issue number. .%O Optional information. .%P Page number. .%Q Corporate or foreign author. .%R Report name. .%T Title of article. .%U Optional hypertext reference. .%V Volume. Macros beginning with `%' are not callable but accept multiple arguments in the usual way. Only the `.Tn' macro is handled properly as a parame- ter; other macros will cause strange output. `.%B' and `.%T' can be used outside of the `.Rs/.Re' environment. Example: .Rs .%A "Matthew Bar" .%A "John Foo" .%T "Implementation Notes on [foobar(1)]" .%R "Technical Report ABC-DE-12-345" .%Q "Drofnats College, Nowhere" .%D "April 1991" .Re produces Matthew Bar and John Foo, Implementation Notes on [, Technical Report ABC-DE-12-345, Drofnats College, Nowhere, April 1991.] foobar(1) Trade Names (or Acronyms and Type Names)The trade name macro prints its arguments in a smaller font. Its intended use is to imitate a small caps fonts for uppercase acronyms. Usage: .Tn <symbol> ... .Tn DEC DEC .Tn ASCII ASCII The default width is 10n. Extended ArgumentsThe .Xo and .Xc macros allow one to extend an argument list on a macro boundary for the `.It' macro (see below). Note that .Xo and .Xc are implemented similarly to all other macros opening and closing an enclo- sure (without inserting characters, of course). This means that the fol- lowing is true for those macros also. Here is an example of `.Xo' using the space mode macro to turn spacing off: .Sm off .It Xo Sy I Ar operation .No \en Ar count No \en .Xc .Sm on produces I operation\n count\n Another one: .Sm off .It Cm S No / Ar old_pattern Xo .No / Ar new_pattern .No / Op Cm g .Xc .Sm on produces S/ old _ pattern/ new _ pattern/[ g] Another example of `.Xo' and enclosure macros: Test the value of a vari- able. .It Xo .Ic .ifndef .Oo \&! Oc Ns Ar variable Oo .Ar operator variable ... .Oc Xc produces .ifndef[!] variable[ operator variable ...] PAGE STRUCTURE DOMAIN Section HeadersThe following `.Sh' section header macros are required in every man page. The remaining section headers are recommended at the discretion of the author writing the manual page. The `.Sh' macro is parsed but not gener- ally callable. It can be used as an argument in a call to `.Sh' only; it then reactivates the default font for `.Sh'. The default width is 8n. .Sh NAME The `.Sh NAME' macro is mandatory. If not specified, headers, footers and page layout defaults will not be set and things will be rather unpleasant. The NAMEsection consists of at least three items. The first is the `.Nm' name macro naming the subject of the man page. The second is the name description macro, `.Nd', which separates the subject name from the third item, which is the description. The description should be the most terse and lucid possible, as the space available is small. `.Nd' first prints `-', then all its arguments. .Sh LIBRARY This section is for section two and three function calls. It should consist of a single `.Lb' macro call; see Library Names. .Sh SYNOPSIS The SYNOPSISsection describes the typical usage of the subject of a man page. The macros required are either `.Nm', `.Cd', or `.Fn' (and possibly `.Fo', `.Fc', `.Fd', and `.Ft'). The function name macro `.Fn' is required for manual page sections 2 and 3; the command and general name macro `.Nm' is required for sections 1, 5, 6, 7, and 8. Section 4 manuals require a `.Nm', `.Fd' or a `.Cd' configuration device usage macro. Several other macros may be necessary to produce the synopsis line as shown below: cat[ -benstuv] [ -] file ...The following macros were used: .Nm cat .Op Fl benstuv .Op Fl .Ar .Sh DESCRIPTION In most cases the first text in the DESCRIPTIONsec- tion is a brief paragraph on the command, function or file, followed by a lexical list of options and respective explanations. To create such a list, the `.Bl' (begin list), `.It' (list item) and `.El' (end list) macros are used (see Lists and Columnsbelow). .Sh IMPLEMENTATION NOTES Implementation specific information should be placed here. .Sh RETURN VALUES Sections 2, 3 and 9 function return values should go here. The `.Rv' macro may be used to generate text for use in the RETURN VALUESsection for most section 2 and 3 library functions; see Return Values. The following `.Sh' section headers are part of the preferred manual page layout and must be used appropriately to maintain consistency. They are listed in the order in which they would be used. .Sh ENVIRONMENT The ENVIRONMENTsection should reveal any related environment variables and clues to their behavior and/or usage. .Sh FILES Files which are used or created by the man page sub- ject should be listed via the `.Pa' macro in the FILESsection. .Sh EXAMPLES There are several ways to create examples. See the EXAMPLESsection below for details. .Sh DIAGNOSTICS Diagnostic messages from a command should be placed in this section. The `.Ex' macro may be used to generate text for use in the DIAGNOSTICSsection for most sec- tion 1, 6 and 8 commands; see Exit Status. .Sh COMPATIBILITY Known compatibility issues (e.g. deprecated options or parameters) should be listed here. .Sh ERRORS Specific error handling, especially from library func- tions (man page sections 2, 3, and 9) should go here. The `.Er' macro is used to specify an error (errno). .Sh SEE ALSO References to other material on the man page topic and cross references to other relevant man pages should be placed in the SEE ALSOsection. Cross references are specified using the `.Xr' macro. Currently [refer(1)]style references are not accommodated. It is recommended that the cross references are sorted on the section number, then alphabetically on the names within a section, and placed in that order and comma separated. Example: [ls(1)], [ps(1)], [group(5)], [passwd(5)].Sh STANDARDS If the command, library function or file adheres to a specific implementation such as IEEE Std 1003.2 (``POSIX.2'') or ANSI X3.159-1989 (``ANSI C89'') this should be noted here. If the command does not adhere to any standard, its history should be noted in the HISTORYsection. .Sh HISTORY Any command which does not adhere to any specific standards should be outlined historically in this sec- tion. .Sh AUTHORS Credits should be placed here. Use the `.An' macro for names and the `.Aq' macro for e-mail addresses within optional contact information. Explicitly indi- cate whether the person authored the initial manual page or the software or whatever the person is being credited for. .Sh BUGS Blatant problems with the topic go here. User-specified `.Sh' sections may be added; for example, this section was set with: .Sh "PAGE STRUCTURE DOMAIN" Subsection HeadersSubsection headers have exactly the same syntax as section headers: `.Ss' is parsed but not generally callable. It can be used as an argument in a call to `.Ss' only; it then reactivates the default font for `.Ss'. The default width is 8n. Paragraphs and Line Spacing.Pp The `.Pp' paragraph command may be used to specify a line space where necessary. The macro is not necessary after a `.Sh' or `.Ss' macro or before a `.Bl' or `.Bd' macro (which both assert a vertical distance unless the -compactflag is given). The macro is neither callable nor parsed and takes no arguments; an alternative name is `.Lp'. KeepsThe only keep that is implemented at this time is for words. The macros are `.Bk' (begin keep) and `.Ek' (end keep). The only option that `.Bk' accepts currently is -words(this is also the default if no option is given) which is useful for preventing line breaks in the middle of options. In the example for the make command line arguments (see What's in a Name), the keep prevented nroff from placing up the flag and the argument on separate lines. Both macros are neither callable nor parsed. More work needs to be done with the keep macros; specifically, a -lineoption should be added. Examples and DisplaysThere are seven types of displays. .D1 (This is D-one.) Display one line of indented text. This macro is parsed but not callable. -ldghfstruThe above was produced by: .D1 Fl ldghfstru. .Dl (This is D-ell.) Display one line of indented literaltext. The `.Dl' example macro has been used throughout this file. It allows the indentation (display) of one line of text. Its default font is set to constant [width (literal)]. `.Dl' is parsed but not callable. % ls -ldg /usr/local/bin The above was produced by: .Dl % ls \-ldg /usr/local/bin. .Bd Begin display. The `.Bd' display must be ended with the `.Ed' macro. It has the following syntax: .Bd {-literal | -filled | -unfilled | -ragged | -centered} [-offset <string>] [-file <file name>] [-compact] -raggedFill, but do not adjust the right margin (only left-justify). -centeredCenter lines between the current left and right margin. Note that each single line is centered. -unfilledDo not fill; display a block of text as typed, using line breaks as specified by the user. This can produce overlong lines without warning mes- sages. -filledDisplay a filled block. The block of text is formatted (i.e., the text is justified on both the left and right side). -literalDisplay block with literal font (usually fixed- width). Useful for source code or simple tabbed or spaced text. -file< file name> The file whose name follows the -fileflag is read and displayed before any data enclosed with `.Bd' and `.Ed', using the selected display type. Any troff/ -mdoccommands in the file will be pro- cessed. -offset< string> If -offsetis specified with one of the following strings, the string is interpreted to indicate the level of indentation for the forthcoming block of text: leftAlign block on the current left mar- gin; this is the default mode of `.Bd'. centerSupposedly center the block. At this time unfortunately, the block merely gets left aligned about an imaginary center margin. indentIndent by one default indent value or tab. The default indent value is also used for the `.D1' and `.Dl' macros, so one is guaranteed the two types of displays will line up. The indentation value is normally set to 6n or about two thirds of an inch (six constant width characters). indent-twoIndent two times the default indent value. rightThis leftaligns the block about two inches from the right side of the page. This macro needs work and per- haps may never do the right thing within troff. If <string> is a valid numeric expression instead ( with a scale indicator other than` u'), use that value for indentation. The most useful scale indicators are `m' and `n', specifying the so- called Emand En square. This is approximately the width of the letters `m' and `n' respectively of the current font (for nroff output, both scale indicators give the same values). If <string> isn't a numeric expression, it is tested whether it is an -mdocmacro name, and the default offset value associated with this macro is used. Finally, if all tests fail, the width of <string> (typeset with a fixed-width font) is taken as the offset. -compactSuppress insertion of vertical space before begin of display. .Ed End display (takes no arguments). Lists and ColumnsThere are several types of lists which may be initiated with the `.Bl' begin-list macro. Items within the list are specified with the `.It' item macro, and each list must end with the `.El' macro. Lists may be nested within themselves and within displays. The use of columns inside of lists or lists inside of columns is unproven. In addition, several list attributes may be specified such as the width of a tag, the list offset, and compactness (blank lines between items allowed or disallowed). Most of this document has been formatted with a tag style list ( -tag). It has the following syntax forms: .Bl {-hang | -ohang | -tag | -diag | -inset} [-width <string>] [-offset <string>] [-compact] .Bl -column [-offset <string>] <string1> <string2> ... .Bl {-item | -enum [-nested] | -bullet | -hyphen | -dash} [-offset <string>] [-compact] And now a detailed description of the list types. -bulletA bullet list. .Bl -bullet -offset indent -compact .It Bullet one goes here. .It Bullet two here. .El Produces: +o Bullet one goes here. +o Bullet two here. -dash(or -hyphen) A dash list. .Bl -dash -offset indent -compact .It Dash one goes here. .It Dash two here. .El Produces: -Dash one goes here. -Dash two here. -enumAn enumerated list. .Bl -enum -offset indent -compact .It Item one goes here. .It And item two here. .El The result: 1. Item one goes here. 2. And item two here. If you want to nest enumerated lists, use the -nestedflag (starting with the second-level list): .Bl -enum -offset indent -compact .It Item one goes here .Bl -enum -nested -compact .It Item two goes here. .It And item three here. .El .It And item four here. .El Result: 1. Item one goes here. 1.1. Item two goes here. 1.2. And item three here. 2. And item four here. -itemA list of type -itemwithout list markers. .Bl -item -offset indent .It Item one goes here. Item one goes here. Item one goes here. .It Item two here. Item two here. Item two here. .El Produces: Item one goes here. Item one goes here. Item one goes here. Item two here. Item two here. Item two here. -tagA list with tags. Use -widthto specify the tag width. SL sleep time of the process (seconds blocked) PAGEIN number of disk I/O's resulting from references by the process to pages not loaded in core. UID numerical user-id of process owner PPID numerical id of parent of process priority (non-pos- itive when in non-interruptible wait) The raw text: .Bl -tag -width "PPID" -compact -offset indent .It SL sleep time of the process (seconds blocked) .It PAGEIN number of disk .Tn I/O Ns 's resulting from references by the process to pages not loaded in core. .It UID numerical user-id of process owner .It PPID numerical id of parent of process priority (non-positive when in non-interruptible wait) .El -diagDiag lists create section four diagnostic lists and are similar to inset lists except callable macros are ignored. The -widthflag is not meaningful in this context. Example: .Bl -diag .It You can't use Sy here. The message says all. .El produces You can't use Sy here.The message says all. -hangA list with hanging tags. Hangedlabels appear similar to tagged lists when the label is smaller than the label width. Longer hanged list labelsblend into the paragraph unlike tagged paragraph labels. And the unformatted text which created it: .Bl -hang -offset indent .It Em Hanged labels appear similar to tagged lists when the label is smaller than the label width. .It Em Longer hanged list labels blend into the paragraph unlike tagged paragraph labels. .El -ohangLists with overhanging tags do not use indentation for the items; tags are written to a separate line. SLsleep time of the process (seconds blocked) PAGEINnumber of disk I/O's resulting from references by the process to pages not loaded in core. UIDnumerical user-id of process owner PPIDnumerical id of parent of process priority (non-positive when in non-interruptible wait) The raw text: .Bl -ohang -offset indent .It Sy SL sleep time of the process (seconds blocked) .It Sy PAGEIN number of disk .Tn I/O Ns 's resulting from references by the process to pages not loaded in core. .It Sy UID numerical user-id of process owner .It Sy PPID numerical id of parent of process priority (non-positive when in non-interruptible wait) .El -insetHere is an example of inset labels: TagThe tagged list (also called a tagged paragraph) is the most common type of list used in the Berkeley manuals. Use a -widthattribute as described below. DiagDiag lists create section four diagnostic lists and are similar to inset lists except callable macros are ignored. HangHanged labels are a matter of taste. OhangOverhanging labels are nice when space is con- strained. InsetInset labels are useful for controlling blocks of paragraphs and are valuable for converting -mdocmanuals to other formats. Here is the source text which produced the above example: .Bl -inset -offset indent .It Em Tag The tagged list (also called a tagged paragraph) is the most common type of list used in the Berkeley manuals. .It Em Diag Diag lists create section four diagnostic lists and are similar to inset lists except callable macros are ignored. .It Em Hang Hanged labels are a matter of taste. .It Em Ohang Overhanging labels are nice when space is constrained. .It Em Inset Inset labels are useful for controlling blocks of paragraphs and are valuable for converting .Nm -mdoc manuals to other formats. .El -columnThis list type generates multiple columns. The number of col- umns and the width of each column is determined by the arguments to the -columnlist, < string1>, < string2>, etc. If < stringN> starts with a `.' (dot) immediately followed by a valid -mdocmacro name, interpret < stringN> and use the width of the result. Otherwise, the width of < stringN> (typeset with a fixed-width font) is taken as the Nth column width. Each `.It' argument is parsed to make a row, each column within the row is a separate argument separated by a tab or the `.Ta' macro. The table: String Nroff Troff<= <= <= >= >= >= was produced by: .Bl -column -offset indent ".Sy String" ".Sy Nroff" ".Sy Troff" .It Sy String Ta Sy Nroff Ta Sy Troff .It Li <= Ta <= Ta \*(<= .It Li >= Ta >= Ta \*(>= .El Don't abuse this list type! For more complicated cases it might be far better and easier to use [tbl(1)], the table preprocessor. Other keywords: -width< string> If < string> starts with a `.' (dot) immediately fol- lowed by a valid -mdocmacro name, interpret < string> and use the width of the result. Almost all lists in this document use this option. Example: .Bl -tag -width ".Fl test Ao Ar string Ac" .It Fl test Ao Ar string Ac This is a longer sentence to show how the .Fl width flag works in combination with a tag list. .El gives: -test< string> This is a longer sentence to show how the -widthflag works in combination with a tag list. (Note that the current state of -mdocis saved before < string> is interpreted; afterwards, all variables are restored again. However, boxes (used for enclosures) can't be saved in GNU [troff(1)]; as a consequence, argu- ments must always be balancedto avoid nasty errors. For example, do not write `.Ao Ar string' but `.Ao Ar string Xc' instead if you really need only an opening angle bracket.) Otherwise, if < string> is a valid numeric expression ( with a scale indicator other than` u'), use that value for indentation. The most useful scale indicators are `m' and `n', specifying the so-called Emand En square. This is approximately the width of the letters `m' and `n' respectively of the current font (for nroff output, both scale indicators give the same values). If < string> isn't a numeric expression, it is tested whether it is an -mdocmacro name, and the default width value associated with this macro is used. Finally, if all tests fail, the width of < string> (typeset with a fixed-width font) is taken as the width. If a width is not specified for the tag list type, every time `.It' is invoked, an attempt is made to determine an appropriate width. If the first argument to `.It' is a callable macro, the default width for that macro will be used; otherwise, the default width of `.No' is used. -offset< string> If < string> is indent, a default indent value (normally set to 6n, similar to the value used in `.Dl' or `.Bd') is used. If < string> is a valid numeric expression instead ( with a scale indicator other than` u'), use that value for indentation. The most useful scale indicators are `m' and `n', specifying the so-called Emand En square. This is approximately the width of the letters `m' and `n' respectively of the current font (for nroff output, both scale indicators give the same values). If < string> isn't a numeric expression, it is tested whether it is an -mdocmacro name, and the default offset value associated with this macro is used. Finally, if all tests fail, the width of < string> (typeset with a fixed-width font) is taken as the offset. -compactSuppress insertion of vertical space before the list and between list items. [Here a list of the remaining macros which do not fit well into one of the above sections. We couldn't find real examples for the following macros: `.Me' and `.Ot'. They are documented here for completeness - if you know how to use them properly please send a mail to] MISCELLANEOUS MACROS bug-groff@gnu.org(includ- ing an example). .Bt prints is currently in beta test. It is neither callable nor parsed and takes no arguments. .Fr Usage: .Fr <function return value> ... Don't use this macro. It allows a break right before the return value (usually a single digit) which is bad typographical behaviour. Use `\~' to tie the return value to the previous word. .Hf Use this macro to include a (header) file literally. It first prints `File:' followed by the file name, then the contents of <file>. Usage: .Hf <file> It is neither callable nor parsed. .Lk To be written. .Me Exact usage unknown. The documentation in the -mdocsource file describes it as a macro for ``menu entries''. Its default width is 6n. .Mt To be written. .Ot Exact usage unknown. The documentation in the -mdocsource file describes it as ``old function type (fortran)''. .Sm Activate (toggle) space mode. Usage: .Sm [on | off] ... If space mode is off, no spaces between macro arguments are inserted. If called without a parameter (or if the next parameter is neither `on' nor `off', `.Sm' toggles space mode. .Ud prints currently under development. It is neither callable nor parsed and takes no arguments. [The following strings are predefined:] PREDEFINED STRINGS String Nroff Troff Meaning<= <= <= less equal >= >= >= greater equal Rq '' '' right double quote Lq `` `` left double quote ua ^ ^ upwards arrow aa ' ' acute accent ga ` ` grave accent q " " straight double quote Pi pi pi greek pi Ne != != not equal Le <= <= less equal Ge >= >= greater equal Lt < < less than Gt > > greater than Pm +- +- plus minus If infinity infinity infinity Am & & ampersand Na NaN NaNnot a number Ba | | vertical bar The names of the columns Nroffand Troffare a bit misleading; Nroffshows the ASCII representation, while Troffgives the best glyph form available. For example, a Unicode enabled TTY-device will have proper glyph representations for all strings, whereas the enhancement for a Latin1 TTY-device is only the plus-minus sign. String names which consist of two characters can be written as `\*(xx'; string names which consist of one character can be written as `\*x'. A generic syntax for a string name of any length is `\*[xxx]' (this is a GNU [troff(1)]extension). [The debugging macro `.Db' available in previous versions of] DIAGNOSTICS -mdochas been removed since GNU [troff(1)]provides better facilities to check parameters; additionally, many error and warning messages have been added to this macro package, making it both more robust and verbose. The only remaining debugging macro is `.Rd' which yields a register dump of all global registers and strings. A normal user will never need it. [By default, the package inhibits page breaks, headers, and footers if displayed with a TTY device like `latin1' or `unicode', to make the man- ual more efficient for viewing on-line. This behaviour can be changed (e.g. to create a hardcopy of the TTY output) by setting the register `cR' to zero while calling] FORMATTING WITH GROFF, TROFF, AND NROFF [groff(1)], resulting in multiple pages instead of a single, very long page: groff -Tlatin1 -rcR=0 -mdoc foo.man > foo.txt For double-sided printing, set register `D' to 1: groff -Tps -rD1 -mdoc foo.man > foo.ps To change the document font size to 11pt or 12pt, set register `S' accordingly: groff -Tdvi -rS11 -mdoc foo.man > foo.dvi Register `S' is ignored for TTY devices. The line and title length can be changed by setting the registers `LL' and `LT', respectively: groff -Tutf8 -rLL=100n -rLT=100n -mdoc foo.man | less If not set, both registers default to 78n for TTY devices and 6.5i other- wise. [doc.tmac The main manual macro package. mdoc.tmac A wrapper file to call] FILES doc.tmac. mdoc/doc-common Common strings, definitions, stuff related typographic output. mdoc/doc-nroff Definitions used for a TTY output device. mdoc/doc-ditroff Definitions used for all other devices. mdoc.local Local additions and customizations. andoc.tmac Use this file if you don't know whether the -mdocor the -manpackage should be used. Multiple man pages (in either format) can be handled. SEE ALSO [groff(1)], [man(1)], [troff(1)], [groff_man(7)] [Section 3f has not been added to the header routines. `.Nm' font should be changed in] BUGS NAMEsection. `.Fn' needs to have a check to prevent splitting up if the line length is too short. Occasionally it separates the last parenthesis, and sometimes looks ridiculous if a line is in fill mode. The list and display macros do not do any keeps and certainly should be able to. FreeBSD 9.3 November 2, 2010 FreeBSD 9.3 [NAME](#NAME)| [SYNOPSIS](#SYNOPSIS)| [DESCRIPTION](#DESCRIPTION)| [GETTING STARTED](#GETTING%09STARTED)| [TROFF IDIOSYNCRASIES](#TROFF_IDIOSYNCRASIES)| [A MANUAL PAGE TEMPLATE](#A_MANUAL_PAGE_TEMPLATE)| [CONVENTIONS](#CONVENTIONS)| [TITLE MACROS](#TITLE_MACROS)| [INTRODUCTION OF MANUAL AND GENERAL TEXT DOMAINS](#INTRODUCTION_OF%09MANUAL_AND_GENERAL_TEXT%09DOMAINS)| [MANUAL DOMAIN](#MANUAL_DOMAIN)| [GENERAL TEXT DOMAIN](#GENERAL%09TEXT_DOMAIN)| [PAGE STRUCTURE DOMAIN](#PAGE_STRUCTURE_DOMAIN)| [MISCELLANEOUS MACROS](#MISCELLANEOUS_MACROS)| [PREDEFINED STRINGS](#PREDEFINED_STRINGS)| [DIAGNOSTICS](#DIAGNOSTICS)| [FORMATTING WITH GROFF, TROFF, AND NROFF](#FORMATTING_WITH%09GROFF,_TROFF,_AND_NROFF)| [FILES](#FILES)| [SEE ALSO](#SEE_ALSO)| [BUGS](#BUGS)
Want to link to this manual page? Use this URL:
<
[http://www.freebsd.org/cgi/man.cgi?query=groff_mdoc&sektion=7&manpath=FreeBSD+9.2-RELEASE](http://www.freebsd.org/cgi/man.cgi?query=groff_mdoc&sektion=7&manpath=FreeBSD+9.2-RELEASE)> [home](/cgi/man.cgi?manpath=)| [help](/cgi/man.cgi/help.html)

Via: 1.1 wfe0.ysv.FreeBSD.org

X-Cache: MISS


markdown:
TRANG CHỦ
|
Bảng xếp hạng
|
Thao tác
|
Vào nhanh diễn đàn game
Đánh dấu đã đọc diễn đàn
Nội dung
» Bạn có thể đăng nhập diễn đàn bằng tài khoản
Go ID
» Nếu chưa có tài khoản,
click vào đây để đăng ký
.
» Vui lòng tuân thủ
Quy định diễn đàn Mạng Việt Nam
.
Nội dung
Bạn chưa đăng nhập hoặc bạn không có quyền truy cập trang này với những lý do sau:
Bạn chưa đăng nhập. Xin điền những thông tin ở dưới để tiếp tục.
Bạn không được quyền truy cập trang này.
Tài khoản của bạn đang bị khóa.
The administrator may have required you to
register
before you can view this page.
Đăng nhập
Tài khoản:
Mật khẩu:
Ghi nhớ?
Diễn đàn Việt Nam
Lên trên

Pragma: private

Connection: keep-alive

Content-Type: text/html; charset=iso-8859-1

Keep-Alive: timeout=3, max=20