python-docs-fr/howto/curses.po

# SOME DESCRIPTIVE TITLE.
# Copyright (C) 1990-2016, Python Software Foundation
# This file is distributed under the same license as the Python package.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Python 2.7\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2016-10-30 10:44+0100\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"

#: ../Doc/howto/curses.rst:5
msgid "Curses Programming with Python"
msgstr ""

#: ../Doc/howto/curses.rst:7
msgid "A.M. Kuchling, Eric S. Raymond"
msgstr ""

#: ../Doc/howto/curses.rst:8
msgid "2.03"
msgstr ""

#: ../Doc/howto/curses.rst:0
msgid "Abstract"
msgstr "Résumé"

#: ../Doc/howto/curses.rst:13
msgid ""
"This document describes how to write text-mode programs with Python 2.x, "
"using the :mod:`curses` extension module to control the display."
msgstr ""

#: ../Doc/howto/curses.rst:18
msgid "What is curses?"
msgstr ""

#: ../Doc/howto/curses.rst:20
msgid ""
"The curses library supplies a terminal-independent screen-painting and "
"keyboard-handling facility for text-based terminals; such terminals include "
"VT100s, the Linux console, and the simulated terminal provided by X11 "
"programs such as xterm and rxvt.  Display terminals support various control "
"codes to perform common operations such as moving the cursor, scrolling the "
"screen, and erasing areas.  Different terminals use widely differing codes, "
"and often have their own minor quirks."
msgstr ""

#: ../Doc/howto/curses.rst:28
msgid ""
"In a world of X displays, one might ask \"why bother\"?  It's true that "
"character-cell display terminals are an obsolete technology, but there are "
"niches in which being able to do fancy things with them are still valuable.  "
"One is on small-footprint or embedded Unixes that don't carry an X server.  "
"Another is for tools like OS installers and kernel configurators that may "
"have to run before X is available."
msgstr ""

#: ../Doc/howto/curses.rst:35
msgid ""
"The curses library hides all the details of different terminals, and "
"provides the programmer with an abstraction of a display, containing "
"multiple non-overlapping windows.  The contents of a window can be changed "
"in various ways-- adding text, erasing it, changing its appearance--and the "
"curses library will automagically figure out what control codes need to be "
"sent to the terminal to produce the right output."
msgstr ""

#: ../Doc/howto/curses.rst:42
msgid ""
"The curses library was originally written for BSD Unix; the later System V "
"versions of Unix from AT&T added many enhancements and new functions. BSD "
"curses is no longer maintained, having been replaced by ncurses, which is an "
"open-source implementation of the AT&T interface.  If you're using an open-"
"source Unix such as Linux or FreeBSD, your system almost certainly uses "
"ncurses.  Since most current commercial Unix versions are based on System V "
"code, all the functions described here will probably be available.  The "
"older versions of curses carried by some proprietary Unixes may not support "
"everything, though."
msgstr ""

#: ../Doc/howto/curses.rst:52
msgid ""
"No one has made a Windows port of the curses module.  On a Windows platform, "
"try the Console module written by Fredrik Lundh.  The Console module "
"provides cursor-addressable text output, plus full support for mouse and "
"keyboard input, and is available from http://effbot.org/zone/console-index."
"htm."
msgstr ""

#: ../Doc/howto/curses.rst:59
msgid "The Python curses module"
msgstr ""

#: ../Doc/howto/curses.rst:61
msgid ""
"Thy Python module is a fairly simple wrapper over the C functions provided "
"by curses; if you're already familiar with curses programming in C, it's "
"really easy to transfer that knowledge to Python.  The biggest difference is "
"that the Python interface makes things simpler, by merging different C "
"functions such as :func:`addstr`, :func:`mvaddstr`, :func:`mvwaddstr`, into "
"a single :meth:`addstr` method.  You'll see this covered in more detail "
"later."
msgstr ""

#: ../Doc/howto/curses.rst:68
msgid ""
"This HOWTO is simply an introduction to writing text-mode programs with "
"curses and Python. It doesn't attempt to be a complete guide to the curses "
"API; for that, see the Python library guide's section on ncurses, and the C "
"manual pages for ncurses.  It will, however, give you the basic ideas."
msgstr ""

#: ../Doc/howto/curses.rst:75
msgid "Starting and ending a curses application"
msgstr ""

#: ../Doc/howto/curses.rst:77
msgid ""
"Before doing anything, curses must be initialized.  This is done by calling "
"the :func:`initscr` function, which will determine the terminal type, send "
"any required setup codes to the terminal, and create various internal data "
"structures.  If successful, :func:`initscr` returns a window object "
"representing the entire screen; this is usually called ``stdscr``, after the "
"name of the corresponding C variable. ::"
msgstr ""

#: ../Doc/howto/curses.rst:87
msgid ""
"Usually curses applications turn off automatic echoing of keys to the "
"screen, in order to be able to read keys and only display them under certain "
"circumstances. This requires calling the :func:`noecho` function. ::"
msgstr ""

#: ../Doc/howto/curses.rst:93
msgid ""
"Applications will also commonly need to react to keys instantly, without "
"requiring the Enter key to be pressed; this is called cbreak mode, as "
"opposed to the usual buffered input mode. ::"
msgstr ""

#: ../Doc/howto/curses.rst:99
msgid ""
"Terminals usually return special keys, such as the cursor keys or navigation "
"keys such as Page Up and Home, as a multibyte escape sequence.  While you "
"could write your application to expect such sequences and process them "
"accordingly, curses can do it for you, returning a special value such as :"
"const:`curses.KEY_LEFT`.  To get curses to do the job, you'll have to enable "
"keypad mode. ::"
msgstr ""

#: ../Doc/howto/curses.rst:108
msgid ""
"Terminating a curses application is much easier than starting one. You'll "
"need to call  ::"
msgstr ""

#: ../Doc/howto/curses.rst:113
msgid ""
"to reverse the curses-friendly terminal settings. Then call the :func:"
"`endwin` function to restore the terminal to its original operating mode. ::"
msgstr ""

#: ../Doc/howto/curses.rst:118
msgid ""
"A common problem when debugging a curses application is to get your terminal "
"messed up when the application dies without restoring the terminal to its "
"previous state.  In Python this commonly happens when your code is buggy and "
"raises an uncaught exception.  Keys are no longer echoed to the screen when "
"you type them, for example, which makes using the shell difficult."
msgstr ""

#: ../Doc/howto/curses.rst:124
msgid ""
"In Python you can avoid these complications and make debugging much easier "
"by importing the :func:`curses.wrapper` function.  It takes a callable and "
"does the initializations described above, also initializing colors if color "
"support is present.  It then runs your provided callable and finally "
"deinitializes appropriately.  The callable is called inside a try-catch "
"clause which catches exceptions, performs curses deinitialization, and then "
"passes the exception upwards.  Thus, your terminal won't be left in a funny "
"state on exception."
msgstr ""

#: ../Doc/howto/curses.rst:134
msgid "Windows and Pads"
msgstr ""

#: ../Doc/howto/curses.rst:136
msgid ""
"Windows are the basic abstraction in curses.  A window object represents a "
"rectangular area of the screen, and supports various methods to display "
"text, erase it, allow the user to input strings, and so forth."
msgstr ""

#: ../Doc/howto/curses.rst:140
msgid ""
"The ``stdscr`` object returned by the :func:`initscr` function is a window "
"object that covers the entire screen.  Many programs may need only this "
"single window, but you might wish to divide the screen into smaller windows, "
"in order to redraw or clear them separately. The :func:`newwin` function "
"creates a new window of a given size, returning the new window object. ::"
msgstr ""

#: ../Doc/howto/curses.rst:150
msgid ""
"A word about the coordinate system used in curses: coordinates are always "
"passed in the order *y,x*, and the top-left corner of a window is coordinate "
"(0,0). This breaks a common convention for handling coordinates, where the "
"*x* coordinate usually comes first.  This is an unfortunate difference from "
"most other computer applications, but it's been part of curses since it was "
"first written, and it's too late to change things now."
msgstr ""

#: ../Doc/howto/curses.rst:157
msgid ""
"When you call a method to display or erase text, the effect doesn't "
"immediately show up on the display.  This is because curses was originally "
"written with slow 300-baud terminal connections in mind; with these "
"terminals, minimizing the time required to redraw the screen is very "
"important.  This lets curses accumulate changes to the screen, and display "
"them in the most efficient manner.  For example, if your program displays "
"some characters in a window, and then clears the window, there's no need to "
"send the original characters because they'd never be visible."
msgstr ""

#: ../Doc/howto/curses.rst:166
msgid ""
"Accordingly, curses requires that you explicitly tell it to redraw windows, "
"using the :func:`refresh` method of window objects.  In practice, this "
"doesn't really complicate programming with curses much. Most programs go "
"into a flurry of activity, and then pause waiting for a keypress or some "
"other action on the part of the user.  All you have to do is to be sure that "
"the screen has been redrawn before pausing to wait for user input, by simply "
"calling ``stdscr.refresh()`` or the :func:`refresh` method of some other "
"relevant window."
msgstr ""

#: ../Doc/howto/curses.rst:175
msgid ""
"A pad is a special case of a window; it can be larger than the actual "
"display screen, and only a portion of it displayed at a time. Creating a pad "
"simply requires the pad's height and width, while refreshing a pad requires "
"giving the coordinates of the on-screen area where a subsection of the pad "
"will be displayed.   ::"
msgstr ""

#: ../Doc/howto/curses.rst:194
msgid ""
"The :func:`refresh` call displays a section of the pad in the rectangle "
"extending from coordinate (5,5) to coordinate (20,75) on the screen; the "
"upper left corner of the displayed section is coordinate (0,0) on the pad.  "
"Beyond that difference, pads are exactly like ordinary windows and support "
"the same methods."
msgstr ""

#: ../Doc/howto/curses.rst:200
msgid ""
"If you have multiple windows and pads on screen there is a more efficient "
"way to go, which will prevent annoying screen flicker at refresh time.  Use "
"the :meth:`noutrefresh` method of each window to update the data structure "
"representing the desired state of the screen; then change the physical "
"screen to match the desired state in one go with the function :func:"
"`doupdate`.  The normal :meth:`refresh` method calls :func:`doupdate` as its "
"last act."
msgstr ""

#: ../Doc/howto/curses.rst:209
msgid "Displaying Text"
msgstr ""

#: ../Doc/howto/curses.rst:211
msgid ""
"From a C programmer's point of view, curses may sometimes look like a twisty "
"maze of functions, all subtly different.  For example, :func:`addstr` "
"displays a string at the current cursor location in the ``stdscr`` window, "
"while :func:`mvaddstr` moves to a given y,x coordinate first before "
"displaying the string. :func:`waddstr` is just like :func:`addstr`, but "
"allows specifying a window to use, instead of using ``stdscr`` by default. :"
"func:`mvwaddstr` follows similarly."
msgstr ""

#: ../Doc/howto/curses.rst:219
msgid ""
"Fortunately the Python interface hides all these details; ``stdscr`` is a "
"window object like any other, and methods like :func:`addstr` accept "
"multiple argument forms.  Usually there are four different forms."
msgstr ""

#: ../Doc/howto/curses.rst:224
msgid "Form"
msgstr ""

#: ../Doc/howto/curses.rst:224 ../Doc/howto/curses.rst:282
msgid "Description"
msgstr "Description"

#: ../Doc/howto/curses.rst:226
msgid "*str* or *ch*"
msgstr ""

#: ../Doc/howto/curses.rst:226
msgid "Display the string *str* or character *ch* at the current position"
msgstr ""

#: ../Doc/howto/curses.rst:229
msgid "*str* or *ch*, *attr*"
msgstr ""

#: ../Doc/howto/curses.rst:229
msgid ""
"Display the string *str* or character *ch*, using attribute *attr* at the "
"current position"
msgstr ""

#: ../Doc/howto/curses.rst:233
msgid "*y*, *x*, *str* or *ch*"
msgstr ""

#: ../Doc/howto/curses.rst:233
msgid "Move to position *y,x* within the window, and display *str* or *ch*"
msgstr ""

#: ../Doc/howto/curses.rst:236
msgid "*y*, *x*, *str* or *ch*, *attr*"
msgstr ""

#: ../Doc/howto/curses.rst:236
msgid ""
"Move to position *y,x* within the window, and display *str* or *ch*, using "
"attribute *attr*"
msgstr ""

#: ../Doc/howto/curses.rst:240
msgid ""
"Attributes allow displaying text in highlighted forms, such as in boldface, "
"underline, reverse code, or in color.  They'll be explained in more detail "
"in the next subsection."
msgstr ""

#: ../Doc/howto/curses.rst:244
msgid ""
"The :func:`addstr` function takes a Python string as the value to be "
"displayed, while the :func:`addch` functions take a character, which can be "
"either a Python string of length 1 or an integer.  If it's a string, you're "
"limited to displaying characters between 0 and 255.  SVr4 curses provides "
"constants for extension characters; these constants are integers greater "
"than 255.  For example, :const:`ACS_PLMINUS` is a +/- symbol, and :const:"
"`ACS_ULCORNER` is the upper left corner of a box (handy for drawing borders)."
msgstr ""

#: ../Doc/howto/curses.rst:252
msgid ""
"Windows remember where the cursor was left after the last operation, so if "
"you leave out the *y,x* coordinates, the string or character will be "
"displayed wherever the last operation left off.  You can also move the "
"cursor with the ``move(y,x)`` method.  Because some terminals always display "
"a flashing cursor, you may want to ensure that the cursor is positioned in "
"some location where it won't be distracting; it can be confusing to have the "
"cursor blinking at some apparently random location."
msgstr ""

#: ../Doc/howto/curses.rst:260
msgid ""
"If your application doesn't need a blinking cursor at all, you can call "
"``curs_set(0)`` to make it invisible.  Equivalently, and for compatibility "
"with older curses versions, there's a ``leaveok(bool)`` function.  When "
"*bool* is true, the curses library will attempt to suppress the flashing "
"cursor, and you won't need to worry about leaving it in odd locations."
msgstr ""

#: ../Doc/howto/curses.rst:268
msgid "Attributes and Color"
msgstr ""

#: ../Doc/howto/curses.rst:270
msgid ""
"Characters can be displayed in different ways.  Status lines in a text-based "
"application are commonly shown in reverse video; a text viewer may need to "
"highlight certain words.  curses supports this by allowing you to specify an "
"attribute for each cell on the screen."
msgstr ""

#: ../Doc/howto/curses.rst:275
msgid ""
"An attribute is an integer, each bit representing a different attribute.  "
"You can try to display text with multiple attribute bits set, but curses "
"doesn't guarantee that all the possible combinations are available, or that "
"they're all visually distinct.  That depends on the ability of the terminal "
"being used, so it's safest to stick to the most commonly available "
"attributes, listed here."
msgstr ""

#: ../Doc/howto/curses.rst:282
msgid "Attribute"
msgstr "Attribut"

#: ../Doc/howto/curses.rst:284
msgid ":const:`A_BLINK`"
msgstr ""

#: ../Doc/howto/curses.rst:284
msgid "Blinking text"
msgstr ""

#: ../Doc/howto/curses.rst:286
msgid ":const:`A_BOLD`"
msgstr ""

#: ../Doc/howto/curses.rst:286
msgid "Extra bright or bold text"
msgstr ""

#: ../Doc/howto/curses.rst:288
msgid ":const:`A_DIM`"
msgstr ""

#: ../Doc/howto/curses.rst:288
msgid "Half bright text"
msgstr ""

#: ../Doc/howto/curses.rst:290
msgid ":const:`A_REVERSE`"
msgstr ""

#: ../Doc/howto/curses.rst:290
msgid "Reverse-video text"
msgstr ""

#: ../Doc/howto/curses.rst:292
msgid ":const:`A_STANDOUT`"
msgstr ""

#: ../Doc/howto/curses.rst:292
msgid "The best highlighting mode available"
msgstr ""

#: ../Doc/howto/curses.rst:294
msgid ":const:`A_UNDERLINE`"
msgstr ""

#: ../Doc/howto/curses.rst:294
msgid "Underlined text"
msgstr ""

#: ../Doc/howto/curses.rst:297
msgid ""
"So, to display a reverse-video status line on the top line of the screen, "
"you could code::"
msgstr ""

#: ../Doc/howto/curses.rst:304
msgid ""
"The curses library also supports color on those terminals that provide it. "
"The most common such terminal is probably the Linux console, followed by "
"color xterms."
msgstr ""

#: ../Doc/howto/curses.rst:308
msgid ""
"To use color, you must call the :func:`start_color` function soon after "
"calling :func:`initscr`, to initialize the default color set (the :func:"
"`curses.wrapper.wrapper` function does this automatically).  Once that's "
"done, the :func:`has_colors` function returns TRUE if the terminal in use "
"can actually display color.  (Note: curses uses the American spelling "
"'color', instead of the Canadian/British spelling 'colour'.  If you're used "
"to the British spelling, you'll have to resign yourself to misspelling it "
"for the sake of these functions.)"
msgstr ""

#: ../Doc/howto/curses.rst:317
msgid ""
"The curses library maintains a finite number of color pairs, containing a "
"foreground (or text) color and a background color.  You can get the "
"attribute value corresponding to a color pair with the :func:`color_pair` "
"function; this can be bitwise-OR'ed with other attributes such as :const:"
"`A_REVERSE`, but again, such combinations are not guaranteed to work on all "
"terminals."
msgstr ""

#: ../Doc/howto/curses.rst:323
msgid "An example, which displays a line of text using color pair 1::"
msgstr ""

#: ../Doc/howto/curses.rst:328
msgid ""
"As I said before, a color pair consists of a foreground and background "
"color. :func:`start_color` initializes 8 basic colors when it activates "
"color mode. They are: 0:black, 1:red, 2:green, 3:yellow, 4:blue, 5:magenta, "
"6:cyan, and 7:white.  The curses module defines named constants for each of "
"these colors: :const:`curses.COLOR_BLACK`, :const:`curses.COLOR_RED`, and so "
"forth."
msgstr ""

#: ../Doc/howto/curses.rst:334
msgid ""
"The ``init_pair(n, f, b)`` function changes the definition of color pair "
"*n*, to foreground color f and background color b.  Color pair 0 is hard-"
"wired to white on black, and cannot be changed."
msgstr ""

#: ../Doc/howto/curses.rst:338
msgid ""
"Let's put all this together. To change color 1 to red text on a white "
"background, you would call::"
msgstr ""

#: ../Doc/howto/curses.rst:343
msgid ""
"When you change a color pair, any text already displayed using that color "
"pair will change to the new colors.  You can also display new text in this "
"color with::"
msgstr ""

#: ../Doc/howto/curses.rst:349
msgid ""
"Very fancy terminals can change the definitions of the actual colors to a "
"given RGB value.  This lets you change color 1, which is usually red, to "
"purple or blue or any other color you like.  Unfortunately, the Linux "
"console doesn't support this, so I'm unable to try it out, and can't provide "
"any examples.  You can check if your terminal can do this by calling :func:"
"`can_change_color`, which returns TRUE if the capability is there.  If "
"you're lucky enough to have such a talented terminal, consult your system's "
"man pages for more information."
msgstr ""

#: ../Doc/howto/curses.rst:359
msgid "User Input"
msgstr ""

#: ../Doc/howto/curses.rst:361
msgid ""
"The curses library itself offers only very simple input mechanisms. Python's "
"support adds a text-input widget that makes up some of the lack."
msgstr ""

#: ../Doc/howto/curses.rst:364
msgid ""
"The most common way to get input to a window is to use its :meth:`getch` "
"method. :meth:`getch` pauses and waits for the user to hit a key, displaying "
"it if :func:`echo` has been called earlier.  You can optionally specify a "
"coordinate to which the cursor should be moved before pausing."
msgstr ""

#: ../Doc/howto/curses.rst:369
msgid ""
"It's possible to change this behavior with the method :meth:`nodelay`. After "
"``nodelay(1)``, :meth:`getch` for the window becomes non-blocking and "
"returns ``curses.ERR`` (a value of -1) when no input is ready.  There's also "
"a :func:`halfdelay` function, which can be used to (in effect) set a timer "
"on each :meth:`getch`; if no input becomes available within a specified "
"delay (measured in tenths of a second), curses raises an exception."
msgstr ""

#: ../Doc/howto/curses.rst:376
msgid ""
"The :meth:`getch` method returns an integer; if it's between 0 and 255, it "
"represents the ASCII code of the key pressed.  Values greater than 255 are "
"special keys such as Page Up, Home, or the cursor keys. You can compare the "
"value returned to constants such as :const:`curses.KEY_PPAGE`, :const:"
"`curses.KEY_HOME`, or :const:`curses.KEY_LEFT`.  Usually the main loop of "
"your program will look something like this::"
msgstr ""

#: ../Doc/howto/curses.rst:392
msgid ""
"The :mod:`curses.ascii` module supplies ASCII class membership functions "
"that take either integer or 1-character-string arguments; these may be "
"useful in writing more readable tests for your command interpreters.  It "
"also supplies conversion functions  that take either integer or 1-character-"
"string arguments and return the same type.  For example, :func:`curses.ascii."
"ctrl` returns the control character corresponding to its argument."
msgstr ""

#: ../Doc/howto/curses.rst:399
msgid ""
"There's also a method to retrieve an entire string, :const:`getstr()`.  It "
"isn't used very often, because its functionality is quite limited; the only "
"editing keys available are the backspace key and the Enter key, which "
"terminates the string.  It can optionally be limited to a fixed number of "
"characters. ::"
msgstr ""

#: ../Doc/howto/curses.rst:409
msgid ""
"The Python :mod:`curses.textpad` module supplies something better. With it, "
"you can turn a window into a text box that supports an Emacs-like set of "
"keybindings.  Various methods of :class:`Textbox` class support editing with "
"input validation and gathering the edit results either with or without "
"trailing spaces.   See the library documentation on :mod:`curses.textpad` "
"for the details."
msgstr ""

#: ../Doc/howto/curses.rst:418
msgid "For More Information"
msgstr ""

#: ../Doc/howto/curses.rst:420
msgid ""
"This HOWTO didn't cover some advanced topics, such as screen-scraping or "
"capturing mouse events from an xterm instance.  But the Python library page "
"for the curses modules is now pretty complete.  You should browse it next."
msgstr ""

#: ../Doc/howto/curses.rst:424
msgid ""
"If you're in doubt about the detailed behavior of any of the ncurses entry "
"points, consult the manual pages for your curses implementation, whether "
"it's ncurses or a proprietary Unix vendor's.  The manual pages will document "
"any quirks, and provide complete lists of all the functions, attributes, "
"and :const:`ACS_\\*` characters available to you."
msgstr ""

#: ../Doc/howto/curses.rst:430
msgid ""
"Because the curses API is so large, some functions aren't supported in the "
"Python interface, not because they're difficult to implement, but because no "
"one has needed them yet.  Feel free to add them and then submit a patch.  "
"Also, we don't yet have support for the menu library associated with "
"ncurses; feel free to add that."
msgstr ""

#: ../Doc/howto/curses.rst:436
msgid ""
"If you write an interesting little program, feel free to contribute it as "
"another demo.  We can always use more of them!"
msgstr ""

#: ../Doc/howto/curses.rst:439
msgid "The ncurses FAQ: http://invisible-island.net/ncurses/ncurses.faq.html"
msgstr ""