This app can Access all your files, peripheral devices, apps, programs and registry Access your Internet connection and act as a server. Access your home or work networks Access your Internet connection Use your video library Use data stored on an external storage device Use your pictures library Use your music library backgroundMediaPlayback Microsoft. Permissions info. Installation Get this app while signed in to your Microsoft account and install on up to ten Windows 10 devices.
Accessibility The product developer believes this product meets accessibility requirements, making it easier for everyone to use. Language supported English United States. Seizure warnings Photosensitive seizure warning.
Report this product Report this app to Microsoft Thanks for reporting your concern. Our team will review it and, if necessary, take action. Sign in to report this app to Microsoft. Report this app to Microsoft.
Report this app to Microsoft Potential violation Offensive content Child exploitation Malware or virus Privacy concerns Misleading app Poor performance. Download now. Related titles. Carousel Previous Carousel Next. Jump to Page. Search inside document. To List files. Praveen Kumar Vasari. Ishan Mahajan. Taushif Alim. Shahabaj Dange. Erian Mae N. Surjeet Singh Saran. Wawan Misbahul Anwar.
Ranadeep Bhattacahraya. Himanshu Bisht. Christopher Lambert. Jun C. Simmhadri Simmi. No Namee. Bharath Kaalai. Rana Abdul Rehman. Jabbar Baloghlanov. Miftahuz Zuhan. Reporting translation bugs to the programmer or maintainer of a package is not very useful, since the maintainer must never change a translation, except on behalf of the translator. Hence the translation bugs must be reported to the translators. Here is a way to organize this so that the maintainer does not need to forward translation bug reports, nor even keep a list of the addresses of the translators or their translation teams.
Every program has a place where is shows the bug report address. In this place, instruct the translator to add her own bug reporting address. For example, if that code has a statement. Should names of persons, cities, locations etc. People who only know languages that can be written with Latin letters English, Spanish, French, German, etc. However, in general when translating from one script to another, names are translated too, usually phonetically or by transliteration.
For example, Russian or Greek names are converted to the Latin alphabet when being translated to English, and English or French names are converted to the Katakana script when being translated to Japanese. This is necessary because the speakers of the target language in general cannot read the script the name is originally written in. As a programmer, you should therefore make sure that names are marked for translation, with a special comment telling the translators that it is a proper name and how to pronounce it.
In its simple form, it looks like this:. In this more comfortable form, it looks like this:. As a translator, you should use some care when translating names, because it is frustrating if people see their names mutilated or distorted. If your language uses the Latin script, all you need to do is to reproduce the name as perfectly as you can within the usual character set of your language. In this particular case, this means to provide a translation containing the c-cedilla character.
If the programmer used the simple case, you should still give, in parentheses, the original writing of the name — for the sake of the people that do read the Latin script. Here is an example, using Greek as the target script:. Because translation of names is such a sensitive domain, it is a good idea to test your translation before submitting it. When you are preparing a library, not a program, for the use of gettext , only a few details are different. Here we assume that the library has a translation domain and a POT file of its own.
If it uses the translation domain and POT file of the main program, then the previous sections apply without changes. The typical idiom used to achieve this is a static boolean variable that indicates whether the initialization function has been called.
Like this:. In other words, dgettext is used instead of gettext. Similarly, the dngettext function should be used in place of the ngettext function. After preparing the sources, the programmer creates a PO template file.
This section explains how to use xgettext for this purpose. You should then rename it to domainname. The answer is: for historical reasons. Up: Template [ Contents ][ Index ]. Read the names of the input files from file instead of getting them from the command line. Add directory to the list of directories. Source files are searched relative to this list of directories.
The resulting. Write output to specified file instead of name. Specifies the language of the input files. Specifies the encoding of the input files. This option is needed only if some untranslated message strings or their corresponding comments contain non-ASCII characters. Place comment blocks starting with tag and preceding keyword lines in the output file.
Without a tag , the option means to put all comment blocks preceding keyword lines in the output file. Note that comment blocks supposed to be extracted must be adjacent to keyword lines. For example, in the following C source code:.
The second comment line will not be extracted, because there is one blank line between the comment line and the keyword. The option has an effect on all input files. To enable or disable checks for a certain string, you can mark it with an xgettext: special comment in the source file.
The xgettext: comment can be followed by flags separated with a comma. If a flag is prefixed by no- , the meaning is negated. Some tests apply the checks to each sentence within the msgid, rather than the whole string. The number is specified with the --sentence-end option. Specify keywordspec as an additional keyword to be looked for.
Without a keywordspec , the option means to not use default keywords. If keywordspec is a C identifier id , xgettext looks for strings in the first argument of each call to the function or macro id. Note that when used through a normal shell command line, the double-quotes around the xcomment need to be escaped. The default keyword specifications, which are always looked for if not explicitly disabled, are language dependent.
They are:. Specifies additional flags for strings occurring as part of the arg th argument of the function word. The effect of this specification is that xgettext will mark as format strings all gettext invocations that occur as arg th argument of function. Use the flags c-format and possible-c-format to show who was responsible for marking a message as a format string.
The latter form is used if the xgettext program decided, the former form is used if the programmer prescribed it. By default only the c-format form is used. The translator should not have to care about these details. This implementation of xgettext is able to process a few awkward cases, like strings in preprocessor macros, ANSI concatenation of adjacent strings, and escaped end of lines for continued strings.
Specify whether or when to use colors and other text attributes. See The --color option for details. Specify the CSS style rule file to use for --color. See The --style option for details.
Write out a strict Uniforum conforming PO file. Write out a Java ResourceBundle in Java. Note that this is only effective with XML files. Set the output page width. Do not break long message lines. Message lines whose width exceeds the output page width will not be split into several lines. Only file reference lines which are wider than the output page width will be split. Generate sorted output. This is useful for testing purposes because it eliminates a source of variance for generated.
With --omit-header , two invocations of xgettext on the same files with the same options at different times are guaranteed to produce the same results.
Note that using this option will lead to an error if the resulting file would not entirely be in ASCII. Set the copyright holder in the output. Translators are expected to transfer or disclaim the copyright for their translations, so that package maintainers can distribute them without legal risk. If string is empty, the output files are marked as being in the public domain; in this case, the translators are expected to disclaim their copyright, again so that package maintainers can distribute them without legal risk.
The default value for string is the Free Software Foundation, Inc. Omit FSF copyright in output. It can be useful for packages outside the GNU project that want their translations to be in the public domain.
Set the package version in the header of the output. Set the reporting address for msgid bugs. This is the email address or URL to which the translators shall report bugs in the untranslated strings:. It can be your email address, or a mailing list address where translators can write to without being subscribed, or the URL of a web page through which the translators can contact you.
The default value is empty, which means that translators will be clueless! When starting a new translation, the translator creates a file called LANG. The alternative way is to do the copy and modifications by hand. To do so, the translator copies package. Then she modifies the initial comments and the header entry of this file. Here are more details.
The following header fields of a PO file are automatically filled, when possible. The value is guessed from the configure script or any other files in the current directory. These values are set according to the current locale and the predefined list of translation teams. These values are set according to the content of the POT file and the current locale. If no inputfile is given, the current directory is searched for the POT file. Assume the input file is a Java ResourceBundle in Java.
Set target locale. The optional part. Declares that the PO file will not have a human translator and is instead automatically generated. You should fill in the following fields. This is the name and version of the package. Fill it in if it has not already been filled in by xgettext. This has already been filled in by xgettext. It contains an email address or URL where you can report bugs in the untranslated strings:. It will be filled by the PO file editor when you save the file.
Fill in the English name of the language, and the email address or homepage URL of the language team you are part of. In the Free Translation Project, each translation team has its own mailing list. But there are three important differences:. In this case, ask your translation team which charset to use.
Because the PO files must be portable to operating systems with less advanced internationalization facilities, the character encodings that can be used are limited to those supported by both GNU libc and GNU libiconv. To enter such quote characters under X11, you can change your keyboard mapping using the xmodmap program.
The X11 names of the quote characters are "leftsinglequotemark", "rightsinglequotemark", "leftdoublequotemark", "rightdoublequotemark", "singlelowquotemark", "doublelowquotemark". The character encoding name can be written in either upper or lower case. Usually upper case is preferred.
This field is optional. It is only needed if the PO file has plural forms. The format of the plural forms field is described in Plural forms and Translating plural forms. Up: Updating [ Contents ][ Index ]. The msgmerge program merges two Uniforum style. The def. The ref. Where an exact match cannot be found, fuzzy matching is used to produce better results. Specify an additional library of message translations. See Compendium. This option may be specified more than once. Here are the values:.
Make numbered backups if numbered backups for this file already exist, otherwise make simple backups. Produce a PO file meant for msgfmt only, not for a translator. This option omits untranslated messages, fuzzy messages except the header entry , and obsolete messages from the output.
Do not use fuzzy matching when an exact match is not found. This may speed up the operation considerably. Assume the input files are Java ResourceBundles in Java. See Header Entry for the meaning of this field.
For those of you being the lucky users of Emacs, PO mode has been specifically created for providing a cozy environment for editing or modifying PO files. While editing a PO file, PO mode allows for the easy browsing of auxiliary and compendium PO files, as well as for following references into the set of C program sources from which PO files have been derived.
It has a few special features, among which are the interactive marking of program strings as translatable, and the validation of PO files with easy repositioning to PO file lines showing errors. For the beginning, besides main PO mode commands see Main PO Commands , you should know how to move between entries see Entry Positioning , and how to handle untranslated entries see Untranslated Entries.
To top off a comfortable installation, you might also want to make the PO mode available to your Emacs users. During the installation of the PO mode, you might want to modify your file.
Later, whenever you edit some. The string PO appears in the mode line for any buffer for which PO mode is active. Many PO files may be active at once in a single Emacs session. If you are using Emacs version 20 or newer, and have already installed the appropriate international fonts on your system, you may also tell Emacs how to determine automatically the coding system of every PO file.
This will often but not always cause the necessary fonts to be loaded and used for displaying the translations on your Emacs screen. For this to happen, add the lines:. If, with this, you still see boxes instead of international characters, try a different font set via Shift Mouse button 1. After setting up Emacs with something similar to the lines in Installation , PO mode is activated for a window when Emacs finds a PO file in that window. This puts the window read-only and establishes a po-mode-map, which is a genuine Emacs mode, in a way that is not derived from text mode in any way.
Functions found on po-mode-hook , if any, will be executed. The mode line also displays how many entries of each kind are held in the PO file.
Zero-coefficients items are not shown. The main PO commands are those which do not fit into the other categories of subsequent sections. These allow for quitting PO mode or for managing windows in special ways. For the purpose of undoing, each PO mode command is atomic. This is especially true for the RET command: the whole edition made by using a single use of this command is undone at once, even if the edition itself implied several actions.
However, while in the editing window, one can undo the edition work quite parsimoniously. The commands Q po-quit and q po-confirm-and-quit are used when the translator is done with the PO file. The former is a bit less verbose than the latter. If the file has been modified, it is saved to disk first. In both cases, and prior to all this, the commands check if any untranslated messages remain in the PO file and, if so, the translator is asked if she really wants to leave off working with this PO file.
This is the preferred way of getting rid of an Emacs PO file buffer. Merely killing it through the usual command C-x k kill-buffer is not the tidiest way to proceed. The command 0 po-other-window is another, softer way, to leave PO mode, temporarily. It just moves the cursor to some other Emacs window, and pops one if necessary. For example, if the translator just got PO mode to show some source context in some other, she might discover some apparent bug in the program source that needs correction.
This command allows the translator to change sex, become a programmer, and have the cursor right into the window containing the program she or rather he wants to modify. By later getting the cursor back in the PO file window, or by asking Emacs to edit this file once again, PO mode is then recovered. The command h po-help displays a summary of all available PO mode commands.
The translator should then type any character to resume normal PO mode operations. The command? The command V po-validate launches msgfmt in checking and verbose mode over the current PO file. This command first offers to save the current PO file on disk. The msgfmt tool, from GNU gettext , has the purpose of creating a MO file out of a PO file, and PO mode uses the features of this program for checking the overall format of a PO file, as well as all individual entries.
The program msgfmt runs asynchronously with Emacs, so the translator regains control immediately while her PO file is being studied. Once the cursor is on the line in error, the translator may decide on any PO mode action which would help correcting the error.
The cursor in a PO file window is almost always part of an entry. The only exceptions are the special case when the cursor is after the last entry in the file, or when the PO file is empty. The entry where the cursor is found to be is said to be the current entry. Many PO mode commands operate on the current entry, so moving the cursor does more than allowing the translator to browse the PO file, this also selects on which entry commands operate.
Some PO mode commands alter the position of the cursor in a specialized way. A few of those special purpose positioning are described here, the others are described in following sections for a complete list try C-h m :. Exchange the current entry location with the previously saved one po-exchange-location. Any Emacs command able to reposition the cursor may be used to select the current entry in PO mode, including commands which move by characters, lines, paragraphs, screens or pages, and search commands.
However, there is a kind of standard way to display the current entry in PO mode, which usual Emacs commands moving the cursor do not especially try to enforce. The command. It is yet to be decided if PO mode helps the translator, or otherwise irritates her, by forcing a rigid window disposition while she is doing her work. We originally had quite precise ideas about how windows should behave, but on the other hand, anyone used to Emacs is often happy to keep full control.
Maybe a fixed window disposition might be offered as a PO mode option that the translator might activate or deactivate at will, so it could be offered on an experimental basis. If nobody feels a real need for using it, or a compulsion for writing it, we should drop this whole idea. The incentive for doing it should come from translators rather than programmers, as opinions from an experienced translator are surely more worth to me than opinions from programmers thinking about how others should do translation.
The commands n po-next-entry and p po-previous-entry move the cursor the entry following, or preceding, the current one. If n is given while the cursor is on the last entry of the PO file, or if p is given while the cursor is on the first entry, no move is done. But even these commands will fail on a truly empty PO file. There are development plans for the PO mode for it to interactively fill an empty PO file from sources. See Marking. The translator may decide, before working at the translation of a particular entry, that she needs to browse the remainder of the PO file, maybe for finding the terminology or phraseology used in related entries.
She can of course use the standard Emacs idioms for saving the current cursor location in some register, and use that register for getting back, or else, use the location ring. PO mode offers another approach, by which cursor locations may be saved onto a special stack. The command m po-push-location merely adds the location of current entry to the stack, pushing the already saved locations under the new one.
The command r po-pop-location consumes the top stack element and repositions the cursor to the entry associated with that top element. This position is then lost, for the next r will move the cursor to the previously saved location, and so on until no locations remain on the stack. If the translator wants the position to be kept on the location stack, maybe for taking a look at the entry associated with the top element, then go elsewhere with the intent of getting back later, she ought to use m immediately after r.
The command x po-exchange-location simultaneously repositions the cursor to the entry associated with the top element of the stack of saved locations, and replaces that top element with the location of the current entry before the move. Consequently, repeating the x command toggles alternatively between two entries. For achieving this, the translator will position the cursor on the first entry, use m , then position to the second entry, and merely use x for making the switch.
There are many different ways for encoding a particular string into a PO file entry, because there are so many different ways to split and quote multi-line strings, and even, to represent special characters by backslashed escaped sequences. Some features of PO mode rely on the ability for PO mode to scan an already existing PO file for a particular string encoded into the msgid field of some entry. Even if PO mode has internally all the built-in machinery for implementing this recognition easily, doing it fast is technically difficult.
To facilitate a solution to this efficiency problem, we decided on a canonical representation for strings. A conventional representation of strings in a PO file is currently under discussion, and PO mode experiments with a canonical representation. Having both xgettext and PO mode converging towards a uniform way of representing equivalent strings would be useful, as the internal normalization needed by PO mode could be automatically satisfied when using xgettext from GNU gettext.
An explicit PO mode normalization should then be only necessary for PO files imported from elsewhere, or for when the convention itself evolves. So, for achieving normalization of at least the strings of a given PO file needing a canonical representation, the following PO mode command is available:.
The special command M-x po-normalize , which has no associated keys, revises all entries, ensuring that strings of both original and translated entries use uniform internal quoting in the PO file.
It also removes any crumb after the last entry. This command may be useful for PO files freshly imported from elsewhere, or if we ever improve on the canonical quoting format we use. This canonical format is not only meant for getting cleaner PO files, but also for greatly speeding up msgid string lookup for some other PO mode commands.
M-x po-normalize presently makes three passes over the entries. These heuristics may fail for comments not related to obsolete entries and ending with a backslash; they also depend on subsequent passes for finalizing the proper commenting of continued lines for obsolete entries.
This first pass might disappear once all oldish PO files would have been adjusted. The second and third pass normalize all msgid and msgstr strings respectively. Having such an explicit normalizing command allows for importing PO files from other sources, but also eases the evolution of the current convention, evolution driven mostly by aesthetic concerns, as of now. It is easy to make suggested adjustments at a later time, as the normalizing command and eventually, other GNU gettext tools should greatly automate conformance.
A description of the canonical string format is given below, for the particular benefit of those not having Emacs handy, and who would nevertheless want to handcraft their PO files in nice ways.
Right now, in PO mode, strings are single line or multi-line. So, we would have:. We are deliberately using a caricatural example, here, to make the point clearer. Usually, multi-lines are not that bad looking. It is probable that we will implement the following suggestion. There are a few yet undecided little points about string normalization, to be documented in this manual, once these questions settle.
Each PO file entry for which the msgstr field has been filled with a translation, and which is not marked as fuzzy see Fuzzy Entries , is said to be a translated entry. Only translated entries will later be compiled by GNU msgfmt and become usable in programs. Other entry types will be excluded; translation will not occur for them.
The commands t po-next-translated-entry and T po-previous-translated-entry move forwards or backwards, chasing for an translated entry. If none is found, the search is extended and wraps around in the PO file buffer. Translated entries usually result from the translator having edited in a translation for them, Modifying Translations. However, if the variable po-auto-fuzzy-on-edit is not nil , the entry having received a new translation first becomes a fuzzy entry, which ought to be later unfuzzied before becoming an official, genuine translated entry.
Each PO file entry may have a set of attributes , which are qualities given a name and explicitly associated with the translation, using a special system comment. One of these attributes has the name fuzzy , and entries having this attribute are said to have a fuzzy translation.
They are called fuzzy entries, for short. Fuzzy entries, even if they account for translated entries for most other purposes, usually call for revision by the translator. Those may be produced by applying the program msgmerge to update an older translated PO files according to a new PO template file, when this tool hypothesises that some new msgid has been modified only slightly out of an older one, and chooses to pair what it thinks to be the old translation for the new modified entry.
The slight alteration in the original string the msgid string should often be reflected in the translated string, and this requires the intervention of the translator. For this reason, msgmerge might mark some entries as being fuzzy.
Also, the translator may decide herself to mark an entry as fuzzy for her own convenience, when she wants to remember that the entry has to be later revisited. So, some commands are more specifically related to fuzzy entry processing. The commands f po-next-fuzzy-entry and F po-previous-fuzzy-entry move forwards or backwards, chasing for a fuzzy entry. The command TAB po-unfuzzy removes the fuzzy attribute associated with an entry, usually leaving it translated.
Further, if the variable po-auto-select-on-unfuzzy has not the nil value, the TAB command will automatically chase for another interesting entry to work on. The initial value of po-auto-select-on-unfuzzy is nil. The initial value of po-auto-fuzzy-on-edit is nil. However, if the variable po-auto-fuzzy-on-edit is set to t , any entry edited through the RET command is marked fuzzy, as a way to ensure some kind of double check, later. In this case, the usual paradigm is that an entry becomes fuzzy if not already whenever the translator modifies it.
If she is satisfied with the translation, she then uses TAB to pick another entry to work on, clearing the fuzzy attribute on the same blow. If she is not satisfied yet, she merely uses SPC to chase another entry, leaving the entry fuzzy. The translator may also use the DEL command po-fade-out-entry over any translated entry to mark it as being fuzzy, when she wants to easily leave a trace she wants to later return working at this entry.
Also, when time comes to quit working on a PO file buffer with the q command, the translator is asked for confirmation, if fuzzy string still exists. When xgettext originally creates a PO file, unless told otherwise, it initializes the msgid field with the untranslated string, and leaves the msgstr string to be empty.
Such entries, having an empty translation, are said to be untranslated entries. Later, when the programmer slightly modifies some string right in the program, this change is later reflected in the PO file by the appearance of a new untranslated entry for the modified string. The usual commands moving from entry to entry consider untranslated entries on the same level as active entries.
The work of the translator might be quite naively seen as the process of seeking for an untranslated entry, editing a translation for it, and repeating these actions until no untranslated entries remain. Some commands are more specifically related to untranslated entry processing.
The commands u po-next-untranslated-entry and U po-previous-untransted-entry move forwards or backwards, chasing for an untranslated entry. An entry can be turned back into an untranslated entry by merely emptying its translation, using the command k po-kill-msgstr. See Modifying Translations. Also, when time comes to quit working on a PO file buffer with the q command, the translator is asked for confirmation, if some untranslated string still exists.
By obsolete PO file entries, we mean those entries which are commented out, usually by msgmerge when it found that the translation is not needed anymore by the package being localized. The usual commands moving from entry to entry consider obsolete entries on the same level as active entries.
Obsolete entries are easily recognizable by the fact that all their lines start with , even those lines containing msgid or msgstr. Commands exist for emptying the translation or reinitializing it to the original untranslated string.
Commands interfacing with the kill ring may force some previously saved text into the translation. The user may interactively edit the translation. All these commands may apply to obsolete entries, carefully leaving the entry obsolete after the fact.
The commands o po-next-obsolete-entry and O po-previous-obsolete-entry move forwards or backwards, chasing for an obsolete entry. PO mode does not provide ways for un-commenting an obsolete entry and making it active, because this would reintroduce an original untranslated string which does not correspond to any marked string in the program sources. This goes with the philosophy of never introducing useless msgid values.
However, it is possible to comment out an active entry, so making it obsolete. GNU gettext utilities will later react to the disappearance of a translation by using the untranslated string. The command DEL po-fade-out-entry pushes the current entry a little further towards annihilation.
If the entry is active it is a translated entry , then it is first made fuzzy. If it is already fuzzy, then the entry is merely commented out, with confirmation. If the entry is already obsolete, then it is completely deleted from the PO file. It is easy to recycle the translation so deleted into some other PO file entry, usually one which is untranslated. Here is a quite interesting problem to solve for later development of PO mode, for those nights you are not sleepy. The idea would be that PO mode might become bright enough, one of these days, to make good guesses at retrieving the most probable candidate, among all obsolete entries, for initializing the translation of a newly appeared string.
I think it might be a quite hard problem to do this algorithmically, as we have to develop good and efficient measures of string similarity. Right now, PO mode completely lets the decision to the translator, when the time comes to find the adequate obsolete translation, it merely tries to provide handy tools for helping her to do so.
By doing so, it pretends helping the translator to avoid little clerical errors about the overall file format, or the proper quoting of strings, as those errors would be easily made.
Other kinds of errors are still possible, but some may be caught and diagnosed by the batch validation process, which the translator may always trigger by the V command. For all other errors, the translator has to rely on her own judgment, and also on the linguistic reports submitted to her by the users of the translated package, having the same mother tongue. When the time comes to create a translation, correct an error diagnosed mechanically or reported by a user, the translators have to resort to using the following commands for modifying the translations.
Reinitialize the translation with the original, untranslated string po-msgid-to-msgstr. Save the translation on the kill ring, without deleting it po-kill-ring-save-msgstr. The command RET po-edit-msgstr opens a new Emacs window meant to edit in a new translation, or to modify an already existing translation.
The new window contains a copy of the translation taken from the current PO file entry, all ready for edition, expunged of all quoting marks, fully modifiable and with the complete extent of Emacs modifying commands. When the translator is done with her modifications, she may use C-c C-c to close the subedit window with the automatically requoted results, or C-c C-k to abort her modifications.
0コメント