User talk:Was a bee/Archives/2010 1
![]() | This is an archive of past discussions. Do not edit the contents of this page. If you wish to start a new discussion or revive an old one, please do so on the current talk page. |
Rotating 3D view of thalamus
Hi Was a bee I noticed you added a nice 3D rotating image of the thalamus. I followed the link provided with the image, but I can't find those automatically rotating images. Where did you get that or how did you make it? Such images are wonderful additions to pages about anatomy.
--Wimleenaerts (talk) 21:37, 17 February 2010 (UTC)
- Hi! Wimleenaerts. Anatomography provides only still images. Anatomography itself does not provide animation at all. To make gif animation, I firstly downloaded 72 still images(5 degrees differences each on view angle) with free downloader software. After the download, I combined it into one gif animation with free gif making software. Thank you. --Was a bee (talk) 03:08, 18 February 2010 (UTC)
- Thanks for the response! I already figured that you did it that way, so I tried that myself, but I could only see about 26 different angles and so I could only compose a gif out of 26 images and that's not 'fluent' or 'smooth' enough for me. Can you tell me how exactly you managed to get 72 of those still images? Thanks!
- --Wimleenaerts (talk) 08:35, 18 February 2010 (UTC)
- More precise configuration is done through URL input. For example, Image of "Only Thalamus(red) and Cranium(white, transparent)" has URL
- You can get this type of URL from "SAVE"->"PNG image URL". And 3 digit, after the word "IF", in URL(...tp_ap=08020601:IF09000...) specifies angle around Z axis. So URL below is rotated just 5 degrees from the image above.("..IF090..." becomes "..IF095...")
- By this way, to change the number in URL on address bar of your browser, you can get 1 degree specification of view angle. Thanks:) --Was a bee (talk) 11:01, 18 February 2010 (UTC)
Message from Goethean
Please explain. — goethean ॐ 17:13, 26 April 2006 (UTC)
- I am high level engrish speaker. So it may be difficult for me to explain it cleary. But I'll try it.
- In modern science, it is commonly accepted as an established fact that physical-phenomena arise together in a mutually interdependent web of cause and effect.There are many scientific topics reffer to or have a deep relation to such a nature of causal-chain.For example Light cone, Feynman's Path integral, Complex system, Butterfly effect, etc.... So I thought that these scientific topics could play a role as a reference to some people who want to understand Pratitya-samutpada.
- But, of course, these scientific and religious ideas do not have same meanings. For example, in science, whether "dependent origination" about mental-phenomenon is correct or not, is not yet clear. So I inserted the link in "See also" section. Was a bee 06:50, 27 April 2006 (UTC)
- Thanks for the explanation. You need to source this research and explain it rather than mysteriously inserting a link under "see also". As it stands, it's almost original research and will be deleted (although not by me) eventually . — goethean ॐ 16:06, 27 April 2006 (UTC)
- Thank you for youe advice. I read such a sayings in Japanese book many years ago. And it's original author was the Dalai Lama. But now...... I don't remenber the title of the book:-( So I erase my posting by myself for the present. I think it would be better for everyone. thanks:-) Was a bee 14:51, 28 April 2006 (UTC)
test ����
�g�т��珑�����݁B Writing test from japan with cell phone.
A sneaky soliciting
Hi! I've noticed your edits at the Commons and see that you love science. If you're interested, you could start a page in Japanese Wiki about reelin, or nudge some JaWikipedian interested in neuroscience to start it. ^_^ Best regards, --CopperKettle 06:40, 4 October 2009 (UTC)
- Hi, CopperKettle. I read reelin. That is very interesting article. So I post tranlation request to Medicine&Medical Portal on ja.wiki(I am not good at physiology and proteins). And, at commons, you fixed category name of connectomics, thanks^o^ --Was a bee (talk) 09:39, 7 October 2009 (UTC)
- Thank you, was-a-bee! A request is fine, somebody will surely look it up. (0: --CopperKettle 14:41, 7 October 2009 (UTC)
Thank
Hey, I just noticed you adding colourful images to articles on the brain. And just dropped by to say thank you they look wonderful! Regards, Captain n00dle T/C 12:36, 23 October 2009 (UTC)
- Your welcome Captain-noodle. I think images can be help for people! thnak you :). --Was a bee (talk) 08:36, 27 October 2009 (UTC)
Thank you
Thank you for adding the rotating brain image to Limbic lobe. Your images make neuroscience articles so much easier to understand! Anthony (talk) 08:49, 13 March 2010 (UTC)
The Signpost: 23 August 2010
- WikiProject report: WikiProject Cryptozoology
- Features and admins: The best of the week
- Arbitration report: Proposed decision of climate change case posted
- Technology report: Bugs, Repairs, and Internal Operational News
The Signpost: 30 August 2010
- In the news: Agatha Christie spoiled, Wales on Wikileaks, University students improve Wikipedia, and more
- WikiProject report: Studying WikiProject Universities
- Features and admins: Featured article milestone: 3,000
- Arbitration report: What does the Race and intelligence case tell us?
The Signpost: 6 September 2010
- Book review: Cognitive Surplus, by Clay Shirky
- WikiProject report: Putting articles in their place: the Uncategorized Task Force
- Features and admins: Bumper crop of admins; Obama featured portal marks our 150th
- Arbitration report: Interim desysopping, CU/OS appointments, and more
- Technology report: Development transparency, resource loading, GSoC: extension management
test
hello, this is test. I want him to come here.—Preceding unsigned comment added by Was a bee (talk • contribs) 13 September 2010 00:41 UTC
- I added {{Unsigned}} by myself, because he didn't come! O.o--Was a bee (talk) 01:06, 13 September 2010 (UTC)
The Signpost: 13 September 2010
- News and notes: Page-edit stats, French National Library partnership, Mass page blanking, Jimbo on Pending changes
- Public Policy Initiative: Experiments with article assessment
- Sister projects: Biography bloopers – update on the Death Anomalies collaboration
- WikiProject report: Getting the picture – an interview with the Graphic lab
- Features and admins: "Magnificent" warthog not so cute, says featured picture judge
- Arbitration report: Tricky and Lengthy Dispute Resolution
- Technology report: Bugs, Repairs, and Internal Operational News
The Signpost: 20 September 2010
- From the editor: New ways to read and share the Signpost
- News and notes: Dutch National Archives donation, French photo raid, brief notes
- In the news: Rush Limbaugh falls for Wikipedia hoax, Public Policy Initiative, Nature cites Wikipedia
- WikiProject report: All Aboard WikiProject Trains
- Features and admins: The best of the week
- Dispatches: Tools, part 2: Internal links and page histories
- Arbitration report: Discretionary sanctions clarification and more
- Technology report: Bugs, Repairs, and Internal Operational News
The Signpost: 27 September 2010
- News and notes: French million, controversial content, Citizendium charter, Pending changes, and more
- WikiProject report: Designing WikiProject Architecture
- Features and admins: The best of the week
- Arbitration report: EEML amendment requests & more
- Technology report: Bugs, Repairs, and Internal Operational News
Rollback
![](http://upload.wikimedia.org/wikipedia/commons/thumb/d/df/Wikipedia_Rollback.svg/80px-Wikipedia_Rollback.svg.png)
I have granted rollback rights to your account; the reason for this is that after a review of some of your contributions, I believe you can be trusted to use rollback correctly, and for its intended usage of reverting vandalism, and that you will not abuse it by reverting good-faith edits or to revert-war. For information on rollback, see Wikipedia:New admin school/Rollback and Wikipedia:Rollback feature. If you do not want rollback, just let me know, and I'll remove it. Good luck and thanks. — Tivedshambo (t/c) 16:06, 28 September 2010 (UTC)
The Signpost: 4 October 2010
- WikiProject report: Hot topics with WikiProject Volcanoes
- Features and admins: Milestone: 2,500th featured picture
- Arbitration report: Tricky and Lengthy Dispute Resolution
- Technology report: Code reviewers, October Engineering update, brief news
The Signpost: 11 October 2010
- News and notes: Board resolutions, fundraiser challenge, traffic report, ten thousand good articles, and more
- In the news: Free culture conference, "The Register" retracts accusations, students blog about Wikipedia, and more
- WikiProject report: WikiProject Smithsonian Institution
- Features and admins: Big week for ships and music
- Dispatches: Tools, part 3: Style tools and wikEd
- Arbitration report: Tricky and Lengthy Dispute Resolution
- Technology report: Bugs, Repairs, and Internal Operational News
Vandal Fighter
Hi,
Thanks for the link to download vf35b52. However, I have downloaded it earlier yesterday and it seems that I can't really use it. The problems is that the details was all in "white".. I have to hover the mouse over for a couple of second to have it readable. (Something like if the memory runs low). I have tried to limit my computer usage to only running VF, but no success. I don't really know what went wrong. Could you help ?? Thanks — Tjmoel bicara 18:59, 16 October 2010 (UTC)
Note: I love VF, it is very helpful to control recentchanges.
- Hi Tjmoel. I understand only part of this program :s. I think you may say "all edit summary become white(blanked)." I sometimes experienced same thing. As far as I know, when program runs long time (24h or so), table works strange (e.g. white, blanked summary). On my environment(JRE6/WinXP), if such thing happen, I click Clear button (bottom-right of window), then it will recover. On my environment, vf35b52 works properly for id.wikipedia also. How about your situation? --Was a bee (talk) 15:04, 17 October 2010 (UTC)
The Signpost: 18 October 2010
- News and notes: Wikipedia fundraiser event, Frankfurt book fair, news in brief
- WikiProject report: Show Me the Money: WikiProject Numismatics
- Features and admins: A week for marine creatures
- Dispatches: Common issues seen in Peer review
- Arbitration report: Climate change case closes after 4 months
- Technology report: Video subtitling tool, staff vs. volunteer developers, brief news
GoogleTrans
Hi there,
Thanks for the testing. It's always good to get feedback.
I'll put in the test for the two characters you have mentioned in the next day or two and get back to you.
Thanks Again
Endo999 (talk) 16:37, 22 September 2010 (UTC)
Hi there,
I have a version of the gadget that will parse with the punctuation characters you mentioned. It also has IEv9 changes in it as well. I am going to test for a couple of days and then update the actual gadget on enwiki.
You are welcome to take the version at:
User:Endo999/vector.js
and see if it does what you want. The changes for you will only work if the default from language is 'ja' (see instructions at help page on porting to other wikis).
Endo999 (talk) 06:49, 24 September 2010 (UTC)
- Thank you Endo999! Now I am testing your new codes in various text. Please wait one day. thank you:) --Was a bee (talk) 23:15, 24 September 2010 (UTC)
- I tested the code. Both "," and "。" is detected. :D --Was a bee (talk) 09:58, 25 September 2010 (UTC)
- I think this code can already provide nice support for non-Japanese speakers. But unpredictable text splittings also occur frequently. Although it it difficult for me to explain it in English...I will try it. In many text, Japanese text is shorter than translated text. Translated text in popup window is longer than original Japanese text in popup window. I put simple one of such case at my test page. Could you find why this happen. --Was a bee (talk) 09:58, 25 September 2010 (UTC)
Hi, I think I know why this happens. I'll get back to you in one more day with changes. Endo999 (talk) 17:56, 25 September 2010 (UTC)
Hi, it's going to take more than a day since I have finally figured out what I have to do to support your two characters. I will do the changes this week and get back to you.
Thanks Again
Endo999 (talk) 22:53, 27 September 2010 (UTC)
- Sorry, and Thank you for your contribution. Please feel at ease, and get on your own pace. I am not hurry. :-D --Was a bee (talk) 14:59, 28 September 2010 (UTC)
- Hi there, I have come up with something but it needs another day of testing. The parsing for the extra punctuation characters was a bit of a problem, but it is good practice for the Asian languages. I'll let you know when my vector.js file is ready to use. Endo999 (talk) 05:45, 5 October 2010 (UTC)
- Hi there, I have finished the coding changes and tested them. Japanese text is now parsed by the two punctuation marks you told me about. I have also strengthened the word under cursor detection algorithm as well, which is good. The changes are in
- You are welcome to test them and please tell me if there are any problems. I will test this new procedure on my enwiki vector.js for about a week and then update the main gadget code after that. Thanks again for the information on Japanese punctuation marks. I was not aware of it before. Endo999 (talk) 18:11, 6 October 2010 (UTC)
- Thank you Endo999! I tested in various pages on jawp. That nicely works.
- Additionally, sorry for additionally, I have one hope about selecting feature. I wrote about it at my test page. I think this feature (translating precisely selected) is good not only for Japanese but also other no space language(e.g. Chinese) and also English.
- I think this selecting feature is very crucial for Japanese and Chinese learners. Because Japanese and Chinese learners must struggle with many kanjis. If poeple want to read Japanese text, people must know at least two thousand kanjis, generally four thousand (this number is Japanese case. I don't know about number of Chinese case). For this reason, Japanese (and Chinese) language leaners have many wants of translating each kanji as much as wants of translating text. Additinally In English, by selecting characters, words can be translated in many style. For example, Oxfordshire can be translated as Oxfordshire and Oxford and shire. This may be good for learners like me :D I can imagine how much hard fixing code is. So this is just hope. Thank you :) --Was a bee (talk) 14:20, 7 October 2010 (UTC)
- Yes, from your very good example 2 page I see what you mean by selection difficulties. I'll see what I can do and get back to you. Endo999 (talk) 15:46, 7 October 2010 (UTC)
- I have fixed up IE selection processing. Thanks so much for your testing. This was a general problem with GoogleTrans. When the zoom was not 100% in ie8 and ie9 I was not detecting the cursor over a selection at all. Googletrans was written under IEv7. I didn't know that zoom processing affected selection processing until I looked at your example 2. However, Firefox selection processing still needs to be fixed up as it is a different algorithm. I'll do this in the next few days but, if you use IE, you can use ja:利用者:Endo999/vector.js as your test file now. Endo999 (talk) 02:40, 9 October 2010 (UTC)
- Yes, from your very good example 2 page I see what you mean by selection difficulties. I'll see what I can do and get back to you. Endo999 (talk) 15:46, 7 October 2010 (UTC)
- Correct selection behavior is now in for Firefox in file ja:利用者:Endo999/vector.js. Thanks for your testing and examples. The whole experience allowed me to retest selection behavior in GoogleTrans and bring it up to Asian language standards.Endo999 (talk) 00:46, 10 October 2010 (UTC)
- Firstly I tested with IE. On IE, Function is perfect! *o* . Now I am testing with FF :) --Was a bee (talk) 09:53, 11 October 2010 (UTC)
- Hi, Endo999! I tested various page. I found only one problem. I wrote that at my test page. I don't think this is huge problem. But If possible to fix, it becomes perfect as much as IE. :)
- By the way, during I am testing, I realized that your code can work in almost every Wikimedia wikis by one code. Amazing *o*. I think almost every people may not know this. If you write "How to import GoogleTrans easily by using importScriptURI(http//:.....)" at your documentation, I think it would be good to spread usage of your script. Thank you. ^.^ --Was a bee (talk) 09:37, 12 October 2010 (UTC)
- Firstly I tested with IE. On IE, Function is perfect! *o* . Now I am testing with FF :) --Was a bee (talk) 09:53, 11 October 2010 (UTC)
- Correct selection behavior is now in for Firefox in file ja:利用者:Endo999/vector.js. Thanks for your testing and examples. The whole experience allowed me to retest selection behavior in GoogleTrans and bring it up to Asian language standards.Endo999 (talk) 00:46, 10 October 2010 (UTC)
- Thanks again for your great testing there. I will fix this problem in the next day or two and get back to you. It probably has to do with the parsing of the Japanese line of text by my Javascript. Endo999 (talk) 14:57, 12 October 2010 (UTC)
- I have fixed up the Firefox problems with Selection and spaces in text. Thanks so much again for your rigorous testing, which I would not have been able to do myself. Please tell me if the fixes do not fix the space selection problem, or that any other items need to be done so that GoogleTrans can be useful for Japanese speakers. My congratulations to you on being able to converse in English, German, and Japanese. I can only read French or Spanish. Writing or speaking in those two tongues is hard for me. Endo999 (talk) 12:51, 15 October 2010 (UTC)
- Two provisos on Firefox selection processing for ja|zh languages with GoogleTrans are:
- 1) If part of a phrase is selected and the cursor is over another part of the phrase (not selected), the selection is translated, not the phrase.
- 2) If the cursor is over a space (for ja|zh languages) then the selected text will not be detected. If the cursor is over a character or punctuation mark (except space) within the selection, then it will be detected.
- Due to the strange detection scheme I have implemented for Firefox, I am unable to fix these two above problems. They shouldn't be too hard to live with.
- Endo999 (talk) 21:54, 15 October 2010 (UTC)
![](http://upload.wikimedia.org/wikipedia/commons/thumb/5/54/TranslationGadget.gif/220px-TranslationGadget.gif)
- Thank you very much for your effort Endo999! Your explanation - "in what type of situation, what type of phenomena happens" - is very helpful. Though I am so lazy, now I'm slowly writing documentation in Japanese (draft). Thanks! --Was a bee (talk) 13:36, 17 October 2010 (UTC)
- Great animated GIF! I just put it on my help page User:Endo999/GoogleTrans. (After I upload all the changes, probably later this week, to production, I'll go ahead and update the help page and also put a link in to your documentation). Endo999 (talk) 17:48, 17 October 2010 (UTC)
- I have updated the production copy of GoogleTrans with the Japanese selection/Zoom selection changes. Thanks once again for your great testing. Is there any chance you can now recommend to a Japanese administrator that GoogleTrans be put onto the Japanese gadget list? I have asked before but have not received a reply before. Endo999 (talk) 00:49, 20 October 2010 (UTC)
- Of course. I want to propose this as gadget. Though I can not predict result of review process. Anyway before proposing it, I have to write documentation in Japanese. And after wrinting, I will propose that. Review process need at least 1-2 weeks. --Was a bee (talk) 12:24, 22 October 2010 (UTC)
- Thanks very much once again Was a bee. I understand your reservations on Google that you emailed me. I have a long term goal to make GoogleTrans as useful for the Wikipedian as possible and your testing and suggestions have made the tool useful for East Asian languages. Thanks a lot. Most of the changes will go into the open source version which is talked about on the Help page. Endo999 (talk) 17:11, 22 October 2010 (UTC)
- Of course. I want to propose this as gadget. Though I can not predict result of review process. Anyway before proposing it, I have to write documentation in Japanese. And after wrinting, I will propose that. Review process need at least 1-2 weeks. --Was a bee (talk) 12:24, 22 October 2010 (UTC)
The Signpost: 25 October 2010
- News and notes: Mike Godwin leaves the Foundation, ArbCom election announced
- In the news: Good faith vs. bad faith, climate change, court citations, weirdest medieval fact, brief news
- WikiProject report: Nightmare on Wiki Street: WikiProject Horror
- Features and admins: The best of the week
- ArbCom interview: So what is being an arbitrator actually like?
- Arbitration report: Case closes within 1 month
- Technology report: Bugs, Repairs, and Internal Operational News
The Signpost: 1 November 2010
- In the news: Airplane construction with Wikipedia, lessons from the strategy project, logic over rhetoric
- WikiProject report: Scoring with WikiProject Ice Hockey
- Features and admins: Good-lookin' slugs and snails
- Arbitration report: Arb resignation during plagiarism discussion; election RfC closing in 2 days
- Technology report: Foundation office switches to closed source, secure browsing, brief news
The Signpost: 8 November 2010
- News and notes: Second Wikipedian in Residence, {{citation needed}} for sanity
- WikiProject report: WikiProject California
- Features and admins: No, not science fiction—real science
- Election report: The countdown begins
- Arbitration report: No cases this week; Date delinking sanctions reduced for one party; History ban extended
- Technology report: Bugs, Repairs, and Internal Operational News
The Signpost: 15 November 2010
- News and notes: Fundraisers start for Wikipedia and Citizendium; controversial content and leadership
- WikiProject report: Sizzling: WikiProject Bacon
- Features and admins: Of lakes and mountains
- Dispatches: A guide to the Good Article Review Process
- Arbitration report: No cases this week; Amendments filed on Climate Change and Date Delinking; Motion passed on EEML
- Technology report: Bugs, Repairs, and Internal Operational News
The Signpost: 22 November 2010
- News and notes: No further Bundesarchiv image donations; Dutch and German awards; anniversary preparations
- Book review: The Myth of the Britannica, by Harvey Einbinder
- WikiProject report: WikiProject College Football
- Features and admins: The best of the week
- Election report: Candidates still stepping forward
- Arbitration report: Brews ohare site-banned; climate change topic-ban broadened
- Technology report: Bugs, Repairs, and Internal Operational News
The Signpost: 29 November 2010
- In the news: Fundraising banners continue to provoke; plagiarism charges against congressional climate change report
- WikiProject report: Celebrate WikiProject Holidays
- Features and admins: The best of the week
- Election report: Voting in full swing
- Arbitration report: New case: Longevity; Biophys topic ban likely to stay in place
- Technology report: Bugs, Repairs, and Internal Operational News
The Signpost: 6 December 2010
- News and notes: ArbCom tally pending; Pediapress renderer; fundraiser update; unreferenced BLP drive
- WikiLeaks: Repercussions of the WikiLeaks cable leak
- WikiProject report: Talking copyright with WikiProject Copyright Cleanup
- Features and admins: Birds and insects
- Arbitration report: New case: World War II
- Technology report: Bugs, Repairs, and Internal Operational News
The Signpost: 13 December 2010
- Rencontres Wikimédia: Wikimedia and the cultural sector: two days of talks in Paris.
- WikiProject report: WikiProject Algae
- Features and admins: The best of the week
- Election report: The community has spoken
- Arbitration report: Requested amendment re Pseudoscience case
- Technology report: Bugs, Repairs, and Internal Operational News
The Signpost: 20 December 2010
- News and notes: Article Alerts back from the dead, plus news in brief
- Image donation: Christmas gift to Commons from the State Library of Queensland
- Discussion report: Should leaked documents be cited on Wikipedia?
- WikiProject report: Majestic Titans
- Features and admins: The best of the week
- Arbitration report: Motion passed in R&I case; ban appeals, amendment requests, and more
- Technology report: Bugs, Repairs, and Internal Operational News