Snowl - Ver. 0.4x0d2010, Updated: 18/01/10 09:41 Options

[alta88]

Maintainer: alta88
Creator: Myk Melez

Ext. Version: 0.4x0d2010
Description: conversations redelivered
Extension is compatible to: ( 3.6 - 3.6.*)

Included locales: bg-BG cs-CZ de-DE en-US es-ES fr fy-NL hu-HU ja-JP nl nn-NO pl-PL pt-PT ru-RU zh-CN

View on WTS -- Download the extension

This post has been edited by alta88: Jan 23 2010, 18:20

[markh]

Welcome!

Just a bit of information for you: in case you have some queries about the WTS, you can find short and simple Questions&Answers about it here!

In case you're looking for a specific translator, please see the list of available translators on BabelZilla.
When you select the desired one, you can send him/her a P.M. or an e-mail (if and when public).

You may also insert a new Topic in the Help Section, in order to ask for specific translations, to write a general request about missing translations, etc.

[markh]

@translators: this is an early version of the possible future of Firefox. You can find more information here.

[markh]

Dutch locale added, tested and released

[Alphawolf]

German locale added, tested and released.

[humbertosartini]

Hi,

Portuguese (Brazilian) / pt-BR localization has been released

[luiso20]

Hi!:

Spanish (es-ES) locale added, tested and released.

[markh]

Argh. I suppose you did the second update just after I pushed my locale to Testing/QA
Fortunately I kept a local copy on my other PC so I’ll update tomorrow

[geolocale]

German translation updated comprehensively, current state is finished. Maybe it finds his way to the next pre-release of Snowl?

[mrfyda]

Hi there.
I noticed that in the file search.dtd there are some missing strings.
They're causing this error:

[markh]

I noticed a couple of unlocalized strings, even though they are translated in some cases:
In firstrun.dtd: snowl.firstrun.get.involved
In preferences.dtd: refreshMinutes.accesskey
In opml.properties, opmlFilterTitle does not seem to be used for the import function.
In the collections sidebar, the translated ‘All messages’ is followed by untranslated English strings between parentheses.
It seems that the string ‘Unsubscribe’ (which appears as a button when clicking a feed in the subscription pane) is not localized.

[alta88]

I noticed a couple of unlocalized strings, even though they are translated in some cases:
In firstrun.dtd: snowl.firstrun.get.involved
In preferences.dtd: refreshMinutes.accesskey
In opml.properties, opmlFilterTitle does not seem to be used for the import function.
In the collections sidebar, the translated ‘All messages’ is followed by untranslated English strings between parentheses.
It seems that the string ‘Unsubscribe’ (which appears as a button when clicking a feed in the subscription pane) is not localized.

hi,

i've been working with myk on snowl, and he's onto other projects lately, so i'll be handling some things.

thanks for your comments.
1) fixed.
2) fixed.
3) that string is in the native OS filepicker filter box (not the title).
4) ah yes, the messages statistics. oops. i foresee a quick subsequent release, and it will be fixed then.
5) will be fixed in the next release.

also, is there a way for me to be a contributor or such that Snowl appears in my list of extensions? i currently have TotalToolbar on babelzilla at the moment.

thanks!

[markh]

hi,

i've been working with myk on snowl, and he's onto other projects lately, so i'll be handling some things.

thanks for your comments.
1) fixed.
2) fixed.
3) that string is in the native OS filepicker filter box (not the title).
4) ah yes, the messages statistics. oops. i foresee a quick subsequent release, and it will be fixed then.
5) will be fixed in the next release.

also, is there a way for me to be a contributor or such that Snowl appears in my list of extensions? i currently have TotalToolbar on babelzilla at the moment.

thanks!

Many thanks!
Currently only the registered developer sees an extension listed. I will make a feature request out of this, since it is possible that an extension is worked on by more than one person.

[alta88]

hi,

there seems to be a bug in the bz uploading/parsing of files. we have a search.dtd which is missing quite a few entities (and the reason for the problem in #10). for example:

<!ENTITY search.example1 'foo, "foo*"'>

is missing. the likely problem is that parsing for the single quotes failed and the entry was dropped. the single quotes are used if the string is to contain double quotes. all missing entries have this in common.

how can this be fixed?

[Goofy]

Yes this is an issue, but as far as I can see

this kind of quote embedment is parsed correctly

<!ENTITY search.explanation4 "Match all items with either 'foo' OR 'bar'.">




but this one is not :

<!ENTITY search.example9 '"*foo bar", *bar'>
<!ENTITY search.explanation15 'Finds "foo b r", "foo b=r", etc. but not "foo bar".'>
(you ought not have single quote to delimit the string)

I would say you should make the missing strings compliant to the dtd usage, which is
<!ENTITY example "this is a string with a 'quote' inside ">

Note that it is also possible to have this
<!ENTITY example "this is a string with a &quot; word &quot; inside ">

[alta88]

yes, but in this case the meaning of the " in the string must be maintained, so it can't be replaced with a single quote. ie the user must enter " for quoted searches to work. also, are you sure using single quotes is not dtd compliant? the browser is able to parse it just fine in my local search.dtd, the issue is the upload of the string literals to bz.

&quot; works of course but is certainly less preferable/readable, a localizer might take it literally. but if you're saying fixing the upload engine isn't an option..

[Goofy]

yes, but in this case the meaning of the " in the string must be maintained, so it can't be replaced with a single quote. ie the user must enter " for quoted searches to work. also, are you sure using single quotes is not dtd compliant? the browser is able to parse it just fine in my local search.dtd, the issue is the upload of the string literals to bz.

&quot; works of course but is certainly less preferable/readable, a localizer might take it literally. but if you're saying fixing the upload engine isn't an option..

I know that the wts parser could be more compliant, and I hope it will be, but unfortunately we are currently much annoyed because our one and only tech admin is seriously ill and not available to fix things (I am no coder at all)

As for the &quot; I think you can use it before submission because it will be converted to " " so it will be ok for the final user (needs to be confirmed)

[alta88]

ok, i'll ask myk to upload a new search.dtd with &quot; and i guess everyone needs to look at it again..

[Goofy]

ok Note that you have not to submit again a full xpi but you can upload only the new search.dtd throughout the "upload" tab on the en-US files page. the changes will be mirrorred in avery locale.

[alta88]

hi all,

Fx 3.6 final has been released, a bit earlier than i thought. but it means Snowl 0.4 must be completed and released, as 0.3 is not compatible with 3.6. so far, only de-DE, es-ES, and pt-PT are in a completed state (with the last minute work on search.dtd due to the upload problem).

those locales not done in the next 2 days will have to go out as 0.4 as they are - so finishing up will be most appreciated!

thanks.

(goofy, let me know if there's a better way to ping people)