The branch, master, has been updated.
- Log -----------------------------------------------------------------
commit 1bcf8192769e27099802e4311c002d6eb81adbfc
Author: Scott Kostyshak <skost...@lyx.org>
Date: Tue Jan 29 23:23:28 2013 -0500
README.localization: typos and grammar
diff --git a/README.localization b/README.localization
index c0e1a03..52280f9 100644
--- a/README.localization
+++ b/README.localization
@@ -16,7 +16,7 @@ and dialog items, console messages) into their native
language.
1) WHERE DO I START?
The file you need to edit is an xx.po file where xx stands for your language's
-two letter code. For a list of languages codes look at:
+two letter code. For a list of language codes look at:
http://www.gnu.org/software/gettext/manual/html_mono/gettext.html#Language-Codes
@@ -27,15 +27,15 @@ the compilation.
There are basically two source trees you can start to work with - trunk
(development version) and branch (stable version). Unless the development
-version is shortly before release it is better idea to start your translating
+version is shortly before release it is better to start your translating
work on the stable version. If you have no idea how to get those trees you
can follow http://www.lyx.org/HowToUseGIT page.
2) HOW DO I EDIT PO FILES?
-PO files can be edited with every text editor available for your system (e.g.
-VIM, NotePad etc.). Yet another option is to use a specialized editor for .po
+PO files can be edited with any text editor available for your system (e.g.
+Vim, NotePad etc.). Yet another option is to use a specialized editor for .po
files. You can e.g. use the editors "poEdit" or "jEdit", Linux users can
additionally use e.g. "kbabel". Using these editors usually makes things
easier
as they have many tools to assist the translator.
@@ -47,8 +47,8 @@ If you are using a simple text editor you should translate
the strings that
appear in the msgid line and write the translation into the msgstr line. Note
that a "#, fuzzy" line is just a hint for translation from compiler - in order
to get the translation of the current item working you have to delete this
-line. It is recommended that you would take a look at another .po file - that
-way you can get an idea of what to do. If you are using a specialized po editor
+line. It is recommended that you take a look at another .po file - that way you
+can get an idea of what to do. If you are using a specialized po editor
then you will see in it the untranslated strings and a place to write your
translation for them.
@@ -63,7 +63,7 @@ invent your own working shortcuts for dialog and menu entries
and resolve
possible conflicts of the same shortcut chars in one menu...
Note also that there are already used global shortcuts (such as p k x c m s a)
-and you should avoid to use these characters for first-level menu shortcuts.
+and you should avoid using these characters for first-level menu shortcuts.
'$' and '%' are usually used as handlers for formatting or variables to be
inserted into the strings. Character sequences like %1$s or %1$d MUST also
@@ -71,10 +71,10 @@ appear in your translations! Please take them exactly as
they are or you may
experience crashes when running LyX.
[[Context]] is used to distinguish otherwise identical strings, which could
-have different translation dependent on the Context. [[Context]] appears only
+have different translations depending on the Context. [[Context]] appears only
in msgid string and should not be repeated in the translated version.
-{} refer to counters and must not be translated. Example would be:
+{} refer to counters and must not be translated. An example would be:
msgid "Algorithm \\arabic{theorem}"
msgstr "Algoritmus \\arabic{theorem}"
@@ -82,8 +82,8 @@ msgstr "Algoritmus \\arabic{theorem}"
5) WHAT IS pocheck.pl AND HOW DO I USE IT?
This is a small script located in the "po" directory of the source that helps
-you find common errors in your translation. In order to use this script you
have
-to have the script language Perl installed.
+you find common errors in your translation. In order to use this script you
+need the script language Perl installed.
Run ./pocheck.pl -h to see all possible switches.
@@ -104,8 +104,8 @@ e.g., Czech, the code is "cs_CZ".
The most comfortable way to see your updated translation while editing, is
running (in linux):
1. "make xx.gmo" in the po directory to compile updated xx.po translation
-2. "make install" in root lyx tree to copy xx.gmo into the appropriate location
- (or do it by hand...)
+2. "make install" in root lyx tree to copy xx.gmo to the appropriate location
+ (or do it by hand...)
For advanced users - if you want to remerge your files against current source
files run make update-po.
@@ -128,18 +128,19 @@ new strings appear, no other function.
9) REFERENCES
-For some basic idea on how the translation works, you can look at
+For a basic idea of how the translation works, you can look at
http://en.wikipedia.org/wiki/Gettext
-For detailed reference (including full list of country and language codes),
-have a look at
+For detailed reference (including a full list of country and language codes),
+have a look at
http://www.gnu.org/software/gettext/manual/gettext.html
-Consider subscribing to the documentation list at lyx-d...@lists.lyx.org
(rather
-silent one) or developer's mailing list lyx-de...@lists.lyx.org (high volume).
+Consider subscribing to the documentation list, lyx-d...@lists.lyx.org (rather
+silent), or the developer's mailing list, lyx-de...@lists.lyx.org (high
+volume).
@@ -149,25 +150,26 @@ PART II - Translation of Math environments and Floats in
the final output
As of 2.0 LyX allows automatic translation in tex/dvi/ps/pdf output for math
environment strings (and some floats) which are not automatically translated
via
babel package to the localized form. For example the environment "Exercise"
-becomes "Aufgabe" in the output of the documents with language set to german.
+becomes "Aufgabe" in the output of the documents with language set to German.
These translations are taken from the previously translated .po file before the
final major LyX release (e.g. 2.0.0) and are fixed for all next minor releases
(e.g. 2.0.x) in order to have fixed output of LyX documents.
-The current translation for your language can be found in
lib/layouttranslations
-file. Easy way to check many of the translation is to simply load
-lib/examples/localization_test.lyx in LyX and read its instructions.
+The current translation for your language can be found in the file
+lib/layouttranslations. An easy way to check many of the translations is to
+simply load lib/examples/localization_test.lyx in LyX and read its
+instructions.
The problematic strings can be then fixed in the .po file. For inspiration the
typical places in .po files, where to fix the translation, can be seen on the
-following commit: http://www.lyx.org/trac/changeset/38169 .
+following commit: http://www.lyx.org/trac/changeset/38169.
-If you need to manually regenerate layouttranslations file from .po files run
-`make ../lib/layouttranslations' in po directory. Python polib library is
-needed for building the output file.
+If you need to manually regenerate the layouttranslations file from .po files
+run `make ../lib/layouttranslations' in the po directory. The Python polib
+library is needed for building the output file.
-Q: Running make ../lib/layouttranslations return with just saying
+Q: Running make ../lib/layouttranslations returns with just saying
../lib/layouttranslations is up to date.
A: To force regerenation, use something like (XX is your language)
make -W XX.po ../lib/layouttranslations
commit 66dcc7f62c1e6c9ff0d4e55c6c13e3fbbf806bc6
Author: Scott Kostyshak <skost...@lyx.org>
Date: Tue Jan 29 22:36:48 2013 -0500
INSTALL: typos and grammar
diff --git a/INSTALL b/INSTALL
index 7ff59da..7ed8b1b 100644
--- a/INSTALL
+++ b/INSTALL
@@ -18,7 +18,7 @@ These four steps will compile, test and install LyX:
(for example, "--with-qt4-dir=/usr/share/qt4/") if the
environment variable QTDIR is not set and pkg-config is not
available.
-
+
See Note below if ./configure script is not present.
2) make
@@ -48,10 +48,10 @@ You will also probably need GNU m4 (perhaps installed as
gm4).
Requirements
------------
-First of all, you will also need a recent C++ compiler, where recent
-means that the compilers are close to C++ standard conforming (gcc 4.x).
+First of all, you will need a recent C++ compiler, where recent means
+that the compilers are close to C++ standard conforming (gcc 4.x).
-LyX makes great use of C++ Standard Template Library (STL).
+LyX makes great use of the C++ Standard Template Library (STL).
This means that gcc users will have to install the relevant libstdc++
library to be able to compile this version of LyX.
@@ -112,7 +112,7 @@ flags:
debug X X X X
gprof X
- The default are as follows in terms of version number
+ The defaults are as follows in terms of version number
release: stable release (1.x.y)
prerelease: version number contains alpha, beta, rc or pre.
development: version number contains dev.
@@ -150,7 +150,7 @@ There are also flags to control the internationalization
support in
LyX:
o --disable-nls suppresses all internationalization support,
- yielding a somewhat smaller code.
+ yielding somewhat smaller code.
o --with-included-gettext forces the use of the included GNU gettext
library, although you might have another one installed.
@@ -160,7 +160,7 @@ LyX:
care.
o You can also set the environment variable LINGUAS to a list of
- language in case you do not want to install all the translation
+ languages in case you do not want to install all the translation
files. For example, if you are only interested in German and
Finnish, you can type (with sh or bash)
export LINGUAS='de fi'
@@ -188,7 +188,7 @@ Moreover, the following generic configure flags may be
useful:
surprises.
Note that the --with-extra-* commands are not really robust when it
-comes to use of relative paths. If you really want to use a relative path
+comes to using relative paths. If you really want to use a relative path
here, you can prepend it with "`pwd`/".
If you do not like the default compile flags used (-g -O2 on gcc), you can
@@ -197,20 +197,20 @@ set CXXFLAGS variable to other values as follows:
o CXXFLAGS='-O2' (sh, bash)
o setenv CXXFLAGS '-O2' (csh, tcsh)
-Similarly, if you want to force the use of some specific compiler, you can
+Similarly, if you want to force the use of a specific compiler, you can
give a value to the CXX variable.
If you encounter problems, please read the section 'Problems' at the end of
this file.
-The following options allow to tweak more precisely the generated code:
+The following options allow you to tweak the generated code more precisely:
o --enable-gprof instruments the code for use with the gprof
- profiler. The result are only meaningful in conjunction with
+ profiler. The results are only meaningful in conjunction with
--enable-build-type=release.
o --enable-optimization=VALUE enables you to set optimization to a
- higher level as the default (-O), for example --enable-optimization=-O3.
+ higher level than the default (-O), for example --enable-optimization=-O3.
o --disable-optimization - you can use this to disable compiler
optimization of LyX. The compile may be much quicker with some
@@ -276,7 +276,7 @@ that can be used to display lyx-documents in filemanagers.
If configure fails for some strange reason
------------------------------------------
-Even when configure fails, it creates a Makefile. You always can check
+Even when configure fails, it creates a Makefile. You can always check
the contents of this file, modify it and run 'make'.
Compiling For Multiple Architectures
@@ -300,8 +300,8 @@ Problems
--------
This section provides several hints that have been submitted by LyX
-team member or users to help compiling on some particular
-architectures. If you find that some of this hints are wrong, please
+team members or users to help compiling on some particular
+architectures. If you find that some of these hints are wrong, please
notify us.
o On SUN Sparc Solaris, you need gnumake. The LyX makefiles do not
@@ -338,7 +338,7 @@ notify us.
to either ~/.fonts.conf (for a per-user change) or /etc/fonts/local.conf
(for a global system change). The stanza should be added between the
<fontconfig> and </fontconfig> tags. If neither ~/.fonts.conf nor
- /etc/fonts/local.conf exist, you can create them with the following
+ /etc/fonts/local.conf exists, you can create them with the following
content:
<?xml version="1.0"?>
-----------------------------------------------------------------------
Summary of changes:
INSTALL | 32 ++++++++++++++--------------
README.localization | 56 ++++++++++++++++++++++++++------------------------
2 files changed, 45 insertions(+), 43 deletions(-)
hooks/post-receive
--
The LyX Source Repository
