Translate Word 2008

[vikinge]

I also cannot translate. Web site load just fine http://mso.worldlingo.com/.
On my office network full T1, unless special outbound ports need to be
opened in my firewall, why else would everything I try to translate
say "Office cannot connect to the internet"

 

[Curt Laird]

Thanks, vikinge.

I am able to reproduce this now. I'm looking into it and I'll reply when I
have more information.



Curt

I also cannot translate. Web site load just fine http://mso.worldlingo.com/.
On my office network full T1, unless special outbound ports need to be
opened in my firewall, why else would everything I try to translate
say "Office cannot connect to the internet"

--
Curt Laird
Software Development Engineer in Test
Microsoft MacBU - Word
(e-mail address removed) (remove ³ONLINE² for all replies)

This posting is provided ³AS IS² with no warranties, and confers no rights.

 

[Curt Laird]

Hi vinkage,
We have tracked this down to an issue related to proxies through the
Translate feature. There are potentially a couple of workarounds:

1. Don't specify a proxy (probably not an option if you're at work)
2. In Network Settings, under Bypass proxy settings for these Hosts &
Domains, try entering a wildcard (i.e. "*.*") or an exception for
mso.worldlingo.com.

I'll be testing the latter more in-depth shortly, but I thought I'd fill you
in with what I know so far.

If you do not have a proxy specified and you're still having problems, try
turning on the Web Proxy and try step 2 above.

Hope this helps.



Curt

Thanks, vikinge.

I am able to reproduce this now. I'm looking into it and I'll reply when I
have more information.



Curt

--
Curt Laird
Software Development Engineer in Test
Microsoft MacBU - Word
(e-mail address removed) (remove ³ONLINE² for all replies)

This posting is provided ³AS IS² with no warranties, and confers no rights.

 

[Curt Laird]

Ugh. Let me revise my response:

The issue is caused by *not* having a proxy specified. So ignore option 1.

Curt

Hi vinkage,
We have tracked this down to an issue related to proxies through the
Translate feature. There are potentially a couple of workarounds:

1. Don't specify a proxy (probably not an option if you're at work)
2. In Network Settings, under Bypass proxy settings for these Hosts &
Domains, try entering a wildcard (i.e. "*.*") or an exception for
mso.worldlingo.com.

I'll be testing the latter more in-depth shortly, but I thought I'd fill you
in with what I know so far.

If you do not have a proxy specified and you're still having problems, try
turning on the Web Proxy and try step 2 above.

Hope this helps.



Curt

--
Curt Laird
Software Development Engineer in Test
Microsoft MacBU - Word
(e-mail address removed) (remove ³ONLINE² for all replies)

This posting is provided ³AS IS² with no warranties, and confers no rights.

 

[spem54]

Sorry, still does not work. Thanks for your effort.

 

[spem54]

I have tried the option of turning on the Web Proxy, but this way it
stops all my internet connection. I will keep trying.

 

[John McGhie]

It's a bug. They are working on it.

You need to set up the Proxy and then add the translation page as an
"exception", I believe.

The bug is that it needs the proxy to "exist", but do nothing

Hope this helps

I have tried the option of turning on the Web Proxy, but this way it
stops all my internet connection. I will keep trying.

--
Don't wait for your answer, click here: http://www.word.mvps.org/

Please reply in the group. Please do NOT email me unless I ask you to.

John McGhie, Consultant Technical Writer
McGhie Information Engineering Pty Ltd
http://jgmcghie.fastmail.com.au/
Nhulunbuy, Northern Territory, Australia
+61 4 1209 1410, mailto:[email protected]

 

[spem54]

Any news on this topic? THX

 

[John McGhie]

I understand your keen interest, but no, and you wouldn't expect any more
news yet.

They have told us that it's a confirmed bug. That means it has been
scheduled for a fix.

Given that this is a new and highly-prized feature, I would imagine that the
fix will be in Service Pack 1.

That would put it three to six months out. In this case, I suspect it might
be a little earlier, but not much.

If you make a change, even a tiny change, to a software product, you have to
TEST the entire product. You will inevitably discover that you have broken
something else, so you have to fix and re-test. This process takes about
three months on a big product like Microsoft Office.

Hope this helps

Any news on this topic? THX

--
Don't wait for your answer, click here: http://www.word.mvps.org/

Please reply in the group. Please do NOT email me unless I ask you to.

John McGhie, Consultant Technical Writer
McGhie Information Engineering Pty Ltd
http://jgmcghie.fastmail.com.au/
Sydney, Australia. S33°53'34.20 E151°14'54.50
+61 4 1209 1410, mailto:[email protected]

 

[spem54]

This bug is not solved in the recent update!

 

[John McGhie]

Thanks for the report.

Yes, it is not listed among the fixes in update 12.0.1.

Sorry

This bug is not solved in the recent update!

--
Don't wait for your answer, click here: http://www.word.mvps.org/

Please reply in the group. Please do NOT email me unless I ask you to.

John McGhie, Consultant Technical Writer
McGhie Information Engineering Pty Ltd
http://jgmcghie.fastmail.com.au/
Sydney, Australia. S33°53'34.20 E151°14'54.50
+61 4 1209 1410, mailto:[email protected]