CKLangTool should sort language entries

[Wiktor Walc]

(as the title says)

[Wiktor Walc]

• test_assets.zip - just in case anyone had problems with creating Arabic files using this patch.
• langtool.jar - compiled version added for easier testing

Few words about new patch..

Previously en.js was used as a template, all language files were constructed just like the English translation, including spacing (tabs, multiple spaces, new lines etc.).

In the new CKLangTool version also the English file is modified. It means that is no longer used as a template (per se), but only as a source of language entries.

Inline and block comments are detected and assigned to the nearest language entry. It means that in current en.js file, the following part of file:

	// Toolbar buttons without dialogs.
	source			: 'Source',
	newPage			: 'New Page',
	save			: 'Save',
	preview			: 'Preview',

will be changed into:

	newPage			: 'New Page',
	preview			: 'Preview',
	save			: 'Save',
	// Toolbar buttons without dialogs.
	source			: 'Source',

so be careful when adding comments.

As a result of sorting, note that two special entries in language files:

	/**
	 * The language reading direction. Possible values are "rtl" for
	 * Right-To-Left languages (like Arabic) and "ltr" for Left-To-Right
	 * languages (like English).
	 * @default 'ltr'
	 */
	dir : 'ltr',

	/*
	 * Screenreader titles. Please note that screenreaders are not always capable
	 * of reading non-English words. So be careful while translating it.
	 */
	editorTitle		: 'Rich text editor, %1',

are sorted just like the other entries and are no longer at the top.

[Frederico Caldeira Knabben]

I'm afraid we have a big misunderstanding here. I think the ticket has been originally created for a very small thing, to have the _translationstatus.txt file entries ordered alphabetically, so we avoid changes like this: [4564/CKEditor/trunk/_source/lang/_translationstatus.txt].

The feature that's being proposed instead is about the entries in the files, which is definitely something not to be done. The entries in the en.js file are added in a certain logical order and that order must not change. For example, we leave "width" and "height" together because they refer to the same kind of thing... dialog titles are in the beginning of their lang blocks, etc.

All this shows us that "(as the title says)" is something really bad to have in the ticket description.

[Wiktor Walc]

The attached patch contains code that sorts lines with translation status before saving them to _translationstatus.txt.

[Wiktor Walc]

Fixed with [4660].