Lines Matching +refs:po +refs:first +refs:entry
218 * Prioritizing messages:: How to find which messages to translate first
243 * po/POTFILES.in:: `POTFILES.in' in `po/'
244 * po/LINGUAS:: `LINGUAS' in `po/'
245 * po/Makevars:: `Makevars' in `po/'
246 * po/Rules-*:: Extending `Makefile' in `po/'
263 * AM_PO_SUBDIRS:: AM_PO_SUBDIRS in `po.m4'
495 "i18n" and "l10n" instead, quoting the first and last letter of each
671 The letters PO in `.po' files means Portable Object, to distinguish it
674 developed by Uniforum, and first implemented by Sun in their Solaris
724 | +----> msgmerge ------> LANG.po ---->--------' |
728 | +--- New LANG.po <--------------------'
735 As a programmer, the first step to bringing GNU `gettext' into your
781 The first time through, there is no `LANG.po' yet, so the `msgmerge'
783 `LANG.po', where LANG represents the target language. See *Note
794 While adding the translated messages into the `LANG.po' PO file, if
825 time, so the translations carried by `LANG.po' are slowly fading out of
837 existing `LANG.po' file, by comparing it with a newer `PACKAGE.pot'
841 `msgmerge' comments out as obsolete, in `LANG.po', those already
849 `LANG.po' file offering translations for all strings.
924 the distribution for the `ABOUT-NLS' information file, for some `LL.po'
925 files, often kept together into some `po/' directory, or for an `intl/'
926 directory. Internationalized packages have usually many `LL.po' files,
966 A PO file is made up of many entries, each entry holding the relation
970 language. One PO file "entry" has the following schematic structure:
985 A simple entry can look like this:
1012 first the untranslated string as it appears in the original program
1023 deleting them, and only by deleting the whole entry. On the other
1180 Such an entry can look like this:
1182 #: src/msgcmp.c:338 src/po-lex.c:699
1198 the very last entry of a PO file. Such lines are not part of any entry,
1219 In this example, the empty string is used on the first line, to allow
1228 `Here' was promoted on the first line, right after `msgid'.(1) It was
1602 This marking operation has two goals. The first goal of marking is
1709 candidate for translation (`po-tags-search').
1712 Mark the last string found with `_()' (`po-mark-translatable').
1717 management of these keywords (`po-select-mark-and-mark').
1720 The `,' (`po-tags-search') command searches for the next occurrence
1741 first time you use the command. You may later change your `TAGS' file
1750 request that the search be restarted all over again from the first
1759 also reinitialize the regular Emacs tags searching to the first tags
1762 The `M-,' (`po-mark-translatable') command will mark the recently
1764 (`po-select-mark-and-mark') command will request that you type one
1767 untranslated entry for the string being marked, and make it the current
1768 entry (making it easy for you to immediately proceed to its
1779 explicitly type all keywords all the time. The first such speedup is
1848 useful for `msgfmt' to test all the strings in the `.po' file. This
1854 only a heuristic. In the `.po' file the entry is marked using the
1880 would prevent translating the `.po' file. The method to prevent this
1920 The first task can be fulfilled by creating a new keyword, which
1998 name: The first name is (with Unicode escapes)
2017 #. name: The first name is (with Unicode escapes)
2038 major hassle for translators using GNU Emacs or XEmacs with po-mode.
2074 that all entry points of the library call the initialization
2132 `xgettext' creates a file named `DOMAINNAME.po'. You should then
2168 searched relative to this list of directories. The resulting `.po'
2179 Use `NAME.po' for output (instead of `messages.po').
2183 Write output to specified file (instead of `NAME.po' or
2184 `messages.po').
2261 in the first argument of each call to the function or macro ID.
2366 string requirement for a `_("string")' call to its first argument,
2407 `--force-po'
2412 Write the .po file using indented style.
2458 Don't write header with `msgid ""' entry.
2478 simply because `xgettext' was first used in the GNU project.
2541 `LANG.po', as a copy of the `PACKAGE.pot' template file with
2543 and in the header entry (the first entry, near the beginning of the
2550 $ cd po
2554 do so, the translator copies `PACKAGE.pot' to `LANG.po'. Then she
2555 modifies the initial comments and the header entry of this file.
2671 Modifying the header entry can already be done using PO mode: in
2672 Emacs, type `M-x po-mode RET' and then `RET' again to start editing the
2673 entry. You should fill in the following fields.
2720 `http://www.iro.umontreal.ca/contrib/po/HTML/', in the "National
2854 msgmerge [OPTION] DEF.po REF.pot
2856 The `msgmerge' program merges two Uniforum style .po files together.
2857 The DEF.po file is an existing PO file with translations which will be
2870 `DEF.po'
2879 searched relative to this list of directories. The resulting `.po'
2893 Update DEF.po. Do nothing if DEF.po is already up to date.
2910 The result is written back to DEF.po.
2913 Make a backup of DEF.po
2949 Apply REF.pot to each of the domains in DEF.po.
2976 `--force-po'
2981 Write the .po file using indented style.
3128 (cons '("\\.po\\'\\|\\.po\\." . po-mode) auto-mode-alist))
3129 (autoload 'po-mode "po-mode" "Major mode for translators to edit PO files" t)
3131 Later, whenever you edit some `.po' file, or any file having the
3132 string `.po.' within its name, Emacs loads `po-mode.elc' (or
3133 `po-mode.el') as needed, and automatically activates PO mode commands
3145 (modify-coding-system-alist 'file "\\.po\\'\\|\\.po\\."
3146 'po-find-file-coding-system)
3147 (autoload 'po-find-file-coding-system "po-mode")
3162 po-mode-map, which is a genuine Emacs mode, in a way that is not derived
3163 from text mode in any way. Functions found on `po-mode-hook', if any,
3183 Undo last modification to the PO file (`po-undo').
3186 Quit processing and save the PO file (`po-quit').
3190 (`po-confirm-and-quit').
3193 Temporary leave the PO file window (`po-other-window').
3197 Show help about PO mode (`po-help').
3200 Give some PO file statistics (`po-statistics').
3203 Batch validate the format of the whole PO file (`po-validate').
3206 The command `_' (`po-undo') interfaces to the Emacs _undo_ facility.
3215 The commands `Q' (`po-quit') and `q' (`po-confirm-and-quit') are
3218 saved to disk first. In both cases, and prior to all this, the
3225 The command `0' (`po-other-window') is another, softer way, to leave
3236 The command `h' (`po-help') displays a summary of all available PO
3240 The command `=' (`po-statistics') computes the total number of
3241 entries in the PO file, the ordinal of the current entry (counted from
3245 The command `V' (`po-validate') launches `msgfmt' in checking and
3246 verbose mode over the current PO file. This command first offers to
3267 The cursor in a PO file window is almost always part of an entry. The
3269 entry in the file, or when the PO file is empty. The entry where the
3270 cursor is found to be is said to be the current entry. Many PO mode
3271 commands operate on the current entry, so moving the cursor does more
3273 on which entry commands operate.
3281 Redisplay the current entry (`po-current-entry').
3284 Select the entry after the current one (`po-next-entry').
3287 Select the entry before the current one (`po-previous-entry').
3290 Select the first entry in the PO file (`po-first-entry').
3293 Select the last entry in the PO file (`po-last-entry').
3296 Record the location of the current entry for later use
3297 (`po-push-location').
3300 Return to a previously saved entry location (`po-pop-location').
3303 Exchange the current entry location with the previously saved one
3304 (`po-exchange-location').
3308 select the current entry in PO mode, including commands which move by
3310 However, there is a kind of standard way to display the current entry
3312 especially try to enforce. The command `.' (`po-current-entry') has
3313 the sole purpose of redisplaying the current entry properly, after the
3314 current entry has been changed by means external to PO mode, or the
3330 The commands `n' (`po-next-entry') and `p' (`po-previous-entry')
3331 move the cursor the entry following, or preceding, the current one. If
3332 `n' is given while the cursor is on the last entry of the PO file, or
3333 if `p' is given while the cursor is on the first entry, no move is done.
3335 The commands `<' (`po-first-entry') and `>' (`po-last-entry') move
3336 the cursor to the first entry, or last entry, of the PO file. When the
3337 cursor is located past the last entry in a PO file, most PO mode
3338 commands will return an error saying `After last entry'. Moreover, the
3340 even when the cursor is not into some PO file entry, and one may use
3347 particular entry, that she needs to browse the remainder of the PO
3354 saved onto a special stack. The command `m' (`po-push-location')
3355 merely adds the location of current entry to the stack, pushing the
3357 (`po-pop-location') consumes the top stack element and repositions the
3358 cursor to the entry associated with that top element. This position is
3363 stack, maybe for taking a look at the entry associated with the top
3367 The command `x' (`po-exchange-location') simultaneously repositions
3368 the cursor to the entry associated with the top element of the stack of
3370 current entry before the move. Consequently, repeating the `x' command
3372 translator will position the cursor on the first entry, use `m', then
3373 position to the second entry, and merely use `x' for making the switch.
3382 PO file entry, because there are so many different ways to split and
3386 particular string encoded into the `msgid' field of some entry. Even
3405 `M-x po-normalize'
3409 The special command `M-x po-normalize', which has no associated
3412 also removes any crumb after the last entry. This command may be
3418 `M-x po-normalize' presently makes three passes over the entries.
3419 The first implements heuristics for converting PO files for GNU
3425 entries. This first pass might disappear once all oldish PO files
3479 Each PO file entry for which the `msgstr' field has been filled with a
3481 is said to be a "translated" entry. Only translated entries will later
3482 be compiled by GNU `msgfmt' and become usable in programs. Other entry
3485 Some commands are more specifically related to translated entry
3489 Find the next translated entry (`po-next-translated-entry').
3492 Find the previous translated entry
3493 (`po-previous-translated-entry').
3496 The commands `t' (`po-next-translated-entry') and `T'
3497 (`po-previous-translated-entry') move forwards or backwards, chasing
3498 for an translated entry. If none is found, the search is extended and
3503 the variable `po-auto-fuzzy-on-edit' is not `nil', the entry having
3504 received a new translation first becomes a fuzzy entry, which ought to
3506 entry. *Note Fuzzy Entries::.
3514 Each PO file entry may have a set of "attributes", which are qualities
3526 translation for the new modified entry. The slight alteration in the
3532 Also, the translator may decide herself to mark an entry as fuzzy
3533 for her own convenience, when she wants to remember that the entry has
3535 to fuzzy entry processing.
3538 Find the next fuzzy entry (`po-next-fuzzy-entry').
3541 Find the previous fuzzy entry (`po-previous-fuzzy-entry').
3544 Remove the fuzzy attribute of the current entry (`po-unfuzzy').
3547 The commands `z' (`po-next-fuzzy-entry') and `Z'
3548 (`po-previous-fuzzy-entry') move forwards or backwards, chasing for a
3549 fuzzy entry. If none is found, the search is extended and wraps around
3552 The command `<TAB>' (`po-unfuzzy') removes the fuzzy attribute
3553 associated with an entry, usually leaving it translated. Further, if
3554 the variable `po-auto-select-on-unfuzzy' has not the `nil' value, the
3555 `<TAB>' command will automatically chase for another interesting entry
3556 to work on. The initial value of `po-auto-select-on-unfuzzy' is `nil'.
3558 The initial value of `po-auto-fuzzy-on-edit' is `nil'. However, if
3559 the variable `po-auto-fuzzy-on-edit' is set to `t', any entry edited
3562 an entry becomes fuzzy (if not already) whenever the translator
3564 `<TAB>' to pick another entry to work on, clearing the fuzzy attribute
3566 to chase another entry, leaving the entry fuzzy.
3569 (`po-fade-out-entry') over any translated entry to mark it as being
3571 working at this entry.
3589 untranslated entry for the modified string.
3591 The usual commands moving from entry to entry consider untranslated
3596 process of seeking for an untranslated entry, editing a translation for
3598 Some commands are more specifically related to untranslated entry
3602 Find the next untranslated entry (`po-next-untranslated-entry').
3605 Find the previous untranslated entry
3606 (`po-previous-untransted-entry').
3609 Turn the current entry into an untranslated one (`po-kill-msgstr').
3612 The commands `u' (`po-next-untranslated-entry') and `U'
3613 (`po-previous-untransted-entry') move forwards or backwards, chasing
3614 for an untranslated entry. If none is found, the search is extended
3617 An entry can be turned back into an untranslated entry by merely
3618 emptying its translation, using the command `k' (`po-kill-msgstr').
3635 The usual commands moving from entry to entry consider obsolete
3644 apply to obsolete entries, carefully leaving the entry obsolete after
3648 entry processing.
3651 Find the next obsolete entry (`po-next-obsolete-entry').
3654 Find the previous obsolete entry (`po-previous-obsolete-entry').
3657 Make an active entry obsolete, or zap out an obsolete entry
3658 (`po-fade-out-entry').
3661 The commands `o' (`po-next-obsolete-entry') and `O'
3662 (`po-previous-obsolete-entry') move forwards or backwards, chasing for
3663 an obsolete entry. If none is found, the search is extended and wraps
3666 PO mode does not provide ways for un-commenting an obsolete entry
3672 However, it is possible to comment out an active entry, so making it
3675 command `<DEL>' (`po-fade-out-entry') pushes the current entry a little
3676 further towards annihilation. If the entry is active (it is a
3677 translated entry), then it is first made fuzzy. If it is already fuzzy,
3678 then the entry is merely commented out, with confirmation. If the entry
3681 entry, usually one which is untranslated. *Note Modifying
3717 Interactively edit the translation (`po-edit-msgstr').
3722 (`po-msgid-to-msgstr').
3726 (`po-kill-msgstr').
3730 (`po-kill-ring-save-msgstr').
3734 (`po-yank-msgstr').
3737 The command `<RET>' (`po-edit-msgstr') opens a new Emacs window
3740 from the current PO file entry, all ready for edition, expunged of all
3747 The command `<LFD>' (`po-msgid-to-msgstr') initializes, or
3753 entry, the `<LFD>' command be automatically executed. If you set
3754 `po-auto-edit-with-msgid' to `t', the translation gets initialised with
3756 for `po-auto-edit-with-msgid' is `nil'.
3769 The command `k' (`po-kill-msgstr') merely empties the translation
3770 string, so turning the entry into an untranslated one. But while doing
3772 kill ring. The command `w' (`po-kill-ring-save-msgstr') has also the
3774 otherwise leaves the entry alone, and does _not_ remove the translation
3775 from the entry. Both commands use exactly the Emacs kill ring, which
3793 The command `y' (`po-yank-msgstr') completely replaces the
3794 translation of the current entry by a string taken from the kill ring.
3797 first time `y' is used, the translation receives the value of the most
3805 When a string is yanked into a PO file entry, it is fully and
3807 have. Further, if the entry is obsolete, PO mode then appropriately
3822 reflected in the PO file by the appearance of a new untranslated entry
3823 for the modified string, and the fact that the entry translating the
3826 translation from the obsolete entry, then initializing the untranslated
3827 entry `msgstr' field with this retrieved translation. Once this done,
3828 the obsolete entry is not wanted anymore, and may be safely deleted.
3830 When the translator finds an untranslated entry and suspects that a
3832 mark the current entry location, then starts chasing obsolete entries
3835 deleting the obsolete entry, knowing that `<DEL>' also _kills_ the
3837 `r' returns to the initial untranslated entry, and `y' then _yanks_ the
3872 Interactively edit the translator comments (`po-edit-comment').
3876 (`po-kill-comment').
3880 (`po-kill-ring-save-comment').
3884 (`po-yank-comment').
3894 The command `#' (`po-edit-comment') opens a new Emacs window
3896 entry. If there are no such comments, PO mode understands that the
3897 translator wants to add a comment to the entry, and she is presented
3905 Functions found on `po-subedit-mode-hook', if any, are executed after
3908 The command `K' (`po-kill-comment') gets rid of all translator
3910 `W' (`po-kill-ring-save-comment') takes a copy of the translator
3912 entry. The command `Y' (`po-yank-comment') completely replaces the
3949 Complete edition (`po-subedit-exit').
3952 Abort edition (`po-subedit-abort').
3955 Consult auxiliary PO files (`po-subedit-cycle-auxiliary').
3961 (`po-subedit-exit') may be used to return the edited translation into
3968 (`po-subedit-abort') to merely get rid of edition, while preserving the
3973 The command `C-c C-a' (`po-subedit-cycle-auxiliary') allows for
3980 Functions found on `po-subedit-mode-hook', if any, are executed after
4004 modifying another entry. Each entry being edited has its own subedit
4006 the comment of a single entry, or to edit entries in different PO
4026 relate the PO file entry to exactly where the untranslated string
4029 When the translator gets to an untranslated entry, she is fairly
4051 program source context for a PO file entry.
4055 them (`po-cycle-source-reference').
4059 (`po-select-source-reference').
4063 (`po-consider-source-path').
4067 (`po-ignore-source-path').
4070 The commands `s' (`po-cycle-source-reference') and `M-s'
4071 (`po-select-source-reference') both open another window displaying some
4074 gives source program context for the string. But if the entry has no
4084 When `s' is typed for the first time, or for a PO file entry which
4086 command reacts by giving the first context available for this entry, if
4088 current PO file entry, and the translator wandered off to do other
4094 contexts for this particular entry, getting back to the first context
4115 (`po-consider-source-path') is used to interactively enter a new
4117 (`po-ignore-source-path') is used to select, with completion, one of
4136 PO files, and also for showing contexts for the entry under work.
4141 Seek auxiliary files for another translation for the same entry
4142 (`po-cycle-auxiliary').
4145 Switch to a particular auxiliary file (`po-select-auxiliary').
4149 (`po-consider-as-auxiliary').
4153 (`po-ignore-as-auxiliary').
4156 Command `A' (`po-consider-as-auxiliary') adds the current PO file to
4158 (`po-ignore-as-auxiliary' just removes it.
4160 The command `a' (`po-cycle-auxiliary') seeks all auxiliary PO files,
4161 round-robin, searching for a translated entry in some other language
4162 having an `msgid' field identical as the one for the current entry.
4169 The command `C-c C-a' (`po-select-auxiliary') asks the translator
4173 entry, and if yes, this entry becomes current. Otherwise, the cursor
4224 msgcat -o compendium.po file1.po file2.po
4228 visible decorated; calling `msgcat' on `file1.po':
4235 and `file2.po':
4248 "#-#-#-#-# file1.po #-#-#-#-#\n"
4250 "#-#-#-#-# file2.po #-#-#-#-#\n"
4254 to decide whether the first or the second version is appropriate (or
4258 If the translator knows in advance the first found translation of a
4260 `--use-first' switch:
4262 msgcat --use-first -o compendium.po file1.po file2.po
4278 msggrep --location src/getopt.c -o compendium.po file.po
4295 msgmerge --compendium compendium.po -o file.po /dev/null file.pot
4304 msgcat --use-first -o update.po compendium1.po compendium2.po file.po
4305 msgmerge update.po file.pot | sed -e '/^#~/d' > file.po
4366 `msgen' is useful as a first step for preparing English translation
4402 that if `--use-first' is specified, they will be taken from the first
4420 searched relative to this list of directories. The resulting `.po'
4476 `--use-first'
4477 Use first available translation for each message. Don't merge
4480 `--force-po'
4485 Write the .po file using indented style.
4564 searched relative to this list of directories. The resulting `.po'
4607 `--force-po'
4612 Write the .po file using indented style.
4690 searched relative to this list of directories. The resulting `.po'
4812 `--force-po'
4816 Write the .po file using indented style.
4893 searched relative to this list of directories. The resulting `.po'
4921 FILTER wants input in a particular encoding, you can in a first step
4925 you can first convert the translation catalog to UTF-8 using the
4961 file. Thus, it can be used to convert an `sr.po' file to an
4962 `sr@latin.po' file.
4985 `--force-po'
4989 Write the .po file using indented style.
4992 Keep the header entry, i.e. the message with `msgid ""',
4993 unmodified, instead of filtering it. By default, the header entry
5066 cumulated, except that if `--use-first' is specified, they will be
5067 taken from the first translation. File positions will be cumulated.
5079 searched relative to this list of directories. The resulting `.po'
5128 `--use-first'
5129 Use first available translation for each message. Don't merge
5132 `--force-po'
5137 Write the .po file using indented style.
5210 preserved, but only from the first PO file to define them. File
5227 searched relative to this list of directories. The resulting `.po'
5279 `--force-po'
5284 Write the .po file using indented style.
5331 Don't write header with `msgid ""' entry.
5352 msgcmp [OPTION] DEF.po REF.pot
5354 The `msgcmp' program compares two Uniforum style .po files to check
5355 that both contain the same set of msgid strings. The DEF.po file is an
5365 `DEF.po'
5382 Apply REF.pot to each of the domains in DEF.po.
5385 Consider fuzzy messages in the DEF.po file like translated
5391 Consider untranslated messages in the DEF.po file like translated
5440 searched relative to this list of directories. The resulting `.po'
5535 `--force-po'
5540 Write the .po file using indented style.
5614 header entry, whereas `msgen' doesn't.
5625 searched relative to this list of directories. The resulting `.po'
5658 `--force-po'
5663 Write the .po file using indented style.
5748 COMMAND wants input in a particular encoding, you can in a first step
5752 you can first convert the translation catalog to UTF-8 using the
5766 searched relative to this list of directories. The resulting `.po'
5811 The functions are declared in the header file `<gettext-po.h>', and
5939 msgfmt [OPTION] FILENAME.po ...
5947 `FILENAME.po ...'
5952 searched relative to this list of directories. The resulting `.po'
6089 entry a check is performed. For example, the check will diagnose
6106 Verify presence and contents of the header entry. *Note Header
6108 entry.
6178 Uniforum style .po file.
6276 `--force-po'
6281 Write the .po file using indented style.
6342 The first two words serve the identification of the file. The magic
6364 file. The first table contains descriptors for the original strings,
6367 strings, and is parallel to the first table: to find the corresponding
6377 becomes the first in both the original and translated tables, making
6481 installer wishes to do so. So we perhaps should first take a look at
6561 The first parameter is this catalog descriptor. The second parameter
6705 Both take an additional argument at the first place, which
6964 After the first complaints from people internationalizing the code
7013 the numerical argument and the first string as a key, the implementation
7018 used and it is assumed that the first string argument is the singular
7093 the header entry of the PO file (the one with the empty `msgid' string).
7120 header entry would look like this:
7134 English is using. A header entry would look like this:
7161 Another language using the same header entry is:
7175 Exceptional case in the language family. The header entry would
7186 The header entry would be:
7196 The header entry would be:
7206 The header entry would be:
7217 The header entry would look like this:
7229 The header entry would look like this:
7241 The header entry would look like this:
7252 The header entry would look like this:
7264 The header entry would look like this:
7404 `N_' is a short form similar to `_'. The `Makefile' in the `po/'
7431 first appearance has to be translated to `"Anzahl"' and the second to
7449 `catgets' allows same original entry to have different translations,
7675 * Prioritizing messages:: How to find which messages to translate first
7873 ourselves first. Most probably that Linux International has some
8095 work this way. I first did all the things I'm responsible for. I've
8099 And when the first localized packages are released we'll get a lot of
8115 12.6 Prioritizing messages: How to determine which messages to translate first
8121 first that are the most visible to the user, or that occur most
8127 In a first step, she uses the programs like a user would do. While
8144 So, in the first step, the translator uses these commands on systems
8167 $ msguniq $HOME/gettextlogused > missing.po
8175 $ sed -n -e 's,^domain "\(.*\)"$,\1,p' < missing.po | sort | uniq
8185 She takes the latest copy of `$lang.po' from the Translation Project,
8186 or from the package (in most cases, `$package/po/$lang.po'), or creates
8187 a fresh one if she's the first translator (see *Note Creating::). She
8193 $ msggrep --domain=$domain missing.po | grep -v '^domain' \
8194 > $domain-missing.po
8195 $ msgattrib --set-obsolete --ignore-file $domain-missing.po $domain.$lang.po \
8196 > $domain.$lang-urgent.po
8198 The she translates `$domain.$lang-urgent.po' by use of a PO file
8205 $ msgmerge --no-fuzzy-matching $domain.$lang-urgent.po $package/po/$domain.pot \
8206 > $domain.$lang.po
8208 Then she can submit `$domain.$lang.po' and proceed to the next
8293 other packages first. Ensure that recent versions of GNU `m4',
8295 and if not, proceed to do this first. If you get to install these
8301 tool and the `Makefile's in the `intl/' and `po/' therefore know
8322 * Your `po/' directory should receive all PO files submitted to you
8323 by the translator teams, each having `LL.po' as a name. This is
8338 PO files in `po/' for distribution.
8370 the first time.
8452 2. A `po/' directory is created for eventually holding all
8454 `po/Makefile.in.in' from the GNU `gettext' distribution (beware
8456 the `po/' directory already exists, it will be preserved along
8464 first.
8487 GNU `gettext' facilities in one package go in `intl/', `po/' and `m4/'
8540 * po/POTFILES.in:: `POTFILES.in' in `po/'
8541 * po/LINGUAS:: `LINGUAS' in `po/'
8542 * po/Makevars:: `Makevars' in `po/'
8543 * po/Rules-*:: Extending `Makefile' in `po/'
8555 File: gettext.info, Node: po/POTFILES.in, Next: po/LINGUAS, Prev: Adjusting Files, Up: Adjustin…
8557 13.4.1 `POTFILES.in' in `po/'
8560 The `po/' directory should receive a file named `POTFILES.in'. This
8584 recommended to list in `po/POTFILES.in' the real source file (ending in
8589 File: gettext.info, Node: po/LINGUAS, Next: po/Makevars, Prev: po/POTFILES.in, Up: Adjusting Fi…
8591 13.4.2 `LINGUAS' in `po/'
8594 The `po/' directory should also receive a file named `LINGUAS'. This
8621 `po/' directory. You can copy them from GNU gettext's `po/' directory;
8625 File: gettext.info, Node: po/Makevars, Next: po/Rules-*, Prev: po/LINGUAS, Up: Adjusting Files
8627 13.4.3 `Makevars' in `po/'
8630 The `po/' directory also has a file named `Makevars'. It contains
8631 variables that are specific to your project. `po/Makevars' gets
8632 inserted into the `po/Makefile' when the latter is created. The
8636 The first three variables can be left unmodified if your package has
8637 a single message domain and, accordingly, a single `po/' directory.
8638 Only packages which have multiple `po/' directories at different
8639 locations need to adjust the three first variables defined in
8643 File: gettext.info, Node: po/Rules-*, Next: configure.in, Prev: po/Makevars, Up: Adjusting Files
8645 13.4.4 Extending `Makefile' in `po/'
8648 All files called `Rules-*' in the `po/' directory get appended to the
8649 `po/Makefile' when it is created. They present an opportunity to add
8651 with `po/Makefile.in.in'.
8654 building catalogs `en@quot.po' and `en@boldquot.po'. The effect of
8655 `en@quot.po' is that people who set their `LANGUAGE' environment
8659 catalog, simply add `en@quot' to the `po/LINGUAS' file. The effect of
8660 `en@boldquot.po' is that people who set `LANGUAGE' to `en@boldquot'
8664 similarly add `en@boldquot' to the `po/LINGUAS' file.
8672 File: gettext.info, Node: configure.in, Next: config.guess, Prev: po/Rules-*, Up: Adjusting Fil…
8720 AC_OUTPUT([EXISTING CONFIGURATION FILES intl/Makefile po/Makefile.in],
8723 The modification to the first argument to `AC_OUTPUT' asks for
8724 substitution in the `intl/' and `po/' directories. Note the `.in'
8725 suffix used for `po/' only. This is because the distributed file
8726 is really `po/Makefile.in.in'.
8802 `longdouble.m4', `longlong.m4', `nls.m4', `po.m4', `printf-posix.m4',
8807 `lib-ld.m4', `lib-link.m4', `lib-prefix.m4', `nls.m4', `po.m4',
8900 you also process the subdirectories `intl' and `po'. Special
8914 SUBDIRS = doc intl lib src po
8922 `po/Makefile' will later assume that the proper directory has been
9027 automatically generated from `Makefile.am', and the first three changes
9133 * AM_PO_SUBDIRS:: AM_PO_SUBDIRS in `po.m4'
9146 `po/' directories of the package for building.
9257 `AM_GNU_GETTEXT' macro, although invoked with the first argument
9269 13.5.5 AM_PO_SUBDIRS in `po.m4'
9272 The `AM_PO_SUBDIRS' macro prepares the `po/' directories of the package
9282 variables in each `po/' directory.
9392 `po/Makefile.in.in' autoinstalled by `gettextize' or `autopoint'.
9424 For the first and second approach, all files modified or brought in
9504 The name `autopoint' is an abbreviation of `auto-po-intl-m4'; the
9505 tool copies or updates mostly files in the `po', `intl', `m4'
9522 $ (cd po; make update-po)
9542 Internationalized packages have usually many `LL.po' files. Unless
9637 `po-mode.el'.
9992 `XGETTEXT_OPTIONS' variable in `po/Makevars' (*note po/Makevars::)
9997 `po/Makefile.in.in'. It is recommended to make one `xgettext'
10084 po-mode marking
10138 po-mode marking
10239 is first transformed into
10257 first argument and a newline, without interpreting backslashes in
10536 po-mode marking
10586 po-mode marking
10638 po-mode marking
10687 po-mode marking
10735 po-mode marking
10785 po-mode marking
10838 po-mode marking
10889 po-mode marking
11057 po-mode marking
11268 po-mode marking
11320 po-mode marking
11378 po-mode marking
11426 po-mode marking
11477 po-mode marking
11575 po-mode marking
11632 module `Locale::Messages' found first in the Perl include path exports a
11717 The first (singular) and the second (plural) argument will be
11722 The first (singular) and the second (plural) argument will be
11727 The first (singular) and the second (plural) argument will be
11986 the first place, and checked for invalid variable interpolation. The
12034 # Parentheses are only significant for the first argument.
12159 in `xgettext' to recognize the first one, and leave the other one alone.
12231 po-mode marking
12281 po-mode marking
12330 po-mode marking
12358 `pot', `po'
12425 folded into an official release. That first draft was full of
12448 project, and the switch from `glocale' to what was first named
12453 April 1995. The first official release of the package, including PO
12460 packages to `glocale' first, then later to `gettext', putting them in
12480 which is the first free C library with full internationalization
14459 [This is the first released version of the Lesser GPL. It also counts
14474 it too, but we suggest you first think carefully about whether this
15133 legibly, you should put the first ones listed (as many as fit
15526 * --force-po, msgattrib option: msgattrib Invocation.
15528 * --force-po, msgcat option: msgcat Invocation. (line 94)
15529 * --force-po, msgcomm option: msgcomm Invocation. (line 84)
15530 * --force-po, msgconv option: msgconv Invocation. (line 64)
15531 * --force-po, msgen option: msgen Invocation. (line 60)
15532 * --force-po, msgfilter option: msgfilter Invocation.
15534 * --force-po, msggrep option: msggrep Invocation. (line 143)
15535 * --force-po, msgmerge option: msgmerge Invocation. (line 129)
15536 * --force-po, msgunfmt option: msgunfmt Invocation. (line 108)
15537 * --force-po, msguniq option: msguniq Invocation. (line 81)
15538 * --force-po, xgettext option: xgettext Invocation. (line 265)
15807 * --use-first, msgcat option: msgcat Invocation. (line 90)
15808 * --use-first, msguniq option: msguniq Invocation. (line 77)
16106 * LANGUAGE, environment variable <1>: po/Rules-*. (line 11)
16152 * comment out PO file entry: Obsolete Entries. (line 47)
16155 * current entry of a PO file: Entry Positioning. (line 6)
16166 * find source fragment for a PO file entry: C Sources Context.
16202 * obsolete active entry: Obsolete Entries. (line 47)
16205 * po-auto-edit-with-msgid, PO Mode variable: Modifying Translations.
16207 * po-auto-fuzzy-on-edit, PO Mode variable: Translated Entries.
16209 * po-auto-select-on-unfuzzy, PO Mode variable: Fuzzy Entries. (line 44)
16210 * po-confirm-and-quit, PO Mode command: Main PO Commands. (line 62)
16211 * po-consider-as-auxiliary, PO Mode command: Auxiliary. (line 36)
16212 * po-consider-source-path, PO Mode command: C Sources Context.
16214 * po-current-entry, PO Mode command: Entry Positioning. (line 46)
16215 * po-cycle-auxiliary, PO Mode command: Auxiliary. (line 40)
16216 * po-cycle-source-reference, PO Mode command: C Sources Context.
16218 * po-edit-comment, PO Mode command: Modifying Comments. (line 46)
16219 * po-edit-msgstr, PO Mode command: Modifying Translations.
16221 * po-exchange-location, PO Mode command: Entry Positioning. (line 106)
16222 * po-fade-out-entry, PO Mode command <1>: Obsolete Entries. (line 47)
16223 * po-fade-out-entry, PO Mode command: Fuzzy Entries. (line 60)
16224 * po-first-entry, PO Mode command: Entry Positioning. (line 74)
16225 * po-help, PO Mode command: Main PO Commands. (line 83)
16226 * po-ignore-as-auxiliary, PO Mode command: Auxiliary. (line 36)
16227 * po-ignore-source-path, PO Mode command: C Sources Context. (line 89)
16228 * po-kill-comment, PO Mode command: Modifying Comments. (line 60)
16229 * po-kill-msgstr, PO Mode command <1>: Modifying Translations.
16231 * po-kill-msgstr, PO Mode command: Untranslated Entries.
16233 * po-kill-ring-save-comment, PO Mode command: Modifying Comments.
16235 * po-kill-ring-save-msgstr, PO Mode command: Modifying Translations.
16237 * po-last-entry, PO Mode command: Entry Positioning. (line 74)
16238 * po-mark-translatable, PO Mode command: Marking. (line 98)
16239 * po-msgid-to-msgstr, PO Mode command: Modifying Translations.
16241 * po-next-entry, PO Mode command: Entry Positioning. (line 69)
16242 * po-next-fuzzy-entry, PO Mode command: Fuzzy Entries. (line 39)
16243 * po-next-obsolete-entry, PO Mode command: Obsolete Entries. (line 36)
16244 * po-next-translated-entry, PO Mode command: Translated Entries.
16246 * po-next-untranslated-entry, PO Mode command: Untranslated Entries.
16248 * po-normalize, PO Mode command: Normalizing. (line 31)
16249 * po-other-window, PO Mode command: Main PO Commands. (line 72)
16250 * po-pop-location, PO Mode command: Entry Positioning. (line 92)
16251 * po-previous-entry, PO Mode command: Entry Positioning. (line 69)
16252 * po-previous-fuzzy-entry, PO Mode command: Fuzzy Entries. (line 39)
16253 * po-previous-obsolete-entry, PO Mode command: Obsolete Entries.
16255 * po-previous-translated-entry, PO Mode command: Translated Entries.
16257 * po-previous-untransted-entry, PO Mode command: Untranslated Entries.
16259 * po-push-location, PO Mode command: Entry Positioning. (line 92)
16260 * po-quit, PO Mode command: Main PO Commands. (line 62)
16261 * po-select-auxiliary, PO Mode command: Auxiliary. (line 49)
16262 * po-select-mark-and-mark, PO Mode command: Marking. (line 98)
16263 * po-select-source-reference, PO Mode command: C Sources Context.
16265 * po-statistics, PO Mode command: Main PO Commands. (line 87)
16266 * po-subedit-abort, PO Mode command: Subedit. (line 27)
16267 * po-subedit-cycle-auxiliary, PO Mode command: Subedit. (line 35)
16268 * po-subedit-exit, PO Mode command: Subedit. (line 20)
16269 * po-subedit-mode-hook, PO Mode variable: Modifying Comments. (line 57)
16270 * po-tags-search, PO Mode command: Marking. (line 56)
16271 * po-undo, PO Mode command: Main PO Commands. (line 53)
16272 * po-unfuzzy, PO Mode command: Fuzzy Entries. (line 44)
16273 * po-validate, PO Mode command: Main PO Commands. (line 92)
16274 * po-yank-comment, PO Mode command: Modifying Comments. (line 60)
16275 * po-yank-msgstr, PO Mode command: Modifying Translations.
16366 * attributes of a PO file entry: Fuzzy Entries. (line 6)
16482 * file format, .po: PO Files. (line 6)
16483 * files, .po and .mo: Files. (line 6)
16517 * header entry of a PO file: Header Entry. (line 6)
16559 * LINGUAS file: po/LINGUAS. (line 6)
16590 * Makefile.in.in extensions: po/Rules-*. (line 6)
16591 * Makevars file: po/Makevars. (line 6)
16719 * POTFILES.in file: po/POTFILES.in. (line 6)
16732 * quotation marks <1>: po/Rules-*. (line 11)
16773 * testing .po files for equivalence: xgettext Invocation. (line 317)
16906 Node: po/POTFILES.in344099
16907 Node: po/LINGUAS345345
16908 Node: po/Makevars347034
16909 Node: po/Rules-*347782