Projects/Summer of Code/2007/Projects/KAider/Introduction - Revision history

Mark Ziegler at 09:59, 30 December 2008

2008-12-30T09:59:03Z

Dhaumann at 17:51, 1 April 2008

2008-04-01T17:51:18Z

Shaforostoff at 08:37, 1 April 2008

2008-04-01T08:37:49Z

Shaforostoff at 08:35, 1 April 2008

2008-04-01T08:35:02Z

Shaforostoff: /* New Translator's Intro */

2008-01-11T19:35:10Z

‎New Translator's Intro

Shaforostoff: /* Glossary */

2007-09-01T14:17:38Z

‎Glossary

Shaforostoff: /* Performance */

2007-08-19T04:51:08Z

‎Performance

Shaforostoff: /* Project history */

2007-08-19T04:50:18Z

‎Project history

Shaforostoff: /* Project View */

2007-08-19T04:49:57Z

‎Project View

Shaforostoff: /* WebQuery */

2007-08-13T01:02:06Z

‎WebQuery

← Older revision		Revision as of 09:59, 30 December 2008
Line 1:		Line 1:
−	KAider was renamed to Lokalize. See also [http://docs.kde.org/development/en/kdesdk/lokalize/index.html official documentation @ docs.kde.org]. See also [[Projects/Summer_of_Code/2007/Projects/KAider#Compiling\|Compilation and setup instructions]]	+	KAider was renamed to [http://userbase.kde.org/Lokalize Lokalize]. See also [http://docs.kde.org/development/en/kdesdk/lokalize/index.html official documentation @ docs.kde.org]. See also [[Projects/Summer_of_Code/2007/Projects/KAider#Compiling\|Compilation and setup instructions]]

	==New Translator's Intro==		==New Translator's Intro==

← Older revision		Revision as of 17:51, 1 April 2008
Line 1:		Line 1:
−	KAider was renamed to Lokalize. See also [http://docs.kde.org/development/en/kdesdk/lokalize/index.html official documentation @ docs.kde.org]. See also [~~http://techbase.kde.org/index.php?title=~~Projects/Summer_of_Code/2007/Projects/KAider#Compiling Compilation and setup instructions]	+	KAider was renamed to Lokalize. See also [http://docs.kde.org/development/en/kdesdk/lokalize/index.html official documentation @ docs.kde.org]. See also [[Projects/Summer_of_Code/2007/Projects/KAider#Compiling\|Compilation and setup instructions]]

	==New Translator's Intro==		==New Translator's Intro==

← Older revision		Revision as of 08:37, 1 April 2008
Line 1:		Line 1:
−	KAider was renamed to Lokalize. See also [http://docs.kde.org/development/en/kdesdk/lokalize/index.html official documentation @ docs.kde.org]	+	KAider was renamed to Lokalize. See also [http://docs.kde.org/development/en/kdesdk/lokalize/index.html official documentation @ docs.kde.org]. See also [http://techbase.kde.org/index.php?title=Projects/Summer_of_Code/2007/Projects/KAider#Compiling Compilation and setup instructions]

	==New Translator's Intro==		==New Translator's Intro==

@@ Line 1: / Line 1: @@
 ==New Translator's Intro==
-When you start KAider with no arguments, you see two big multiline edits and a bunch of 'views'. They can be stacked (like tabs), shown separately or be hidden at all.
+When you start Lokalize with no arguments, you see two big multiline edits and a bunch of 'views'. They can be stacked (like tabs), shown separately or be hidden at all.
-Translation file consists of many pairs english-target strings (these pair are called 'messages'). They correspond to one separate string in user interface or one paragraph in documentation. KDE uses gettext .po file format.
+Translation file consists of many english-target pairs (these pairs are called 'messages'). They correspond to one separate string in user interface or one paragraph in documentation. KDE uses gettext .po file format.
 The purpose of first multiline edit is to display original part of the pair.
@@ Line 23: / Line 25: @@
 If the option is specified, it also saves previous string in comment field.
-So when KAider encounters this previous string in the translations (.po) file,
+So when Lokalize encounters this previous string in the translations (.po) file,
 it displays word-by-word difference betwen old and new strings.
 This enables translator to easily see what has changed and make the appropriate change in the translation.
@@ Line 30: / Line 32: @@
 I've implemented basic framework for translation projects.
 Currently it displays file tree with statistics like percentage of translated messages and last translator.
-It allows to open selected file in the current or in the new KAider window
+It allows to open selected file in the current or in the new Lokalize window
 (tip: use middle mouse button to open file in new window).
 Project file defines dir with translations, templates, glossary filename and list of webquery scripts. All paths contained in it are relative.
-Whenever KAider opens file and there is no project loaded, it will search for project file in file parent directories (up to 4).
+Whenever Lokalize opens file and there is no project loaded, it will search for project file in file parent directories (up to 4).
 ===Operations on multiple files===
-Currently Kaider supports only searching in multiple files.
+Currently Lokalize supports only searching in multiple files.
 Select items you are interested in, choose "find in files" from context menu.
-The first match will be displayed in usual KAider window. Proceed with F3 (find next). If you press F3 and there are no matches left in the current file, the search will continue in the next file and so on.
+The first match will be displayed in usual Lokalize window. Proceed with F3 (find next). If you press F3 and there are no matches left in the current file, the search will continue in the next file and so on.
-Ctrl+F in KAider editor window resets multiple files searching state.
+Ctrl+F in Lokalize editor window resets multiple files searching state.
 ==Merge Mode==
 It is one of things that are easy to implement but save tremendous amount of time for editors, particularly when two translators were working simultaneously on the same file.
-KAider allows quick navigation through messages that differ and (again) displays word-by-word difference.
+Lokalize allows quick navigation through messages that differ and (again) displays word-by-word difference.
 Open base file, then drop its changed version onto mergeview, and use ctrl+alt+pgdown/pgup to navigate through changed entries.
@@ Line 55: / Line 57: @@
 Now you will only have to find the (frequent) word sequence in the Glossary view and insert it by pressing a shortcut.
-Also, KAider has handy glossary editor with explicit search over the whole glossary
+Also, Lokalize has handy glossary editor with explicit search over the whole glossary
 ==WebQuery==
@@ Line 66: / Line 68: @@
 ==Performance==
-My measurings (ps aux) show that KAider consumes 20 to 35 mb of ram
+My measurings (ps aux) show that Lokalize consumes 20 to 35 mb of ram
 (kdelibs.po + project is loaded and all other views are shown).
-Remember that project and glossary can be shared between KAider windows.
+Remember that project and glossary can be shared between Lokalize windows.
 The speed of .po files parsing is 1mb per second on my 1.8Ghz Athlon XP (512 mb ram).

@@ Line 7: / Line 7: @@
 The purpose of second multiline edit is to display translation.
-You can navigate through 'messages' via Catalog Tree view or using PgDown and PgUp. By the way. It is important that you get used to using keyboard instead of menu and toolbars, because this will increase you productivity. For example, use Alt+<underscored letter> to switch between views when they are stacked into tabs, or Alt+Q to imitate pressing of 'Query' butten when WebQueries view is open.
+You can navigate through 'messages' via Catalog Tree view or using PgDown and PgUp. By the way. It is important that you get used to using keyboard instead of menu and toolbars, because this will increase you productivity. For example, use Alt+<underscored letter in the tab name> to switch between views when they are stacked into tabs, or Alt+Q to imitate pressing of 'Query' butten when WebQueries view is open.
 ==Project development history==

@@ Line 53: / Line 53: @@
 just because it would take more time to find its translation for copy-paste?
-Now you will only have to find the (frequent) sequence in the Glossary view and insert it by pressing a shortcut.
+Now you will only have to find the (frequent) word sequence in the Glossary view and insert it by pressing a shortcut.
 ==WebQuery==

@@ Line 9: / Line 9: @@
 You can navigate through 'messages' via Catalog Tree view or using PgDown and PgUp. By the way. It is important that you get used to using keyboard instead of menu and toolbars, because this will increase you productivity. For example, use Alt+<underscored letter> to switch between views when they are stacked into tabs, or Alt+Q to imitate pressing of 'Query' butten when WebQueries view is open.
-==Project history==
+==Project development history==
 I've started the project in January when my exams have finished and worked heavily on it almost two weeks.
 During this time I incorporated kbabel code dealing with translation file representation, parsing and saving (improving, refactoring, cleaning and fixing it along the way).