Jump to content


Important Announcement!

Please read this post

Photo

Private Tab - Ver. 0.2.0


  • Please log in to reply
16 replies to this topic

#1 Infocatcher

Infocatcher

    Member

  • Members
  • 11 posts


  • Translator for [No translator]
  • Extension Developer: Yes
  • Extensions: Private Tab
  • My OS Windows

Posted 23 May 2013 - 10:28 AM

Maintainer: Infocatcher
Creator: Infocatcher

Ext. Version: 0.2.0
Release date: 2016-08-25
Description: Adds private tabs
Extension is compatible to: ( sm.png 2.17 - 2.48a1) ( ff.png 20.0 - 51.0a1)

Included locales: ar ca de el en-US es et fi fr hu id it ja pl pt-BR pt-PT ru sr sv-SE tr uk vi zh-CN zh-TW

View on WTS -- Download the extension


Edited by Infocatcher, 25 August 2016 - 07:51 PM.


#2 Grg68

Grg68

    Advanced Member

  • Members
  • 67 posts
  • Gender:Male
  • Location:Hellas, Island of Crete - Chania
  • Interests:electronics, mechanics, computers


  • Translator for Greek (el)
  • Extension Developer: Yes
  • Extensions: Restart manager
  • Translation Credits to George Malamas
  • My OS Several

Posted 24 May 2013 - 03:25 AM

Hi Infocatcher,

Welcome to BabelZilla..! welcomeani.gif

I already have updated my locale, adapting it on
the new feature you implemented recently, to distinct
singular/plural on disable/uninstall messages.
Actually, this feature makes the related dialogs to
appear natural now.
In my language at least, this is important and makes
good sense to the user.

So, thanks for your efforts to make this project even better
at all! wink.gif

Question: On WTS, in <em:localized> section, why
you include the "creator" item? You wish your name to be
translated!..? tongue.gif

Grg

#3 Infocatcher

Infocatcher

    Member

  • Members
  • 11 posts


  • Translator for [No translator]
  • Extension Developer: Yes
  • Extensions: Private Tab
  • My OS Windows

Posted 24 May 2013 - 07:04 AM

QUOTE (Grg68 @ May 24 2013, 03:25) <{POST_SNAPBACK}>
Welcome to BabelZilla..! welcomeani.gif
Thanks. smile.gif

QUOTE (Grg68 @ May 24 2013, 03:25) <{POST_SNAPBACK}>
I already have updated my locale [...]
Thanks, updated.

QUOTE (Grg68 @ May 24 2013, 03:25) <{POST_SNAPBACK}>
Question: On WTS, in <em:localized> section, why
you include the "creator" item? You wish your name to be
translated!..? tongue.gif
Interesting, works for "global" <em:creator>, but not for <em:developer> or <em:contributor>.
This is strange and unfortunately looks not documented. mellow.gif

#4 Grg68

Grg68

    Advanced Member

  • Members
  • 67 posts
  • Gender:Male
  • Location:Hellas, Island of Crete - Chania
  • Interests:electronics, mechanics, computers


  • Translator for Greek (el)
  • Extension Developer: Yes
  • Extensions: Restart manager
  • Translation Credits to George Malamas
  • My OS Several

Posted 25 May 2013 - 12:23 AM

Hi Infocatcher,
QUOTE (Infocatcher @ May 24 2013, 09:04) <{POST_SNAPBACK}>
Interesting, works for "global" <em:creator>...

I think i have the answer.
This is not related to Private Tab and so it's out of the current
topic.
If you wish to know what i have to say, please read the text
in the attachment.

Thanks

Attached Files


Grg

#5 Infocatcher

Infocatcher

    Member

  • Members
  • 11 posts


  • Translator for [No translator]
  • Extension Developer: Yes
  • Extensions: Private Tab
  • My OS Windows

Posted 28 May 2013 - 04:41 PM

QUOTE (Grg68 @ May 25 2013, 03:23) <{POST_SNAPBACK}>
If you wish to know what i have to say, please read the text
in the attachment.
Thanks, I read some time ago, but did some tests only now. You are right about data from AMO. And also I noticed that this data is stored in %profile%/addons.sqlite file, but isn't updated automatically (or updated very rarely) – only after extensions updates (and only for updated extensions).

And about Private Tab. smile.gif
Global <em:creator> isn't used for new installed extension, if browser can't receive data from AMO.
So it's better to leave it in each <em:localized> block.

#6 Grg68

Grg68

    Advanced Member

  • Members
  • 67 posts
  • Gender:Male
  • Location:Hellas, Island of Crete - Chania
  • Interests:electronics, mechanics, computers


  • Translator for Greek (el)
  • Extension Developer: Yes
  • Extensions: Restart manager
  • Translation Credits to George Malamas
  • My OS Several

Posted 28 May 2013 - 09:13 PM

Hi Infocatcher,
QUOTE (Infocatcher @ May 28 2013, 18:41) <{POST_SNAPBACK}>
Global <em:creator> isn't used for new installed extension, if browser...
I know it, probably i was not so clear previously.
Creator's name should be appear of course in extension's "About",
even when the extension has been localized.
In my first post here i meant that, if a name is not localizable, e.g.
because it's a nickname in English, then it's not necessary the "<em:creator>"
item to be included among the items to be localized, on WTS.
You can just put it in every "<em:localized>" section in your install.rdf,
letting only the localizable items to be managed by the translators, putting
them on WTS.
For more documented details, you may be interested to take a look here and here
and then consider which of them can be eligible to be localized and
put them on WTS.
In my opinion, the most common localizable entries in "<em:localized>" section,
are the extension's name ("<em:name>", if applicable, depending of the locale),
"<em:description>", "<em:translator>" and maybe "<em:contributor>".

Grg

#7 Infocatcher

Infocatcher

    Member

  • Members
  • 11 posts


  • Translator for [No translator]
  • Extension Developer: Yes
  • Extensions: Private Tab
  • My OS Windows

Posted 29 May 2013 - 06:42 AM

QUOTE (Grg68 @ May 29 2013, 00:13) <{POST_SNAPBACK}>
... then it's not necessary the "<em:creator>"
item to be included among the items to be localized, on WTS.
Yes, I understood this "side", but I'm too lazy to edit extension before each uploading to WTS...
And the same with not yet localized strings in English: it's easy to remove them, but take some time.
And since I don't have much free time, I prefer to do something more useful (in my opinion, of course) first (or instead).

QUOTE (Grg68 @ May 29 2013, 00:13) <{POST_SNAPBACK}>
For more documented details, you may be interested to take a look here and here
and then consider which of them can be eligible to be localized and
put them on WTS.
Thanks, I know about extensions.EXTENSION_ID.* preferences (and use them in some other extensions), but them are obsolete for now. smile.gif
About localization of AMO descriptions. Is here a way to update AMO "automatically" (to just approve new translations for example)? Because I sometimes see obsolete localized descriptions and I'm don't like this.
Anyway, I'm not sure about release notes – I'm (generally) just write them before release on AMO.
And I should probably wrote more detailed description first. unsure.gif

#8 DakSrbija

DakSrbija

    Advanced Member

  • BabelZillian Mods
  • 422 posts
  • Gender:Male
  • Location:Republic of Srpska


  • Translator for Serbian (sr)
  • Extension Developer: No
  • Translation Credits to ДакСРБИЈА
  • My OS Windows

Posted 03 June 2013 - 05:00 PM

Serbian (sr) localization has been released.

#9 Infocatcher

Infocatcher

    Member

  • Members
  • 11 posts


  • Translator for [No translator]
  • Extension Developer: Yes
  • Extensions: Private Tab
  • My OS Windows

Posted 04 June 2013 - 09:28 AM

QUOTE (DakSrbija @ Jun 3 2013, 20:00) <{POST_SNAPBACK}>
Serbian (sr) localization has been released.

Thanks, updated.

#10 Infocatcher

Infocatcher

    Member

  • Members
  • 11 posts


  • Translator for [No translator]
  • Extension Developer: Yes
  • Extensions: Private Tab
  • My OS Windows

Posted 16 September 2013 - 02:11 PM

About new strings: https://github.com/I...omment-24412217

#11 Infocatcher

Infocatcher

    Member

  • Members
  • 11 posts


  • Translator for [No translator]
  • Extension Developer: Yes
  • Extensions: Private Tab
  • My OS Windows

Posted 26 March 2014 - 08:36 PM

About new "buttonTipTemplate" string: https://github.com/I...omment-38728692

#12 Infocatcher

Infocatcher

    Member

  • Members
  • 11 posts


  • Translator for [No translator]
  • Extension Developer: Yes
  • Extensions: Private Tab
  • My OS Windows

Posted 04 May 2014 - 09:37 PM

About new "openNewPrivateTabShortInAustralis" string: https://github.com/I...omment-42143903

#13 alfapegasi

alfapegasi

    Advanced Member

  • Members
  • 112 posts
  • Gender:Male
  • Location:Ankara, Turkey


  • Translator for Turkish (tr)
  • Extension Developer: No
  • Translation Credits to Sinan Kaan Yerli (skyerli.org)

Posted 11 May 2014 - 05:35 AM

tr is released

cheers,

Sinan.


#14 Infocatcher

Infocatcher

    Member

  • Members
  • 11 posts


  • Translator for [No translator]
  • Extension Developer: Yes
  • Extensions: Private Tab
  • My OS Windows

Posted 11 May 2014 - 10:31 AM

QUOTE (alfapegasi @ May 11 2014, 08:35) <{POST_SNAPBACK}>
tr is released

Thanks, updated: https://github.com/I...b1dc5a9e1c9798e

But I have some notes.
Attached File  fx_Private_Tab_tr_locale.png   17.98KB   14 downloads
(this is Turkish language pack on Firefox 29.0.1)
So, I think, it's better to 1) translate accesskeys and 2) don't use Title Case (e.g. "Yeni Gizli Sekme" -> "Yeni gizli sekme").

#15 alfapegasi

alfapegasi

    Advanced Member

  • Members
  • 112 posts
  • Gender:Male
  • Location:Ankara, Turkey


  • Translator for Turkish (tr)
  • Extension Developer: No
  • Translation Credits to Sinan Kaan Yerli (skyerli.org)

Posted 11 May 2014 - 08:35 PM

QUOTE (Infocatcher @ May 11 2014, 12:31) <{POST_SNAPBACK}>
So, I think, it's better to 1) translate accesskeys and 2) don't use Title Case (e.g. "Yeni Gizli Sekme" -> "Yeni gizli sekme").


Sure. I'll do that.

However, being EN as the default, your "Open Link in New Private Tab" string has "v" as the accesskey. Mine probably will have "g" (of "Gizli") as the accesskey. So, if accesskeys are translated would you like to keep the /original/ Title Case of the string.

Not all creators would like to see translation of accesskeys: Mostly because of conflict with other add-ons and/or firefox itself: "v" might be well thought but /my/ "g" might get conflicted with similar add-on(s); yes I know it will only change the key-press-order but by doing so you are changing /the customer's default usage behaviour/.

Therefore, there is a tendency (AFAIK) to leave the accesskeys as they are unless requested by the creator.

cheers,

Sinan.


#16 Infocatcher

Infocatcher

    Member

  • Members
  • 11 posts


  • Translator for [No translator]
  • Extension Developer: Yes
  • Extensions: Private Tab
  • My OS Windows

Posted 13 May 2014 - 12:40 PM

QUOTE (alfapegasi @ May 11 2014, 23:35) <{POST_SNAPBACK}>
Sure. I'll do that.
Thanks, updated: https://github.com/I...0c9a8fe34f339ce

QUOTE (alfapegasi @ May 11 2014, 23:35) <{POST_SNAPBACK}>
So, if accesskeys are translated would you like to keep the /original/ Title Case of the string.
...
Therefore, there is a tendency (AFAIK) to leave the accesskeys as they are unless requested by the creator.
I just think, that extensions should be in line with the browser UI (if possible and if this isn't something to change UI). And extensions localization should looks similar to browser localization.
So, if we have "Yeni sekmede aç" for built-in item, it's better to use "Yeni gizli sekmede aç".

#17 Lakrits

Lakrits

    Daredevil Test Pilot

  • Admin
  • 894 posts
  • Gender:Male
  • Location:Uppsala, Sweden
  • Interests:# Science (biology and ecology, mainly botany, mycology, and plant and forest pathology).<br /># Language (words, their use, sounds and flexibility).<br /># Tennis (and almost any other sport, but first and foremost tennis).<br /># Theatrical arts.<br /># … and much more.


  • Translator for Swedish (sv-SE)
  • Extension Developer: No
  • Translation Credits to Mikael Hiort af Ornäs
  • My OS Windows

Posted 13 May 2014 - 01:06 PM

QUOTE (Infocatcher @ May 13 2014, 13:40) <{POST_SNAPBACK}>
I just think, that extensions should be in line with the browser UI (if possible and if this isn't something to change UI). And extensions localization should looks similar to browser localization.

I agree. That will also make the add-on's textual parts easier to read. Changes in the use of upper and lower case letters between e.g. the items in a menu, will make the entire menu somewhat "scrambled". It's actually one of the first things you learn when you take classes in pedagogics or oral and visual presentation. And there are studies suggesting that when too much is happening in a body of text, the average reader will experience what you could call temporary facultative dyslexia.

Of course, when an add-on is "passive" or only uses its own GUI (via buttons, preferences windows, etc.), the "anomalies" will be contained in a closed setting, and hence be perceived as normal in that particular environment. However, to ensure that the add-on will be as easy to use as possible, regardless of its placement within any given UI, compliance with the standard Mozilla UI for your locale is always preferred. That also gives the developer the opportunity to move the add-on's UI around inside the Mozilla UI, without loosing any of the usability or (as some developers like to "hide" their add-ons) stealthiness.

Well, that's my opinion. (Remember that it won't become universal law until I manage to take over the world, so you're all safe for now. biggrin.gif )

Lakrits
"[…] och han talar med bönder på böndernas sätt
men med lärde män på latin." – Erik Axel Karlfeldt

Lakrits
BabelZilla admin
Moderator for the Swedish BabelZilla forum section


0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users