french-conjugator(1) [debian man page]
french-conjugator(1) french-conjugator(1) NAME
french-conjugator - conjugate French verbs SYNOPSIS
echo aimer | french-conjugator > result.txt DESCRIPTION
french-conjugator reads the infinitive form of French verbs from the command line or from standard input and writes (to standard output) the complete conjugation of those verbs, if they are known. The standard input is not read if verbs are passed as command-line arguments. Each mode and tense is introduced by a line that starts with a hyphen and a space, and ends with a colon. The mode and tense in that line are always in English, regardless of the user's current locale. (This is meant to facilitate automatic parsing of the output. For a French user interface, see the GNOME application and applet.) The conjugation is ended with a line that only contains a hyphen. If the given verb is unknown or not in the infinitive form, only this line is written. The command flushes its output buffer after finishing each answer. This allows the command to be easily called from another program through two pipes. The command starts by loading its database from XML files (stored typically in /usr/share/verbiste). This takes some time, so it is a good idea to have the command answer many requests instead of running it for each request. The verbiste library's source archive contains Perl and Java example programs that illustrate this technique. There must not be any leading or trailing white spaces on the lines read by the command. In the past participle tense, four lines are written: they correspond in order to the masculine singular, masculine plural, feminine singu- lar and feminine plural. OPTIONS
--help display a help page and exit --version display version information and exit --lang=L select the language to use (fr for French or it for Italian); French is the default language --mode=M only display mode M, where M can be infinitive, indicative, conditional, subjunctive, imperative or participle --tense=T only display tense T, where T can be present, past, imperfect or future --pronouns show the pronouns --utf8 assume that the terminal uses the UTF-8 encoding instead of Latin-1 (ISO-8859-1); try this option if Verbiste claims not to know a verb that contains an accented character --all-infinitives print the infinitive form of all the verbs in the knowledge base, one per line, unsorted; other command-line arguments are ignored EXAMPLES
$ french-conjugator aimer - infinitive present: aimer - indicative present: aime aimes aime aimons aimez aiment - indicative imperfect: aimais aimais aimait [...] - participle past: aime aimes aimee aimees - LICENSE
This program is free software; you may redistribute it under the terms of the GNU General Public License. This program has absolutely no warranty. AUTHOR
See the verbiste(3) manual page. BUGS
See the verbiste(3) manual page. SEE ALSO
verbiste(3), french-deconjugator(1). April 28th, 2012 french-conjugator(1)
Check Out this Related Man Page
srchtxt(1) User Commands srchtxt(1) NAME
srchtxt - display contents of, or search for a text string in, message data bases SYNOPSIS
srchtxt [-s] [-l locale] [ -m msgfile ,...] [text] DESCRIPTION
The srchtxt utility is used to display all the text strings in message data bases, or to search for a text string in message data bases (see mkmsgs(1)). These data bases are files in the directory /usr/lib/locale/locale/LC_MESSAGES (see setlocale(3C)), unless a file name given with the -m option contains a /. The directory locale can be viewed as the name of the language in which the text strings are writ- ten. If the -l option is not specified, the files accessed will be determined by the value of the environment variable LC_MESSAGES. If LC_MESSAGES is not set, the files accessed will be determined by the value of the environment variable LANG. If LANG is not set, the files accessed will be in the directory /usr/lib/locale//C/LC_MESSAGES , which contains default strings. If no text argument is present, then all the text strings in the files accessed will be displayed. If the -s option is not specified, the displayed text is prefixed by message sequence numbers. The message sequence numbers are enclosed in angle brackets: <msgfile:msgnum>. msgfile name of the file where the displayed text occurred msgnum sequence number in msgfile where the displayed text occurred This display is in the format used by gettxt(1) and gettxt(3C). OPTIONS
-s Suppress printing of the message sequence numbers of the messages being displayed. -l locale Access files in the directory /usr/lib/locale/locale/LC_MESSAGES. If -m msgfile is also supplied, lOCALE is ignored for msgfiles containing a /. -m msgfile Access files specified by one or more msgfiles. If msgfile contains a / character, then msgfile is interpreted as a path- name; otherwise, it will be assumed to be in the directory determined as described above. To specify more than one msgfile, separate the file names using commas. text Search for the text string specified by text and display each one that matches. text can take the form of a regular expres- sion; see regexp(5). EXAMPLES
Example 1: Using srchtxt If message files have been installed in a locale named french by using mkmsgs(1), then you could display the entire set of text strings in the french locale (/usr/lib/locale/french/LC_MESSAGES/* ) by typing: example% srchtxt -l french Example 2: Using srchtxt If a set of error messages associated with the operating system have been installed in the file UX in the french locale (/usr/lib/locale/french/LC_MESSAGE/UX ), then, using the value of the LANG environment variable to determine the locale to be searched, you could search that file in that locale for all error messages dealing with files by typing: example% setenv LANG=french; export LANG example% srchtxt -m UX "[Ff]ichier" If /usr/lib/locale/french/LC_MESSAGES/UX contained the following strings: Erreur E/S Liste d'arguments trop longue Fichier inexistant Argument invalide Trop de fichiers ouverts Fichier trop long Trop de liens Argument hors du domaine Identificateur supprim Etreinte fatale . . . then the following strings would be displayed: <UX:3>Fichier inexistant <UX:5>Trop de fichiers ouverts <UX:6>Fichier trop long Example 3: Using srchtxt If a set of error messages associated with the operating system have been installed in the file UX and a set of error messages associated with the INGRESS data base product have been installed in the file ingress, both in the german locale, then you could search for the pat- tern [Dd]atei in both the files UX and ingress in the german locale by typing: example% srchtxt -l german -m UX,ingress "[Dd]atei" ENVIRONMENT VARIABLES
See environ(5) for a description of the LC_CTYPE environment variable that affects the execution of srchtxt. FILES
/usr/lib/locale/C/LC_MESSAGES/* default files created by mkmsgs(1) /usr/lib/locale/locale/LC_MESSAGES/* message files created by mkmsgs(1) ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | |Availability |SUNWloc | +-----------------------------+-----------------------------+ SEE ALSO
exstr(1), gettxt(1), locale(1), mkmsgs(1), gettxt(3C), setlocale(3C), attributes(5), environ(5), locale(5), regexp(5) DIAGNOSTICS
The error messages produced by srchtxt are intended to be self-explanatory. They indicate an error in the command line or errors encoun- tered while searching for a particular locale and/or message file. SunOS 5.10 20 Dec 1996 srchtxt(1)