i18n spell checker + mail scrolling

[novad]

Hello everybody,

I'm administrator of a zimbra NE and make my tests on a FOSS version for our future migration to version 6.xx

I have 2 big questions.

1) Spell checker

once upon a time there was a bug (bug 22255 Spell checker not i18n ready) for which I voted. This bug was tagged as resolved for version 6.02 (that I installed yesterday). It still doesn't work and actually makes the following error :
"A netwok error occured" (I allready sent the error report).
I tried to access the bug (22255) in the bugzilla but it is locked down . Does anyone have any new about it????

2) Mail scrolling

This new feature is actually a bit... hum... not polished
Is there a way to:
- Configure back the old behaviour (X mail per page)?
- To show more mails per default?
- To rise the number of mails added per step when the scrollbar arrives at the bottom of the page?
- To show all mails in the mailbox in one easy step?

One nice additional feature would be a way to say how many mails to show... for example "Show XXX Mails" (XXX being editable and with the option "all")

P.S: Sorry for my english (I do my best )

Novad

[phoenix]

Hello everybody,

I'm administrator of a zimbra NE and make my tests on a FOSS version for our future migration to version 6.xx

I have 2 big questions.

1) Spell checker

once upon a time there was a bug (bug 22255 Spell checker not i18n ready) for which I voted. This bug was tagged as resolved for version 6.02 (that I installed yesterday). It still doesn't work and actually makes the following error :
"A netwok error occured" (I allready sent the error report).
I tried to access the bug (22255) in the bugzilla but it is locked down . Does anyone have any new about it????

That bug was resolved for Zimbra 6.x and the 'network error' is likely to be a configuration error (most likely DNS) and nothing to do with the changes for that bug report.

2) Mail scrolling

This new feature is actually a bit... hum... not polished
Is there a way to:

The new scrolling is the way it will be and not the 'old' per-page method.If there's a problem with it then I'd suggest you raise a bug report.What exactly does 'not polished' mean?

[novad]

That bug was resolved for Zimbra 6.x and the 'network error' is likely to be a configuration error (most likely DNS) and nothing to do with the changes for that bug report.

Well... That doesn't explain why the bug is locked down and not accessible.
The full error I recieve is this:

+++++++++++++
method: CheckSpellingRequest
msg: system failure: Spell check failed: iconv() [function.iconv]: Detected an illegal character in input string
code: service.FAILURE
detail: soap:Receiver
trace: btpool0-24://mail.xsys.ch/service/soap/CheckSpellingRequest:1256633126337:000da97c3709404 0
request:

>>I deleted my mail for privacy<< 0_e907b338a8337036f0bdfba0d5e2718129567881_69643d3 3363a32663063343666322d613239362d343266642d6263396 62d3432313331356265343532633b6578703d31333a3132353 63830323232373431333b747970653d363a7a696d6272613bB onjour
+++++++++++++

That doesn't look like a DNS error. My test system is working since one year and I never had any DNS problem with it... Anyway I'll check it again.

The new scrolling is the way it will be and not the 'old' per-page method.If there's a problem with it then I'd suggest you raise a bug report.What exactly does 'not polished' mean?

That means "not easy to use (little moves you must make at the bottom of the scrollbar during one minut to reach last mail)", "slow scrolling", "unhandy to reach last mails in your mailbox" or "missing some features that ** I ** think would be nice" (Maybe I'm alone with that).

Any idea for my other questions about mail scrolling???

Is there a way to show more mails per default?
Is there a way to rise the number of mails added per step when the scrollbar arrives at the bottom of the page?
Is there a way to show all mails in the mailbox in one easy step?

Thank you for your help,

Novad

[phoenix]

Well... That doesn't explain why the bug is locked down and not accessible.
The full error I recieve is this:

+++++++++++++
method: CheckSpellingRequest
msg: system failure: Spell check failed: iconv() [function.iconv]: Detected an illegal character in input string
code: service.FAILURE
detail: soap:Receiver
trace: btpool0-24://mail.xsys.ch/service/soap/CheckSpellingRequest:1256633126337:000da97c3709404 0
request:

>>I deleted my mail for privacy<< 0_e907b338a8337036f0bdfba0d5e2718129567881_69643d3 3363a32663063343666322d613239362d343266642d6263396 62d3432313331356265343532633b6578703d31333a3132353 63830323232373431333b747970653d363a7a696d6272613bB onjour
+++++++++++++

That doesn't look like a DNS error. My test system is working since one year and I never had any DNS problem with it... Anyway I'll check it again.

You're quite right, that doesn't look like a DNS error but that's not what you posted in your earlier post. I'd suggest you file a bug report for this problem.

[novad]

Hello (again)

The error I just posted is the result of "Show details" of the error I posted forst... So yes... It's related.

Anyway, I'll post a bug repport.

Regards

Novad

[ArcaneMagus]

That error is related to the following two bugs:
Bug 41394 - spanish spellcheck uses 8859-1 instead of UTF-8 when suggesting words
Bug 41760 - Spell check fails on illegal characters

[novad]

Yes... It's exactly that... I have in fact both problems even if I posted only about the one with the system error (41760)

I'll add the info to my bug submission and keep an eye on that.

Thank you for the info

[ArcaneMagus]

There is no need to file a new bug only to have it duped to those two bugs, simply vote for those bugs and you will see when the status is updated on either (41394 was already fixed... might not have made it into 6.0.2 though, 41760 hopefully will be in 6.0.3).

Only file a new bug if there is an issue not already in bugzilla.

[Gaarby]

Hi

I have exactly the same problem (41394) with speel checker and french dictionnary.
I have upgraded to 6.0.2_GA 64bit on debian.
I have found a workaroud who work fine for me:
Edit /opt/zimbra/httpd/htdocs/aspell.php

Simply comment following lines
$text = iconv("UTF-8", "iso-8859-1//IGNORE", $text);
This line resolved the zimbra error
you have to comment too this line:
$suggestions = utf8_encode($suggestions);
Who resolved bug for suggestion with specials caracters

Hope this help you.

[novad]

Thanks Gaarby.

I'll simply wait for 6.03. Zimbra people have confirmed me that it would be corrected for this version.

As the server is not in production (test server) I can wait for that