Print man pages with fixed widthDifferences between man pagesMan page with preserved text decorations, proportional text and fixed-width codeSearching in man pagesMan-pages don't include all relevant informationMan pages are shuffledSplit lines inside files with fixed width columnsReinstall man pages & fix manawk - , fixed width columnsPaginate man pagesHow to search a pattern containing hyphens inside man pages?

Theorems that impeded progress

SSH "lag" in LAN on some machines, mixed distros

How to say in German "enjoying home comforts"

Today is the Center

Doing something right before you need it - expression for this?

Emailing HOD to enhance faculty application

What reasons are there for a Capitalist to oppose a 100% inheritance tax?

Can a rocket refuel on Mars from water?

Is Lorentz symmetry broken if SUSY is broken?

Twin primes whose sum is a cube

Is the Joker left-handed?

Arrow those variables!

Why does Arabsat 6A need a Falcon Heavy to launch

I Accidentally Deleted a Stock Terminal Theme

How can saying a song's name be a copyright violation?

Blender 2.8 I can't see vertices, edges or faces in edit mode

Western buddy movie with a supernatural twist where a woman turns into an eagle at the end

What does it mean to describe someone as a butt steak?

Brothers & sisters

What killed these X2 caps?

How to prevent "they're falling in love" trope

If a Gelatinous Cube takes up the entire space of a Pit Trap, what happens when a creature falls into the trap but succeeds on the saving throw?

1960's book about a plague that kills all white people

Should I tell management that I intend to leave due to bad software development practices?



Print man pages with fixed width


Differences between man pagesMan page with preserved text decorations, proportional text and fixed-width codeSearching in man pagesMan-pages don't include all relevant informationMan pages are shuffledSplit lines inside files with fixed width columnsReinstall man pages & fix manawk - , fixed width columnsPaginate man pagesHow to search a pattern containing hyphens inside man pages?






.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty margin-bottom:0;








8















With the example command



man apropos > outputfile


a text file is generated which contains the formatted man page of apropos (with some little differences with respect to man apropos directly printed on screen, such as bold characters).



But I would like to manually set the maximum line width of the generated output file, so that all the paragraphs will be justified to that width.



man pages are created through groff: for example, I tried to put .ll 50 before a paragraph of the original .gz man source text file, but it is trivial if I need to work on several man pages. Moreover not all the characters are recognized:



apropos.1:45: warning: can't find character with input code 195
apropos.1:45: warning: can't find character with input code 168
apropos.1:47: warning: can't find character with input code 178
apropos.1:131: warning: can't find character with input code 169


So, I wonder if a more straightforward method exists. How to modify the maximum line width, during the creation of an outputfile? Is there some specific command?




Edit:



(All the following considerations are about Ubuntu 18.04: I can no more test them in previous versions, included the 14.04 of the above question.)



As regards a one-line temporary solution, if MANWIDTH has not been already exported with a custom value, there is no difference between



$ MANWIDTH=60 man apropos > outputfile


and



$ COLUMNS=60 man apropos > outputfile


The first one, using MANWIDTH, is however better in principle.




Edit 2 (not strictly related to the question):



To make instead a permanent width setting to be applied to any manpage printing, it is necessary to export the desired value of the variable. With:



$ export MANWIDTH=60
# zero or more additional lines
$ man apropos > outputfile


man apropos will be printed with the same width regardless of any terminal window resizing. Instead,



$ export COLUMNS=60
# zero or more additional lines
$ man apropos > outputfile


will provide the same result as before only if the terminal window is not resized between export and man <page> > outputfile.










share|improve this question
























  • I can't reproduce your input code errors 195 168 could be è in UTF-8. Is the man page in English? What's your man implementation? What's your locale?

    – Stéphane Chazelas
    Aug 11 '15 at 14:04











  • the system is Ubuntu 14.04 (version from man man is 2.6.7.1). The man page is in Italian and it is UTF-8. What do you mean by locale?

    – BowPark
    Aug 11 '15 at 16:40











  • What's the output of locale? and locale charmap?

    – Stéphane Chazelas
    Aug 11 '15 at 16:57











  • locale output: LANG=it_IT.UTF-8 LANGUAGE= LC_CTYPE="it_IT.UTF-8" LC_NUMERIC="it_IT.UTF-8" locale charmap output: UTF-8

    – BowPark
    Aug 11 '15 at 17:05







  • 1





    Yes the terminal not functional is from less because TERM is not set. I meant env -i LANG=it_IT.UTF-8 man apropos > output (or | head).

    – Stéphane Chazelas
    Aug 12 '15 at 8:33

















8















With the example command



man apropos > outputfile


a text file is generated which contains the formatted man page of apropos (with some little differences with respect to man apropos directly printed on screen, such as bold characters).



But I would like to manually set the maximum line width of the generated output file, so that all the paragraphs will be justified to that width.



man pages are created through groff: for example, I tried to put .ll 50 before a paragraph of the original .gz man source text file, but it is trivial if I need to work on several man pages. Moreover not all the characters are recognized:



apropos.1:45: warning: can't find character with input code 195
apropos.1:45: warning: can't find character with input code 168
apropos.1:47: warning: can't find character with input code 178
apropos.1:131: warning: can't find character with input code 169


So, I wonder if a more straightforward method exists. How to modify the maximum line width, during the creation of an outputfile? Is there some specific command?




Edit:



(All the following considerations are about Ubuntu 18.04: I can no more test them in previous versions, included the 14.04 of the above question.)



As regards a one-line temporary solution, if MANWIDTH has not been already exported with a custom value, there is no difference between



$ MANWIDTH=60 man apropos > outputfile


and



$ COLUMNS=60 man apropos > outputfile


The first one, using MANWIDTH, is however better in principle.




Edit 2 (not strictly related to the question):



To make instead a permanent width setting to be applied to any manpage printing, it is necessary to export the desired value of the variable. With:



$ export MANWIDTH=60
# zero or more additional lines
$ man apropos > outputfile


man apropos will be printed with the same width regardless of any terminal window resizing. Instead,



$ export COLUMNS=60
# zero or more additional lines
$ man apropos > outputfile


will provide the same result as before only if the terminal window is not resized between export and man <page> > outputfile.










share|improve this question
























  • I can't reproduce your input code errors 195 168 could be è in UTF-8. Is the man page in English? What's your man implementation? What's your locale?

    – Stéphane Chazelas
    Aug 11 '15 at 14:04











  • the system is Ubuntu 14.04 (version from man man is 2.6.7.1). The man page is in Italian and it is UTF-8. What do you mean by locale?

    – BowPark
    Aug 11 '15 at 16:40











  • What's the output of locale? and locale charmap?

    – Stéphane Chazelas
    Aug 11 '15 at 16:57











  • locale output: LANG=it_IT.UTF-8 LANGUAGE= LC_CTYPE="it_IT.UTF-8" LC_NUMERIC="it_IT.UTF-8" locale charmap output: UTF-8

    – BowPark
    Aug 11 '15 at 17:05







  • 1





    Yes the terminal not functional is from less because TERM is not set. I meant env -i LANG=it_IT.UTF-8 man apropos > output (or | head).

    – Stéphane Chazelas
    Aug 12 '15 at 8:33













8












8








8


2






With the example command



man apropos > outputfile


a text file is generated which contains the formatted man page of apropos (with some little differences with respect to man apropos directly printed on screen, such as bold characters).



But I would like to manually set the maximum line width of the generated output file, so that all the paragraphs will be justified to that width.



man pages are created through groff: for example, I tried to put .ll 50 before a paragraph of the original .gz man source text file, but it is trivial if I need to work on several man pages. Moreover not all the characters are recognized:



apropos.1:45: warning: can't find character with input code 195
apropos.1:45: warning: can't find character with input code 168
apropos.1:47: warning: can't find character with input code 178
apropos.1:131: warning: can't find character with input code 169


So, I wonder if a more straightforward method exists. How to modify the maximum line width, during the creation of an outputfile? Is there some specific command?




Edit:



(All the following considerations are about Ubuntu 18.04: I can no more test them in previous versions, included the 14.04 of the above question.)



As regards a one-line temporary solution, if MANWIDTH has not been already exported with a custom value, there is no difference between



$ MANWIDTH=60 man apropos > outputfile


and



$ COLUMNS=60 man apropos > outputfile


The first one, using MANWIDTH, is however better in principle.




Edit 2 (not strictly related to the question):



To make instead a permanent width setting to be applied to any manpage printing, it is necessary to export the desired value of the variable. With:



$ export MANWIDTH=60
# zero or more additional lines
$ man apropos > outputfile


man apropos will be printed with the same width regardless of any terminal window resizing. Instead,



$ export COLUMNS=60
# zero or more additional lines
$ man apropos > outputfile


will provide the same result as before only if the terminal window is not resized between export and man <page> > outputfile.










share|improve this question
















With the example command



man apropos > outputfile


a text file is generated which contains the formatted man page of apropos (with some little differences with respect to man apropos directly printed on screen, such as bold characters).



But I would like to manually set the maximum line width of the generated output file, so that all the paragraphs will be justified to that width.



man pages are created through groff: for example, I tried to put .ll 50 before a paragraph of the original .gz man source text file, but it is trivial if I need to work on several man pages. Moreover not all the characters are recognized:



apropos.1:45: warning: can't find character with input code 195
apropos.1:45: warning: can't find character with input code 168
apropos.1:47: warning: can't find character with input code 178
apropos.1:131: warning: can't find character with input code 169


So, I wonder if a more straightforward method exists. How to modify the maximum line width, during the creation of an outputfile? Is there some specific command?




Edit:



(All the following considerations are about Ubuntu 18.04: I can no more test them in previous versions, included the 14.04 of the above question.)



As regards a one-line temporary solution, if MANWIDTH has not been already exported with a custom value, there is no difference between



$ MANWIDTH=60 man apropos > outputfile


and



$ COLUMNS=60 man apropos > outputfile


The first one, using MANWIDTH, is however better in principle.




Edit 2 (not strictly related to the question):



To make instead a permanent width setting to be applied to any manpage printing, it is necessary to export the desired value of the variable. With:



$ export MANWIDTH=60
# zero or more additional lines
$ man apropos > outputfile


man apropos will be printed with the same width regardless of any terminal window resizing. Instead,



$ export COLUMNS=60
# zero or more additional lines
$ man apropos > outputfile


will provide the same result as before only if the terminal window is not resized between export and man <page> > outputfile.







shell command-line text-processing man text-formatting






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Oct 18 '18 at 13:58







BowPark

















asked Aug 11 '15 at 13:42









BowParkBowPark

1,62082749




1,62082749












  • I can't reproduce your input code errors 195 168 could be è in UTF-8. Is the man page in English? What's your man implementation? What's your locale?

    – Stéphane Chazelas
    Aug 11 '15 at 14:04











  • the system is Ubuntu 14.04 (version from man man is 2.6.7.1). The man page is in Italian and it is UTF-8. What do you mean by locale?

    – BowPark
    Aug 11 '15 at 16:40











  • What's the output of locale? and locale charmap?

    – Stéphane Chazelas
    Aug 11 '15 at 16:57











  • locale output: LANG=it_IT.UTF-8 LANGUAGE= LC_CTYPE="it_IT.UTF-8" LC_NUMERIC="it_IT.UTF-8" locale charmap output: UTF-8

    – BowPark
    Aug 11 '15 at 17:05







  • 1





    Yes the terminal not functional is from less because TERM is not set. I meant env -i LANG=it_IT.UTF-8 man apropos > output (or | head).

    – Stéphane Chazelas
    Aug 12 '15 at 8:33

















  • I can't reproduce your input code errors 195 168 could be è in UTF-8. Is the man page in English? What's your man implementation? What's your locale?

    – Stéphane Chazelas
    Aug 11 '15 at 14:04











  • the system is Ubuntu 14.04 (version from man man is 2.6.7.1). The man page is in Italian and it is UTF-8. What do you mean by locale?

    – BowPark
    Aug 11 '15 at 16:40











  • What's the output of locale? and locale charmap?

    – Stéphane Chazelas
    Aug 11 '15 at 16:57











  • locale output: LANG=it_IT.UTF-8 LANGUAGE= LC_CTYPE="it_IT.UTF-8" LC_NUMERIC="it_IT.UTF-8" locale charmap output: UTF-8

    – BowPark
    Aug 11 '15 at 17:05







  • 1





    Yes the terminal not functional is from less because TERM is not set. I meant env -i LANG=it_IT.UTF-8 man apropos > output (or | head).

    – Stéphane Chazelas
    Aug 12 '15 at 8:33
















I can't reproduce your input code errors 195 168 could be è in UTF-8. Is the man page in English? What's your man implementation? What's your locale?

– Stéphane Chazelas
Aug 11 '15 at 14:04





I can't reproduce your input code errors 195 168 could be è in UTF-8. Is the man page in English? What's your man implementation? What's your locale?

– Stéphane Chazelas
Aug 11 '15 at 14:04













the system is Ubuntu 14.04 (version from man man is 2.6.7.1). The man page is in Italian and it is UTF-8. What do you mean by locale?

– BowPark
Aug 11 '15 at 16:40





the system is Ubuntu 14.04 (version from man man is 2.6.7.1). The man page is in Italian and it is UTF-8. What do you mean by locale?

– BowPark
Aug 11 '15 at 16:40













What's the output of locale? and locale charmap?

– Stéphane Chazelas
Aug 11 '15 at 16:57





What's the output of locale? and locale charmap?

– Stéphane Chazelas
Aug 11 '15 at 16:57













locale output: LANG=it_IT.UTF-8 LANGUAGE= LC_CTYPE="it_IT.UTF-8" LC_NUMERIC="it_IT.UTF-8" locale charmap output: UTF-8

– BowPark
Aug 11 '15 at 17:05






locale output: LANG=it_IT.UTF-8 LANGUAGE= LC_CTYPE="it_IT.UTF-8" LC_NUMERIC="it_IT.UTF-8" locale charmap output: UTF-8

– BowPark
Aug 11 '15 at 17:05





1




1





Yes the terminal not functional is from less because TERM is not set. I meant env -i LANG=it_IT.UTF-8 man apropos > output (or | head).

– Stéphane Chazelas
Aug 12 '15 at 8:33





Yes the terminal not functional is from less because TERM is not set. I meant env -i LANG=it_IT.UTF-8 man apropos > output (or | head).

– Stéphane Chazelas
Aug 12 '15 at 8:33










4 Answers
4






active

oldest

votes


















14














Use the MANWIDTH environment variable:



MANWIDTH=60 man apropos > apropos.txt


The manpage for man 2.7.4 says:




If $MANWIDTH is set, its value is used as the line length for which manual pages should be formatted. If it is not set, manual pages will be formatted with a line length appropriate to the current terminal (using the value of $COLUMNS, an ioctl(2) if available, or falling back to 80 characters if neither is available).




That is, it overrides both COLUMNS and the ioctl value. I prefer to not rely on modifying COLUMNS (although it does work here) since its value is updated dynamically every time the window size changes.



Using MANWIDTH instead of COLUMNS also allows you to make the change permanent by adding a line such as export MANWIDTH=60 to your shell startup file.






share|improve this answer

























  • Excellent job. I didn't want to change COLUMNS either, and MANWIDTH works a treat in RHEL5. Cheers.

    – Felipe Alvarez
    Apr 20 '16 at 0:35






  • 1





    A note to readers: you may need to use export MANWIDTH=60 if setting this in your ~/.bashrc. See stackoverflow.com/a/30173376/82216 . Also, consider wrapping man in a function to set MANWIDTH depending upon your terminal width, as suggested here on the Arch wiki.

    – sampablokuper
    Dec 17 '17 at 17:46












  • @Marcel M Thank you for your very precise answer. Can you please read the update in the question and edit your answer to include the fundamental suggestion about export MANWIDTH=60?

    – BowPark
    Oct 18 '18 at 8:07











  • @BowPark I wrote the answer without export because you asked about a temporary solution: "How to modify the maximum line width, during the creation of an outputfile?" (emphasis mine). You may even want to revert your edit as it doesn’t add to the question. (A comment is more appropriate.)

    – Marcel M
    Oct 18 '18 at 12:42











  • @MarcelM Actually you are right. I edited the question accordingly. I wrote a second edit with the export statements because in a comment it would be almost unreadable (not being possible to create newlines).

    – BowPark
    Oct 18 '18 at 14:03


















10














Try setting the COLUMNS environment variable. Works for me with man from mandb 2.7.0.2 on Debian with groff 1.22.3.



$ COLUMNS=60 man apropos | head
APROPOS(1) Manual pager utils APROPOS(1)



NAME
apropos - search the manual page names and descrip‐
tions

SYNOPSIS
apropos [-dalv?V] [-e|-w|-r] [-s list] [-m sys‐




$ COLUMNS=70 man apropos | head
APROPOS(1) Manual pager utils APROPOS(1)



NAME
apropos - search the manual page names and descriptions

SYNOPSIS
apropos [-dalv?V] [-e|-w|-r] [-s list] [-m system[,...]] [-M
path] [-L locale] [-C file] keyword ...


With the version on Ubuntu 14.04, I need to write it:



COLUMNS=60 < /dev/null man apropos | head


There, man seems to disregard the COLUMNS environment variable if stdin is a terminal (it then queries the terminal device for the terminal width).



You can also try:



s=$(stty -g); stty cols 60; man apropos | head; stty "$s"


Which with zsh you can shorten to:



STTY='cols 60' man apropos | head


You could do it by invoking groff by hand as:



gzip -dcf "$(man -w apropos)" |
groff -ekpstR -mtty-char -mandoc -Tutf8 -rLL=60n |
col -bpx


Your can't find character with input code errors were because you used -Tascii instead of -Tutf8 and didn't use -k to pre-process the files with preconv.






share|improve this answer

























  • I tried the same command: COLUMNS=60 man apropos | head, but unfortunately the output width is all the screen width. Can I set the variable COLUMNS elsewhere or in other way?

    – BowPark
    Aug 11 '15 at 16:46






  • 2





    Try COLUMNS=60 < /dev/null man apropos | head. Looks like on Ubuntu 14.04, it doesn't trust COLUMNS if stdin is a terminal (and gets the width from the terminal device).

    – Stéphane Chazelas
    Aug 11 '15 at 16:53











  • Maybe it is like you supposed. And now it works, thank you!

    – BowPark
    Aug 11 '15 at 17:03



















4














You can use the fmt command, which as far as I know is present in any Linux distribution.



man apropos | fmt -w 70 


will wrap up lines at 70 characters.






share|improve this answer


















  • 1





    yes I have it, thank you, it works and it is pretty useful, but I need a justified text and it simply wrap up lines instead.

    – BowPark
    Aug 11 '15 at 16:42











  • Sorry, I must have missed up that part.

    – dr01
    Aug 12 '15 at 8:10


















2














You can use fold



man cp | fold -w 20


will fold after each 20 characters(!). Note that this will cut words in two as the only option is "fold every 20 characters"



taking care of this, you might use sed as follows (with dynamic line length)



man cp | sed 's/.20 /&n/g'


will add a newline after 20 random characters followed by a space (i.e. new word). So lines might be longer than 20 characters (match is 20 characters then a space so a 26-character word would result in a 26-character line)



For omitting the last space in the sed command:



sed 's/(.20) /1n/g'





share|improve this answer




















  • 1





    Thank you, I tried your examples and they work, but - as written in a comment to dr01 - I need a justified text.

    – BowPark
    Aug 11 '15 at 16:48











Your Answer








StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "106"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);

else
createEditor();

);

function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);



);













draft saved

draft discarded


















StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f222528%2fprint-man-pages-with-fixed-width%23new-answer', 'question_page');

);

Post as a guest















Required, but never shown

























4 Answers
4






active

oldest

votes








4 Answers
4






active

oldest

votes









active

oldest

votes






active

oldest

votes









14














Use the MANWIDTH environment variable:



MANWIDTH=60 man apropos > apropos.txt


The manpage for man 2.7.4 says:




If $MANWIDTH is set, its value is used as the line length for which manual pages should be formatted. If it is not set, manual pages will be formatted with a line length appropriate to the current terminal (using the value of $COLUMNS, an ioctl(2) if available, or falling back to 80 characters if neither is available).




That is, it overrides both COLUMNS and the ioctl value. I prefer to not rely on modifying COLUMNS (although it does work here) since its value is updated dynamically every time the window size changes.



Using MANWIDTH instead of COLUMNS also allows you to make the change permanent by adding a line such as export MANWIDTH=60 to your shell startup file.






share|improve this answer

























  • Excellent job. I didn't want to change COLUMNS either, and MANWIDTH works a treat in RHEL5. Cheers.

    – Felipe Alvarez
    Apr 20 '16 at 0:35






  • 1





    A note to readers: you may need to use export MANWIDTH=60 if setting this in your ~/.bashrc. See stackoverflow.com/a/30173376/82216 . Also, consider wrapping man in a function to set MANWIDTH depending upon your terminal width, as suggested here on the Arch wiki.

    – sampablokuper
    Dec 17 '17 at 17:46












  • @Marcel M Thank you for your very precise answer. Can you please read the update in the question and edit your answer to include the fundamental suggestion about export MANWIDTH=60?

    – BowPark
    Oct 18 '18 at 8:07











  • @BowPark I wrote the answer without export because you asked about a temporary solution: "How to modify the maximum line width, during the creation of an outputfile?" (emphasis mine). You may even want to revert your edit as it doesn’t add to the question. (A comment is more appropriate.)

    – Marcel M
    Oct 18 '18 at 12:42











  • @MarcelM Actually you are right. I edited the question accordingly. I wrote a second edit with the export statements because in a comment it would be almost unreadable (not being possible to create newlines).

    – BowPark
    Oct 18 '18 at 14:03















14














Use the MANWIDTH environment variable:



MANWIDTH=60 man apropos > apropos.txt


The manpage for man 2.7.4 says:




If $MANWIDTH is set, its value is used as the line length for which manual pages should be formatted. If it is not set, manual pages will be formatted with a line length appropriate to the current terminal (using the value of $COLUMNS, an ioctl(2) if available, or falling back to 80 characters if neither is available).




That is, it overrides both COLUMNS and the ioctl value. I prefer to not rely on modifying COLUMNS (although it does work here) since its value is updated dynamically every time the window size changes.



Using MANWIDTH instead of COLUMNS also allows you to make the change permanent by adding a line such as export MANWIDTH=60 to your shell startup file.






share|improve this answer

























  • Excellent job. I didn't want to change COLUMNS either, and MANWIDTH works a treat in RHEL5. Cheers.

    – Felipe Alvarez
    Apr 20 '16 at 0:35






  • 1





    A note to readers: you may need to use export MANWIDTH=60 if setting this in your ~/.bashrc. See stackoverflow.com/a/30173376/82216 . Also, consider wrapping man in a function to set MANWIDTH depending upon your terminal width, as suggested here on the Arch wiki.

    – sampablokuper
    Dec 17 '17 at 17:46












  • @Marcel M Thank you for your very precise answer. Can you please read the update in the question and edit your answer to include the fundamental suggestion about export MANWIDTH=60?

    – BowPark
    Oct 18 '18 at 8:07











  • @BowPark I wrote the answer without export because you asked about a temporary solution: "How to modify the maximum line width, during the creation of an outputfile?" (emphasis mine). You may even want to revert your edit as it doesn’t add to the question. (A comment is more appropriate.)

    – Marcel M
    Oct 18 '18 at 12:42











  • @MarcelM Actually you are right. I edited the question accordingly. I wrote a second edit with the export statements because in a comment it would be almost unreadable (not being possible to create newlines).

    – BowPark
    Oct 18 '18 at 14:03













14












14








14







Use the MANWIDTH environment variable:



MANWIDTH=60 man apropos > apropos.txt


The manpage for man 2.7.4 says:




If $MANWIDTH is set, its value is used as the line length for which manual pages should be formatted. If it is not set, manual pages will be formatted with a line length appropriate to the current terminal (using the value of $COLUMNS, an ioctl(2) if available, or falling back to 80 characters if neither is available).




That is, it overrides both COLUMNS and the ioctl value. I prefer to not rely on modifying COLUMNS (although it does work here) since its value is updated dynamically every time the window size changes.



Using MANWIDTH instead of COLUMNS also allows you to make the change permanent by adding a line such as export MANWIDTH=60 to your shell startup file.






share|improve this answer















Use the MANWIDTH environment variable:



MANWIDTH=60 man apropos > apropos.txt


The manpage for man 2.7.4 says:




If $MANWIDTH is set, its value is used as the line length for which manual pages should be formatted. If it is not set, manual pages will be formatted with a line length appropriate to the current terminal (using the value of $COLUMNS, an ioctl(2) if available, or falling back to 80 characters if neither is available).




That is, it overrides both COLUMNS and the ioctl value. I prefer to not rely on modifying COLUMNS (although it does work here) since its value is updated dynamically every time the window size changes.



Using MANWIDTH instead of COLUMNS also allows you to make the change permanent by adding a line such as export MANWIDTH=60 to your shell startup file.







share|improve this answer














share|improve this answer



share|improve this answer








edited 2 days ago









Antonin Décimo

32




32










answered Feb 16 '16 at 10:52









Marcel MMarcel M

25624




25624












  • Excellent job. I didn't want to change COLUMNS either, and MANWIDTH works a treat in RHEL5. Cheers.

    – Felipe Alvarez
    Apr 20 '16 at 0:35






  • 1





    A note to readers: you may need to use export MANWIDTH=60 if setting this in your ~/.bashrc. See stackoverflow.com/a/30173376/82216 . Also, consider wrapping man in a function to set MANWIDTH depending upon your terminal width, as suggested here on the Arch wiki.

    – sampablokuper
    Dec 17 '17 at 17:46












  • @Marcel M Thank you for your very precise answer. Can you please read the update in the question and edit your answer to include the fundamental suggestion about export MANWIDTH=60?

    – BowPark
    Oct 18 '18 at 8:07











  • @BowPark I wrote the answer without export because you asked about a temporary solution: "How to modify the maximum line width, during the creation of an outputfile?" (emphasis mine). You may even want to revert your edit as it doesn’t add to the question. (A comment is more appropriate.)

    – Marcel M
    Oct 18 '18 at 12:42











  • @MarcelM Actually you are right. I edited the question accordingly. I wrote a second edit with the export statements because in a comment it would be almost unreadable (not being possible to create newlines).

    – BowPark
    Oct 18 '18 at 14:03

















  • Excellent job. I didn't want to change COLUMNS either, and MANWIDTH works a treat in RHEL5. Cheers.

    – Felipe Alvarez
    Apr 20 '16 at 0:35






  • 1





    A note to readers: you may need to use export MANWIDTH=60 if setting this in your ~/.bashrc. See stackoverflow.com/a/30173376/82216 . Also, consider wrapping man in a function to set MANWIDTH depending upon your terminal width, as suggested here on the Arch wiki.

    – sampablokuper
    Dec 17 '17 at 17:46












  • @Marcel M Thank you for your very precise answer. Can you please read the update in the question and edit your answer to include the fundamental suggestion about export MANWIDTH=60?

    – BowPark
    Oct 18 '18 at 8:07











  • @BowPark I wrote the answer without export because you asked about a temporary solution: "How to modify the maximum line width, during the creation of an outputfile?" (emphasis mine). You may even want to revert your edit as it doesn’t add to the question. (A comment is more appropriate.)

    – Marcel M
    Oct 18 '18 at 12:42











  • @MarcelM Actually you are right. I edited the question accordingly. I wrote a second edit with the export statements because in a comment it would be almost unreadable (not being possible to create newlines).

    – BowPark
    Oct 18 '18 at 14:03
















Excellent job. I didn't want to change COLUMNS either, and MANWIDTH works a treat in RHEL5. Cheers.

– Felipe Alvarez
Apr 20 '16 at 0:35





Excellent job. I didn't want to change COLUMNS either, and MANWIDTH works a treat in RHEL5. Cheers.

– Felipe Alvarez
Apr 20 '16 at 0:35




1




1





A note to readers: you may need to use export MANWIDTH=60 if setting this in your ~/.bashrc. See stackoverflow.com/a/30173376/82216 . Also, consider wrapping man in a function to set MANWIDTH depending upon your terminal width, as suggested here on the Arch wiki.

– sampablokuper
Dec 17 '17 at 17:46






A note to readers: you may need to use export MANWIDTH=60 if setting this in your ~/.bashrc. See stackoverflow.com/a/30173376/82216 . Also, consider wrapping man in a function to set MANWIDTH depending upon your terminal width, as suggested here on the Arch wiki.

– sampablokuper
Dec 17 '17 at 17:46














@Marcel M Thank you for your very precise answer. Can you please read the update in the question and edit your answer to include the fundamental suggestion about export MANWIDTH=60?

– BowPark
Oct 18 '18 at 8:07





@Marcel M Thank you for your very precise answer. Can you please read the update in the question and edit your answer to include the fundamental suggestion about export MANWIDTH=60?

– BowPark
Oct 18 '18 at 8:07













@BowPark I wrote the answer without export because you asked about a temporary solution: "How to modify the maximum line width, during the creation of an outputfile?" (emphasis mine). You may even want to revert your edit as it doesn’t add to the question. (A comment is more appropriate.)

– Marcel M
Oct 18 '18 at 12:42





@BowPark I wrote the answer without export because you asked about a temporary solution: "How to modify the maximum line width, during the creation of an outputfile?" (emphasis mine). You may even want to revert your edit as it doesn’t add to the question. (A comment is more appropriate.)

– Marcel M
Oct 18 '18 at 12:42













@MarcelM Actually you are right. I edited the question accordingly. I wrote a second edit with the export statements because in a comment it would be almost unreadable (not being possible to create newlines).

– BowPark
Oct 18 '18 at 14:03





@MarcelM Actually you are right. I edited the question accordingly. I wrote a second edit with the export statements because in a comment it would be almost unreadable (not being possible to create newlines).

– BowPark
Oct 18 '18 at 14:03













10














Try setting the COLUMNS environment variable. Works for me with man from mandb 2.7.0.2 on Debian with groff 1.22.3.



$ COLUMNS=60 man apropos | head
APROPOS(1) Manual pager utils APROPOS(1)



NAME
apropos - search the manual page names and descrip‐
tions

SYNOPSIS
apropos [-dalv?V] [-e|-w|-r] [-s list] [-m sys‐




$ COLUMNS=70 man apropos | head
APROPOS(1) Manual pager utils APROPOS(1)



NAME
apropos - search the manual page names and descriptions

SYNOPSIS
apropos [-dalv?V] [-e|-w|-r] [-s list] [-m system[,...]] [-M
path] [-L locale] [-C file] keyword ...


With the version on Ubuntu 14.04, I need to write it:



COLUMNS=60 < /dev/null man apropos | head


There, man seems to disregard the COLUMNS environment variable if stdin is a terminal (it then queries the terminal device for the terminal width).



You can also try:



s=$(stty -g); stty cols 60; man apropos | head; stty "$s"


Which with zsh you can shorten to:



STTY='cols 60' man apropos | head


You could do it by invoking groff by hand as:



gzip -dcf "$(man -w apropos)" |
groff -ekpstR -mtty-char -mandoc -Tutf8 -rLL=60n |
col -bpx


Your can't find character with input code errors were because you used -Tascii instead of -Tutf8 and didn't use -k to pre-process the files with preconv.






share|improve this answer

























  • I tried the same command: COLUMNS=60 man apropos | head, but unfortunately the output width is all the screen width. Can I set the variable COLUMNS elsewhere or in other way?

    – BowPark
    Aug 11 '15 at 16:46






  • 2





    Try COLUMNS=60 < /dev/null man apropos | head. Looks like on Ubuntu 14.04, it doesn't trust COLUMNS if stdin is a terminal (and gets the width from the terminal device).

    – Stéphane Chazelas
    Aug 11 '15 at 16:53











  • Maybe it is like you supposed. And now it works, thank you!

    – BowPark
    Aug 11 '15 at 17:03
















10














Try setting the COLUMNS environment variable. Works for me with man from mandb 2.7.0.2 on Debian with groff 1.22.3.



$ COLUMNS=60 man apropos | head
APROPOS(1) Manual pager utils APROPOS(1)



NAME
apropos - search the manual page names and descrip‐
tions

SYNOPSIS
apropos [-dalv?V] [-e|-w|-r] [-s list] [-m sys‐




$ COLUMNS=70 man apropos | head
APROPOS(1) Manual pager utils APROPOS(1)



NAME
apropos - search the manual page names and descriptions

SYNOPSIS
apropos [-dalv?V] [-e|-w|-r] [-s list] [-m system[,...]] [-M
path] [-L locale] [-C file] keyword ...


With the version on Ubuntu 14.04, I need to write it:



COLUMNS=60 < /dev/null man apropos | head


There, man seems to disregard the COLUMNS environment variable if stdin is a terminal (it then queries the terminal device for the terminal width).



You can also try:



s=$(stty -g); stty cols 60; man apropos | head; stty "$s"


Which with zsh you can shorten to:



STTY='cols 60' man apropos | head


You could do it by invoking groff by hand as:



gzip -dcf "$(man -w apropos)" |
groff -ekpstR -mtty-char -mandoc -Tutf8 -rLL=60n |
col -bpx


Your can't find character with input code errors were because you used -Tascii instead of -Tutf8 and didn't use -k to pre-process the files with preconv.






share|improve this answer

























  • I tried the same command: COLUMNS=60 man apropos | head, but unfortunately the output width is all the screen width. Can I set the variable COLUMNS elsewhere or in other way?

    – BowPark
    Aug 11 '15 at 16:46






  • 2





    Try COLUMNS=60 < /dev/null man apropos | head. Looks like on Ubuntu 14.04, it doesn't trust COLUMNS if stdin is a terminal (and gets the width from the terminal device).

    – Stéphane Chazelas
    Aug 11 '15 at 16:53











  • Maybe it is like you supposed. And now it works, thank you!

    – BowPark
    Aug 11 '15 at 17:03














10












10








10







Try setting the COLUMNS environment variable. Works for me with man from mandb 2.7.0.2 on Debian with groff 1.22.3.



$ COLUMNS=60 man apropos | head
APROPOS(1) Manual pager utils APROPOS(1)



NAME
apropos - search the manual page names and descrip‐
tions

SYNOPSIS
apropos [-dalv?V] [-e|-w|-r] [-s list] [-m sys‐




$ COLUMNS=70 man apropos | head
APROPOS(1) Manual pager utils APROPOS(1)



NAME
apropos - search the manual page names and descriptions

SYNOPSIS
apropos [-dalv?V] [-e|-w|-r] [-s list] [-m system[,...]] [-M
path] [-L locale] [-C file] keyword ...


With the version on Ubuntu 14.04, I need to write it:



COLUMNS=60 < /dev/null man apropos | head


There, man seems to disregard the COLUMNS environment variable if stdin is a terminal (it then queries the terminal device for the terminal width).



You can also try:



s=$(stty -g); stty cols 60; man apropos | head; stty "$s"


Which with zsh you can shorten to:



STTY='cols 60' man apropos | head


You could do it by invoking groff by hand as:



gzip -dcf "$(man -w apropos)" |
groff -ekpstR -mtty-char -mandoc -Tutf8 -rLL=60n |
col -bpx


Your can't find character with input code errors were because you used -Tascii instead of -Tutf8 and didn't use -k to pre-process the files with preconv.






share|improve this answer















Try setting the COLUMNS environment variable. Works for me with man from mandb 2.7.0.2 on Debian with groff 1.22.3.



$ COLUMNS=60 man apropos | head
APROPOS(1) Manual pager utils APROPOS(1)



NAME
apropos - search the manual page names and descrip‐
tions

SYNOPSIS
apropos [-dalv?V] [-e|-w|-r] [-s list] [-m sys‐




$ COLUMNS=70 man apropos | head
APROPOS(1) Manual pager utils APROPOS(1)



NAME
apropos - search the manual page names and descriptions

SYNOPSIS
apropos [-dalv?V] [-e|-w|-r] [-s list] [-m system[,...]] [-M
path] [-L locale] [-C file] keyword ...


With the version on Ubuntu 14.04, I need to write it:



COLUMNS=60 < /dev/null man apropos | head


There, man seems to disregard the COLUMNS environment variable if stdin is a terminal (it then queries the terminal device for the terminal width).



You can also try:



s=$(stty -g); stty cols 60; man apropos | head; stty "$s"


Which with zsh you can shorten to:



STTY='cols 60' man apropos | head


You could do it by invoking groff by hand as:



gzip -dcf "$(man -w apropos)" |
groff -ekpstR -mtty-char -mandoc -Tutf8 -rLL=60n |
col -bpx


Your can't find character with input code errors were because you used -Tascii instead of -Tutf8 and didn't use -k to pre-process the files with preconv.







share|improve this answer














share|improve this answer



share|improve this answer








edited Aug 12 '15 at 9:17

























answered Aug 11 '15 at 13:50









Stéphane ChazelasStéphane Chazelas

313k57592948




313k57592948












  • I tried the same command: COLUMNS=60 man apropos | head, but unfortunately the output width is all the screen width. Can I set the variable COLUMNS elsewhere or in other way?

    – BowPark
    Aug 11 '15 at 16:46






  • 2





    Try COLUMNS=60 < /dev/null man apropos | head. Looks like on Ubuntu 14.04, it doesn't trust COLUMNS if stdin is a terminal (and gets the width from the terminal device).

    – Stéphane Chazelas
    Aug 11 '15 at 16:53











  • Maybe it is like you supposed. And now it works, thank you!

    – BowPark
    Aug 11 '15 at 17:03


















  • I tried the same command: COLUMNS=60 man apropos | head, but unfortunately the output width is all the screen width. Can I set the variable COLUMNS elsewhere or in other way?

    – BowPark
    Aug 11 '15 at 16:46






  • 2





    Try COLUMNS=60 < /dev/null man apropos | head. Looks like on Ubuntu 14.04, it doesn't trust COLUMNS if stdin is a terminal (and gets the width from the terminal device).

    – Stéphane Chazelas
    Aug 11 '15 at 16:53











  • Maybe it is like you supposed. And now it works, thank you!

    – BowPark
    Aug 11 '15 at 17:03

















I tried the same command: COLUMNS=60 man apropos | head, but unfortunately the output width is all the screen width. Can I set the variable COLUMNS elsewhere or in other way?

– BowPark
Aug 11 '15 at 16:46





I tried the same command: COLUMNS=60 man apropos | head, but unfortunately the output width is all the screen width. Can I set the variable COLUMNS elsewhere or in other way?

– BowPark
Aug 11 '15 at 16:46




2




2





Try COLUMNS=60 < /dev/null man apropos | head. Looks like on Ubuntu 14.04, it doesn't trust COLUMNS if stdin is a terminal (and gets the width from the terminal device).

– Stéphane Chazelas
Aug 11 '15 at 16:53





Try COLUMNS=60 < /dev/null man apropos | head. Looks like on Ubuntu 14.04, it doesn't trust COLUMNS if stdin is a terminal (and gets the width from the terminal device).

– Stéphane Chazelas
Aug 11 '15 at 16:53













Maybe it is like you supposed. And now it works, thank you!

– BowPark
Aug 11 '15 at 17:03






Maybe it is like you supposed. And now it works, thank you!

– BowPark
Aug 11 '15 at 17:03












4














You can use the fmt command, which as far as I know is present in any Linux distribution.



man apropos | fmt -w 70 


will wrap up lines at 70 characters.






share|improve this answer


















  • 1





    yes I have it, thank you, it works and it is pretty useful, but I need a justified text and it simply wrap up lines instead.

    – BowPark
    Aug 11 '15 at 16:42











  • Sorry, I must have missed up that part.

    – dr01
    Aug 12 '15 at 8:10















4














You can use the fmt command, which as far as I know is present in any Linux distribution.



man apropos | fmt -w 70 


will wrap up lines at 70 characters.






share|improve this answer


















  • 1





    yes I have it, thank you, it works and it is pretty useful, but I need a justified text and it simply wrap up lines instead.

    – BowPark
    Aug 11 '15 at 16:42











  • Sorry, I must have missed up that part.

    – dr01
    Aug 12 '15 at 8:10













4












4








4







You can use the fmt command, which as far as I know is present in any Linux distribution.



man apropos | fmt -w 70 


will wrap up lines at 70 characters.






share|improve this answer













You can use the fmt command, which as far as I know is present in any Linux distribution.



man apropos | fmt -w 70 


will wrap up lines at 70 characters.







share|improve this answer












share|improve this answer



share|improve this answer










answered Aug 11 '15 at 14:10









dr01dr01

16.3k115275




16.3k115275







  • 1





    yes I have it, thank you, it works and it is pretty useful, but I need a justified text and it simply wrap up lines instead.

    – BowPark
    Aug 11 '15 at 16:42











  • Sorry, I must have missed up that part.

    – dr01
    Aug 12 '15 at 8:10












  • 1





    yes I have it, thank you, it works and it is pretty useful, but I need a justified text and it simply wrap up lines instead.

    – BowPark
    Aug 11 '15 at 16:42











  • Sorry, I must have missed up that part.

    – dr01
    Aug 12 '15 at 8:10







1




1





yes I have it, thank you, it works and it is pretty useful, but I need a justified text and it simply wrap up lines instead.

– BowPark
Aug 11 '15 at 16:42





yes I have it, thank you, it works and it is pretty useful, but I need a justified text and it simply wrap up lines instead.

– BowPark
Aug 11 '15 at 16:42













Sorry, I must have missed up that part.

– dr01
Aug 12 '15 at 8:10





Sorry, I must have missed up that part.

– dr01
Aug 12 '15 at 8:10











2














You can use fold



man cp | fold -w 20


will fold after each 20 characters(!). Note that this will cut words in two as the only option is "fold every 20 characters"



taking care of this, you might use sed as follows (with dynamic line length)



man cp | sed 's/.20 /&n/g'


will add a newline after 20 random characters followed by a space (i.e. new word). So lines might be longer than 20 characters (match is 20 characters then a space so a 26-character word would result in a 26-character line)



For omitting the last space in the sed command:



sed 's/(.20) /1n/g'





share|improve this answer




















  • 1





    Thank you, I tried your examples and they work, but - as written in a comment to dr01 - I need a justified text.

    – BowPark
    Aug 11 '15 at 16:48















2














You can use fold



man cp | fold -w 20


will fold after each 20 characters(!). Note that this will cut words in two as the only option is "fold every 20 characters"



taking care of this, you might use sed as follows (with dynamic line length)



man cp | sed 's/.20 /&n/g'


will add a newline after 20 random characters followed by a space (i.e. new word). So lines might be longer than 20 characters (match is 20 characters then a space so a 26-character word would result in a 26-character line)



For omitting the last space in the sed command:



sed 's/(.20) /1n/g'





share|improve this answer




















  • 1





    Thank you, I tried your examples and they work, but - as written in a comment to dr01 - I need a justified text.

    – BowPark
    Aug 11 '15 at 16:48













2












2








2







You can use fold



man cp | fold -w 20


will fold after each 20 characters(!). Note that this will cut words in two as the only option is "fold every 20 characters"



taking care of this, you might use sed as follows (with dynamic line length)



man cp | sed 's/.20 /&n/g'


will add a newline after 20 random characters followed by a space (i.e. new word). So lines might be longer than 20 characters (match is 20 characters then a space so a 26-character word would result in a 26-character line)



For omitting the last space in the sed command:



sed 's/(.20) /1n/g'





share|improve this answer















You can use fold



man cp | fold -w 20


will fold after each 20 characters(!). Note that this will cut words in two as the only option is "fold every 20 characters"



taking care of this, you might use sed as follows (with dynamic line length)



man cp | sed 's/.20 /&n/g'


will add a newline after 20 random characters followed by a space (i.e. new word). So lines might be longer than 20 characters (match is 20 characters then a space so a 26-character word would result in a 26-character line)



For omitting the last space in the sed command:



sed 's/(.20) /1n/g'






share|improve this answer














share|improve this answer



share|improve this answer








edited Aug 11 '15 at 14:05

























answered Aug 11 '15 at 13:52









FiximanFiximan

3,298625




3,298625







  • 1





    Thank you, I tried your examples and they work, but - as written in a comment to dr01 - I need a justified text.

    – BowPark
    Aug 11 '15 at 16:48












  • 1





    Thank you, I tried your examples and they work, but - as written in a comment to dr01 - I need a justified text.

    – BowPark
    Aug 11 '15 at 16:48







1




1





Thank you, I tried your examples and they work, but - as written in a comment to dr01 - I need a justified text.

– BowPark
Aug 11 '15 at 16:48





Thank you, I tried your examples and they work, but - as written in a comment to dr01 - I need a justified text.

– BowPark
Aug 11 '15 at 16:48

















draft saved

draft discarded
















































Thanks for contributing an answer to Unix & Linux Stack Exchange!


  • Please be sure to answer the question. Provide details and share your research!

But avoid


  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.

To learn more, see our tips on writing great answers.




draft saved


draft discarded














StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f222528%2fprint-man-pages-with-fixed-width%23new-answer', 'question_page');

);

Post as a guest















Required, but never shown





















































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown

































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown







Popular posts from this blog

Àrd-bhaile Cathair chruinne/Baile mòr cruinne | Artagailean ceangailte | Clàr-taice na seòladaireachd

Cannot Extend partition with GParted The 2019 Stack Overflow Developer Survey Results Are In Announcing the arrival of Valued Associate #679: Cesar Manara Planned maintenance scheduled April 17/18, 2019 at 00:00UTC (8:00pm US/Eastern) 2019 Community Moderator Election ResultsCan't increase partition size with GParted?GParted doesn't recognize the unallocated space after my current partitionWhat is the best way to add unallocated space located before to Ubuntu 12.04 partition with GParted live?I can't figure out how to extend my Arch home partition into free spaceGparted Linux Mint 18.1 issueTrying to extend but swap partition is showing as Unknown in Gparted, shows proper from fdiskRearrange partitions in gparted to extend a partitionUnable to extend partition even though unallocated space is next to it using GPartedAllocate free space to root partitiongparted: how to merge unallocated space with a partition

대한민국 목차 국명 지리 역사 정치 국방 경제 사회 문화 국제 순위 관련 항목 각주 외부 링크 둘러보기 메뉴북위 37° 34′ 08″ 동경 126° 58′ 36″ / 북위 37.568889° 동경 126.976667°  / 37.568889; 126.976667ehThe Korean Repository문단을 편집문단을 편집추가해Clarkson PLC 사Report for Selected Countries and Subjects-Korea“Human Development Index and its components: P.198”“http://www.law.go.kr/%EB%B2%95%EB%A0%B9/%EB%8C%80%ED%95%9C%EB%AF%BC%EA%B5%AD%EA%B5%AD%EA%B8%B0%EB%B2%95”"한국은 국제법상 한반도 유일 합법정부 아니다" - 오마이뉴스 모바일Report for Selected Countries and Subjects: South Korea격동의 역사와 함께한 조선일보 90년 : 조선일보 인수해 혁신시킨 신석우, 임시정부 때는 '대한민국' 국호(國號) 정해《우리가 몰랐던 우리 역사: 나라 이름의 비밀을 찾아가는 역사 여행》“남북 공식호칭 ‘남한’‘북한’으로 쓴다”“Corea 대 Korea, 누가 이긴 거야?”국내기후자료 - 한국[김대중 前 대통령 서거] 과감한 구조개혁 'DJ노믹스'로 최단기간 환란극복 :: 네이버 뉴스“이라크 "韓-쿠르드 유전개발 MOU 승인 안해"(종합)”“해외 우리국민 추방사례 43%가 일본”차기전차 K2'흑표'의 세계 최고 전력 분석, 쿠키뉴스 엄기영, 2007-03-02두산인프라, 헬기잡는 장갑차 'K21'...내년부터 공급, 고뉴스 이대준, 2008-10-30과거 내용 찾기mk 뉴스 - 구매력 기준으로 보면 한국 1인당 소득 3만弗과거 내용 찾기"The N-11: More Than an Acronym"Archived조선일보 최우석, 2008-11-01Global 500 2008: Countries - South Korea“몇년째 '시한폭탄'... 가계부채, 올해는 터질까”가구당 부채 5000만원 처음 넘어서“‘빚’으로 내몰리는 사회.. 위기의 가계대출”“[경제365] 공공부문 부채 급증…800조 육박”“"소득 양극화 다소 완화...불평등은 여전"”“공정사회·공생발전 한참 멀었네”iSuppli,08年2QのDRAMシェア・ランキングを発表(08/8/11)South Korea dominates shipbuilding industry | Stock Market News & Stocks to Watch from StraightStocks한국 자동차 생산, 3년 연속 세계 5위자동차수출 '현대-삼성 웃고 기아-대우-쌍용은 울고' 과거 내용 찾기동반성장위 창립 1주년 맞아Archived"중기적합 3개업종 합의 무시한 채 선정"李대통령, 사업 무분별 확장 소상공인 생계 위협 질타삼성-LG, 서민업종인 빵·분식사업 잇따라 철수상생은 뒷전…SSM ‘몸집 불리기’ 혈안Archived“경부고속도에 '아시안하이웨이' 표지판”'철의 실크로드' 앞서 '말(言)의 실크로드'부터, 프레시안 정창현, 2008-10-01“'서울 지하철은 안전한가?'”“서울시 “올해 안에 모든 지하철역 스크린도어 설치””“부산지하철 1,2호선 승강장 안전펜스 설치 완료”“전교조, 정부 노조 통계서 처음 빠져”“[Weekly BIZ] 도요타 '제로 이사회'가 리콜 사태 불러들였다”“S Korea slams high tuition costs”““정치가 여론 양극화 부채질… 합리주의 절실””“〈"`촛불집회'는 민주주의의 질적 변화 상징"〉”““촛불집회가 민주주의 왜곡 초래””“국민 65%, "한국 노사관계 대립적"”“한국 국가경쟁력 27위‥노사관계 '꼴찌'”“제대로 형성되지 않은 대한민국 이념지형”“[신년기획-갈등의 시대] 갈등지수 OECD 4위…사회적 손실 GDP 27% 무려 300조”“2012 총선-대선의 키워드는 '국민과 소통'”“한국 삶의 질 27위, 2000년과 2008년 연속 하위권 머물러”“[해피 코리아] 행복점수 68점…해외 평가선 '낙제점'”“한국 어린이·청소년 행복지수 3년 연속 OECD ‘꼴찌’”“한국 이혼율 OECD중 8위”“[통계청] 한국 이혼율 OECD 4위”“오피니언 [이렇게 생각한다] `부부의 날` 에 돌아본 이혼율 1위 한국”“Suicide Rates by Country, Global Health Observatory Data Repository.”“1. 또 다른 차별”“오피니언 [편집자에게] '왕따'와 '패거리 정치' 심리는 닮은꼴”“[미래한국리포트] 무한경쟁에 빠진 대한민국”“대학생 98% "외모가 경쟁력이라는 말 동의"”“특급호텔 웨딩·200만원대 유모차… "남보다 더…" 호화病, 고질병 됐다”“[스트레스 공화국] ① 경쟁사회, 스트레스 쌓인다”““매일 30여명 자살 한국, 의사보다 무속인에…””“"자살 부르는 '우울증', 환자 중 85% 치료 안 받아"”“정신병원을 가다”“대한민국도 ‘묻지마 범죄’,안전지대 아니다”“유엔 "학생 '성적 지향'에 따른 차별 금지하라"”“유엔아동권리위원회 보고서 및 번역본 원문”“고졸 성공스토리 담은 '제빵왕 김탁구' 드라마 나온다”“‘빛 좋은 개살구’ 고졸 취업…실습 대신 착취”원본 문서“정신건강, 사회적 편견부터 고쳐드립니다”‘소통’과 ‘행복’에 목 마른 사회가 잠들어 있던 ‘심리학’ 깨웠다“[포토] 사유리-곽금주 교수의 유쾌한 심리상담”“"올해 한국인 평균 영화관람횟수 세계 1위"(종합)”“[게임연중기획] 게임은 문화다-여가활동 1순위 게임”“영화속 ‘영어 지상주의’ …“왠지 씁쓸한데””“2월 `신문 부수 인증기관` 지정..방송법 후속작업”“무료신문 성장동력 ‘차별성’과 ‘갈등해소’”대한민국 국회 법률지식정보시스템"Pew Research Center's Religion & Public Life Project: South Korea"“amp;vwcd=MT_ZTITLE&path=인구·가구%20>%20인구총조사%20>%20인구부문%20>%20 총조사인구(2005)%20>%20전수부문&oper_YN=Y&item=&keyword=종교별%20인구& amp;lang_mode=kor&list_id= 2005년 통계청 인구 총조사”원본 문서“한국인이 좋아하는 취미와 운동 (2004-2009)”“한국인이 좋아하는 취미와 운동 (2004-2014)”Archived“한국, `부분적 언론자유국' 강등〈프리덤하우스〉”“국경없는기자회 "한국, 인터넷감시 대상국"”“한국, 조선산업 1위 유지(S. Korea Stays Top Shipbuilding Nation) RZD-Partner Portal”원본 문서“한국, 4년 만에 ‘선박건조 1위’”“옛 마산시,인터넷속도 세계 1위”“"한국 초고속 인터넷망 세계1위"”“인터넷·휴대폰 요금, 외국보다 훨씬 비싸”“한국 관세행정 6년 연속 세계 '1위'”“한국 교통사고 사망자 수 OECD 회원국 중 2위”“결핵 후진국' 한국, 환자가 급증한 이유는”“수술은 신중해야… 자칫하면 생명 위협”대한민국분류대한민국의 지도대한민국 정부대표 다국어포털대한민국 전자정부대한민국 국회한국방송공사about korea and information korea브리태니커 백과사전(한국편)론리플래닛의 정보(한국편)CIA의 세계 정보(한국편)마리암 부디아 (Mariam Budia),『한국: 하늘이 내린 한 폭의 그림』, 서울: 트랜스라틴 19호 (2012년 3월)대한민국ehehehehehehehehehehehehehehWorldCat132441370n791268020000 0001 2308 81034078029-6026373548cb11863345f(데이터)00573706ge128495