taskLinterna Mágica - Tasks: task #11056, Split translations in separate...


You are not allowed to post comments on this tracker with your current authentication level.

task #11056: Split translations in separate userscript files

Submitter:  Ivaylo Valkov <valkov>
Submitted:  Mon 04 Apr 2011 09:16:14 AM UTC
Should Start On:  Mon 04 Apr 2011 12:00:00 AM UTC Should be Finished on:  Mon 18 Apr 2011 12:00:00 AM UTC
Category:  Code and framework changes Priority:  5 - Normal
Status:  Done Privacy:  Public
Assigned to:  valkov Open/Closed:  Closed
Planned Release:  0.0.10

Wed 06 Apr 2011 12:03:13 PM UTC, comment #1: 

Finished in revision 34.

The @require tag in Greasemonkey is useless. It must be used with path/url to file.

With Greasemonkey (the actual extension) it is not straightforward to make script-to-script communication. The only way to expose data between scripts is trough variables in the page itself.

Ivaylo Valkov <valkov>
Group administrator
Mon 04 Apr 2011 09:16:14 AM UTC, original submission:  

The current framework makes all translations available to everyone. This increases the size of the userscript file. If new translations are made, the size will increase even more. Most people will not need most of the translations.

Every translation must be in separate file  that depends on the main userscript. This will be achieved by using the Greasemonkey @require tag. For browsers that do not support it, code in the main module will have to check for translation objects. It is best to not use code in the translation modules.

Each translation should have property that indicates the direction of the language (RTL/LTR). See bug #32740.

Ivaylo Valkov <valkov>
Group administrator


(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

No files currently attached


Depends on the following items: None found

Items that depend on this one: None found


Carbon-Copy List
  • -email is unavailable- added by valkov (Submitted the item)

    There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.


    Follow 2 latest changes.

    Date Changed by Updated Field Previous Value => Replaced by
    2011-04-06 valkov StatusIn Progress Done
        Open/ClosedOpen Closed

    Back to the top

    Powered by Savane 3.13-4b48.
    Corresponding source code