Simply not working anywhere (Chrome v13.x)

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Install version 1.1.4.
2. Edit options, remove all Kanji from exclude list, or make exclude only the 
most common 100 Kanjis (Or just don't modify any settings. Modifying or not 
modifying these settings does not make any difference).
3. Open any page with lots of Kanji in it.
4. Observe it is not injecting any Furigana.

What is the expected output? What do you see instead?
There must have been Furigana injected.

Which browser are you using, Firefox or Chrome? On what operating system?
Google Chrome 13.0.782.215 m
Windows 7 Ultimate x64 SP1, Up-to-date

Please provide any additional information below.
I installed only this Furigana Injector extension and nothing more. I don't 
know if I need to install any companion extension (Like we used to install 
"HTML Ruby" in Firefox) or not. Please instruct me (and give me a URL) to do so 
if I need any tool to install in order to make this extension work.

Original issue reported on code.google.com by AhmedHan on 29 Aug 2011 at 12:39

[GoogleCodeExporter]

It is not necessary to install a Ruby extension, because Chrome supports ruby 
natively.

If a "振" icon does not appear on the right-hand side of URL bar, then 
Furigana Injector did not for some reason detect any Japanese text on the page. 
This can happen on some sites, most notably facebook.com, which insert most of 
their content AJAX'ly.

If the "振" icon does appear (in black, not grey) but nothing seems to happen 
after clicking it, first can you confirm that the text isn't all links (e.g. 
www.asahi.com) and/or that Furigana Injector's option "Include text inside 
links" is on?

After this, if the problem continues, can you describe what happens? The most 
common error at this stage is that the server is down, and a message appears 
saying that. If it doesn't, then I'd like to see what the javascript error log 
is for the extension. ("Manage extensions", enable developer mode, inspect 
"background.html", click the "show console" button at the bottom.)

Original comment by akira.kurogane@gmail.com on 29 Aug 2011 at 1:51

[GoogleCodeExporter]

Thank you for your message.

A "振" icon does not never appear. I didn't see it even once. I tried turning 
on and off the option "Include text inside links", but in either case nothing 
changes.

I visited the link you have given (asahi.com). No Furigana is inserted, nor the 
"振" icon appeared. The problem is not only in Facebook.

There is no message which informs about any server errors. Everything is so 
silent.
This image is the screenshot of the console (also added it as an attachment):
http://img52.imageshack.us/img52/7642/furiganainjectorconsole.png

Thank you for your help.
I will appreciate your further help.

Original comment by AhmedHan on 29 Aug 2011 at 2:11

Attachments:

• FuriganaInjectorConsole.png

[GoogleCodeExporter]

Thanks so much for that screenshot!

The error message "The extension manifest must request permission to access 
this host" which appears when Furigana Injector tries to open it's welcome page 
(just a HTML file within the extension's subdirectory) is very interesting. How 
and why would Chrome be blocking it?

The messages "The localStorage [XYZ] value was null. It will be initialized" 
show that this is the first time after installing the extension, or that access 
to the localStorage object is permanently blocked. I would be interested to 
know if it appears every time, or just once.

In general it is as though there is a permissions problem which is nearly 
completely disabling the extension. So I can research, what is the version of 
your Chrome. 12.x? 13.x? Something else?

Also please note that Furigana Injector has been deliberately disabled from 
running on HTTPS web sites or local files, so sticking with 
http://www.asahi.com/ as a test site would be appreciated.

(The "Failed to load resource" errors next to "wwwjdic.cgi" resources are not 
important. A large list of WWWJDIC servers are checked and some are now 
offline. Ignore.)

Original comment by akira.kurogane@gmail.com on 29 Aug 2011 at 2:34

[GoogleCodeExporter]

I made a second check on the console after opening http://www.asahi.com/. This 
time console output looked like different. I'm attaching the screenshot again.

My browser version is this: Google Chrome 13.0.782.215 m

Original comment by AhmedHan on 29 Aug 2011 at 2:44

Attachments:

• FuriganaInjectorConsole2.png

[GoogleCodeExporter]

Ah, this changes things completely. Actually the second screenshot shows no 
problems.

Thanks for advising your version no. My browser is still at version 12.x, I'll 
upgrade and check that for myself. I'll post on this issue thread again when I 
have.

Original comment by akira.kurogane@gmail.com on 29 Aug 2011 at 2:50

[GoogleCodeExporter]

Long story short, I couldn't get version 13.x, although I could install a daily 
dev build, which is currently version 15.0.865.0.

I could not replicate the problem. My actions:

* Start up chrome. (The output to the background page's java console is the 
same as the last screenshot, which is normal and correct.)
* Open http://www.asahi.com/
* When the page has completely finished loading (was about 5secs), the 振 icon 
appeared (black colour, not grey). When I click it, after a second furigana are 
inserted.
* No extra lines appear in the background page's java console. That's OK.
* (An error message "background returned a gloss for 
#fi_ruby_doppleganger[xx...xx] but it didn't exist/was already removed." did 
appear in the java console for the foreground page (i.e. www.asahi.com) but 
this is not a problem. It's probably a HTML element that was dynamically 
deleted by the site's javascript.)

Could you tell me at which point your experience deviates?

Original comment by akira.kurogane@gmail.com on 29 Aug 2011 at 3:17

[GoogleCodeExporter]

My steps:

* Start up chrome. (The output to the background page's java console is similar 
to the last screenshot, the only difference is the order of lines. See the 
attachment.)
* Open http://www.asahi.com/
* When the page has completely finished loading (was about 5secs), the 振 icon 
appeared (black colour, not grey). When I click it, after 30 seconds I receive 
an error message, as seen in the second attachment. (At this point I have to 
admit that until now I wasn't looking for the "振" icon at the address bar. 
Instead I was expecting to see it in the tool-bar where the icons of all other 
extensions exist. I don't know if the "振" icon existed there all the time and 
I'm just noticing it, or it appeared there for the first time.)
* No extra lines appear in the background page's java console.
* (There are some error messages listed in the foreground java console which 
are shown in the screenshot in the third attachment.)

Original comment by AhmedHan on 29 Aug 2011 at 3:43

Attachments:

• FuriganaInjectorConsole3.png
• FuriganaInjectorError.png
• FuriganaInjectorForegroundConsole.png

[GoogleCodeExporter]

Ahah! I have function discoverability issue. If you never saw the welcome page 
it's easier to understand why you missed it. Or, if you're used to the Firefox 
version ... you looked for a fixed icon because that's the way they do it there.

OK, now it looks like a more common issue, being unable to connect to furigana 
server. But I don't think it is that. A) the server is up now, B) ("Furigana 
Injector service at http://fi.yayakoshi.net/furiganainjector confirmed") 
confirms you could connect to it at least once, and C) the messages "Processing 
as GM script", "GM_setValue is not supported" are suspicious. Does "GM" = 
GreaseMonkey, maybe?

Could you please try and find if there's an extension clash? I.e. disable all 
your other extensions and try again.

Original comment by akira.kurogane@gmail.com on 29 Aug 2011 at 4:44

[GoogleCodeExporter]

I disabled all other extensions, but it gave the same error message (Request to 
fetch data from furigana server(s) failed.).

GM_* functions are most probably Greasemonkey API functions. I too wondered 
what they are doing in Google Chrome.

Original comment by AhmedHan on 29 Aug 2011 at 11:01

[GoogleCodeExporter]

Hmm, I don't have any other ideas for today. Let me sleep on it.

In case you were thinking it, I wouldn't recommend uninstalling the other 
extensions. I'm quite confident that disabling them and simply reloading the 
test page once is enough to avoid the interference.

Mata ato de ...

Original comment by akira.kurogane@gmail.com on 29 Aug 2011 at 11:14

[GoogleCodeExporter]

Why don't you make an off-line version of this extension? Establishing a remote 
connection to a server will of course cause problems like this on some users, 
that's inevitable. In an off-line solution, mass amount of harddisk usage may 
be a disadvantage, but robustness, security and absence of server down problems 
are the most essential features for some users like me. I just don't like the 
idea that I must connect to a remote server every time I open any web page. 
This causes extra bandwidth usage, increment in page load time, security 
problems, problems like being not able to work on HTTPS protocol, and being out 
of service when the remote server is down.

Please consider also supporting an off-line version. When I was using Firefox, 
Furigana Injector + HTML Ruby was doing a super job, and that was the important 
thing for me.

Original comment by AhmedHan on 29 Aug 2011 at 11:49

[GoogleCodeExporter]

It's a simple answer, which has been given before: the natural-language parsing 
used takes up _too much_ memory with recent dictionaries- and they're only 
going to get bigger. A server or PC can afford to allocate the 250Mb for a 
standalone application, it's no big deal, but that's a ridiculous thing for a 
browser sub-process.

Secondly Chrome just doesn't support binary add-ons like Firefox does, so 
making it work like the old 1.x versions of Furigana Injector for Firefox isn't 
possible. Furigana Injector 2.x for Firefox uses the server already.

But I have been developing a new offline option for months. I have been looking 
for volunteers to try it, too. Basically it's to run the server on your own 
local PC. If you have the memory and CPU to spare you can enjoy the increased 
speed and run whilst offline. I will upload the code and you can compile it ... 
if you're a C and/or C++ developer.

However in your case I don't think we'll succeed. I strongly suspect there is 
some exceptional problem in your environment that stops the content-side script 
of Furigana Injector from working. It could have been a new Chrome version 
issue but so far I haven't had any other reports from other v13.x users.

Sorry.

Original comment by akira.kurogane@gmail.com on 30 Aug 2011 at 8:03

• Changed title: Simply not working anywhere... (Chrome v13.x?)

[GoogleCodeExporter]

Hello. I have the same problem. It is just not working. Can you please change 
your decision and make an offline version? People can choose between offline 
and online versions.  Today's computers are strong enough to spare 250Mb for 
learning Japanese.

Original comment by KubilayE...@gmail.com on 4 Dec 2011 at 10:26

[GoogleCodeExporter]

There are now more thousands more users thanks to this change. If you want to 
go back to the DLL version try pulling the < 2.0 versions from the Firefox 
add-ons site, and hack the chrome.manifest and javascript until the latest 
versions of Firefox will accept.

Alternatively, there is a local* version of the server you can try. This is 
only option for Chrome users. If you're a linux user I can send you a binary. 
Otherwise you'll have to compile the source code. If you're an experienced 
C/C++ developer you will be able to do it. 
http://code.google.com/p/furigana-injector/source/browse/#svn%2Ftrunk%2Ffurigana
server.

*It runs locally. Actually it's exactly the same as the real server, except for 
the port it'll run on.

Akira

Original comment by akira.kurogane@gmail.com on 4 Dec 2011 at 12:24

[GoogleCodeExporter]

Hello again;

I'm a C++ programmer, but not too experienced. I have just checked the source 
code of the server. There are Python source code files, different source code 
directories and some include directives which includes Linux files, like 
"pthread.h"; I got confused a little.

I would like to compile this code for Windows using Visual Studio 2010. If tell 
me the steps, I can compile it and share with other friends.

Original comment by AhmedHan on 4 Dec 2011 at 1:52

[GoogleCodeExporter]

Hi Ahmed. If you compile it on Windows, please share. I will happily make it a 
download on this site.

First install Mecab, with dev/lib options included. You should probably install 
a dictionary too (Unidic, or IPAdic) and test that it works from the command 
line once.

Then back in this code build the mongoose and json-c directories. (These are 
external projects- http://code.google.com/p/mongoose/ and 
http://oss.metaparadigm.com/json-c/). Then finally you can build the fiserver/ 
subdirectory, which will include/link the Mecab, Mongoose and json-c libs. The 
"fiserver" executable produced here is the actual server.

Original comment by akira.kurogane@gmail.com on 5 Dec 2011 at 2:21

[GoogleCodeExporter]

I'm having a similar issue in that the icon just does not appear, ever. I've 
tried disabling every other addon and just running it alone but still nothing. 
I'm using the most recent version of Chrome (19.0.1084.24).

I'll attach a screenshot but I think my errors are the same as the others have 
had.

Original comment by davyde...@gmail.com on 18 Apr 2012 at 10:25

Attachments:

• errors.PNG

[GoogleCodeExporter]

Re: comment #17, the icon should only appear on pages with Japanese text. And 
if you've set your kanji list to be very large, only on a few of those. Also, 
heavy ajax-using pages (google mail, facebook are the most common examples) 
tend to avoid triggering events the japanese text detection needs.

Original comment by akira.kurogane@gmail.com on 19 Apr 2012 at 5:59

[GoogleCodeExporter]

Original comment by akira.kurogane@gmail.com on 19 Apr 2012 at 5:59

• Changed title: Simply not working anywhere (Chrome v13.x)

[GoogleCodeExporter]

Original comment by akira.kurogane@gmail.com on 19 Apr 2012 at 6:00

• Changed state: Started

[GoogleCodeExporter]

I've left the kanji list at default. I am testing it on many different pages, 
all Japanese. Even the asahi site you recommend. Still nothing.

Original comment by davyde...@gmail.com on 19 Apr 2012 at 12:05

[GoogleCodeExporter]

Maybe you could try to view the javascript console output when you open a 
japanese page? Javascript errors show which file they occurred in, which in the 
case of Furigana Injector will be something like 
"chrome://cbahnmcliajmanjkaolemjelphicnein/kanji_content_detect.js".

("cbahnmcliajmanjkaolemjelphicnein" is just a more-or-less random id code that 
was given to F.I. when it was uploaded to the Chrome Extensions site.)

Original comment by akira.kurogane@gmail.com on 19 Apr 2012 at 12:37

[GoogleCodeExporter]

Hi again. I reformatted my computer last night (due to an unrelated problem) 
and now the plugin works fine. My google version is also 18.0... now instead of 
the 19. I had before. I dunno if that was the problem but I do know I was 
having a lot of issues with java prior to the reformat.

Original comment by davyde...@gmail.com on 20 Apr 2012 at 1:39

[GoogleCodeExporter]

Original comment by akira.kurogane@gmail.com on 28 May 2012 at 2:50

• Changed state: WontFix

[GoogleCodeExporter]

(No comment was entered for this change.)
Status: WontUse

Original comment by AhmedHan on 28 May 2012 at 5:57