Saturday, December 15, 2012

Enable "Google Latitude" in Korea


UPDATE 2013-06-22: The same features of Google Latitude are now available in the Google+ App, under the "Locations" sidebar. You'll need to enable location sharing to a specific Google+ circle, and your former Latitude friends will have to enable their location sharing to you, but it works much the same. 

UPDATE  2013-02-23: A nice replacement app for Latitude is Backitude, which gives greater control over location updates. This app will only report your location. For your own Location History, you'll need to install a modded version of the latest Maps version with "World Navigation" active. 

UPDATE  2013-02-19: Apparently as of Maps 6.14.2, Latitude is now removed even from the English interface. Buzz among Korean bloggers indicates that, at the moment, the method below must be done while assigned a US-based IP address (i.e. use a proxy or VPN).

===============

Problem:
You want to use Google Latitude to obsessively stalk your Korean boyfriend keep up with your friends, but the version of the Google Maps app (Android)  in Korea doesn't have the Latitude feature.

Solution:
It actually does, but it's disabled in the Korean settings. Here is how to make it work:
  1. Switch the phone's overall system language from Korean to English.
  2. "Settings" -> "Applications" -> "Manage applications" -> Maps
  3. Hit the "Clear data" button
  4. Hit "Uninstall" (if it says it will revert to the factory version, that's fine)
  5. Go to Android Market aka Google Play Store. Reinstall Google Maps.
  6. DO NOT ALLOW IT TO AUTOMATICALLY UPDATE, or you'll have to do this all over again every single time. I suggest changing Play Store's preferences to forbid any/all apps from auto-updating.
  7. Open Maps, Launch Latitude, change settings to enable "Location Reporting" and to allow friends (you) to view that Location Data. "Location History" is unnecessary.
  8. TURN OFF THE PHONE. TURN ON THE PHONE AGAIN, WHILE STILL IN ENGLISH. If you do not do this, Maps will revert to non-Latitude status when you change the language back to Korean.
  9. Now launch Maps again. Verify Latitude is still working.
  10. Change phone's language back to Korean. Done.
Note that although Latitude will not appear in Maps anymore (because it's set back to Korean), the location will still be reporting and be visible to your Latitude friends or your Latitude dashboard. This can be verified by checking the phone's "Running Services."
Note also that this will only succeed in reporting the phone's location. It will not, so long as it is set to Korean, allow you to view your friends' locations.

Now when your boyfriend calls you at 3am, slurredly says he doesn't know where he is, then passes out drunk, you can go fetch him easily. Just be aware that Latitude updates rather infrequently, so the room-salon his location is reporting may only be where he was an hour ago. Thus, you are advised to check the local gutters in a half-mile radius, lest he end up on this site.
Read more ...

Monday, November 12, 2012

Dokdo KakaoTalk theme


Thank god, someone has finally created a Dokdo theme for KakaoTalk. I haven't even installed it, but I'm giving it 5 stars!

(I'm thinking I know where he got the English name "Bruce" from...) 
Read more ...

Saturday, July 14, 2012

Extend SubDownloader beyond 30 days


Problem:
You love using SubDownloader to download a lot of subtitle files for your media collection, but SubDownloader (for Windows) limits you to 30 days. Other versions do not.

Solution:
1) Open run (start menu -> run).
2) Type "regedit" (without ""'s)
3) Registry Editor should be open, press CTRL+F (find for something in registry)
4) Check, under "Look at", only "Keys", uncheck "Values" and "Data". Then also check "Match whole string only"
5) Search for "SubDownloader" (without ""'s)
6) When you find it, there should be folder named "mainwindow" under it. Click on it, then change the value of "size2" into "1861826968.484"

Source: http://forum.opensubtitles.org/viewtopic.php?t=1733
Read more ...

Sunday, June 24, 2012

Right-click on Korean websites that block it


Sometimes you want to copy or highlight text from a Korean blog/website, or right-click to save an image from it, but the site prevents you from right-clicking.

I use this simple add-on for Firefox. One click on this non-obtrusive button in the tool-bar, and the page reloads will full right-click context menu, and easy highlighting of text.

RightToClick :: Add-ons for Firefox

UPDATE: A great and very simple bookmarklet can work on Chrome or Firefox and do the same thing. I just tried it on a Naver blog and worked perfectly. Just drag this to your bookmarks bar:


SourceJS Bookmarklets!: Enable Right-Click on websites that disable it!

I love bookmarklets. Simple, practical, portable, multi-device solutions that should get more credit and should have caught on more than they have.
Read more ...

Thursday, June 21, 2012

Moving from Livejournal (via Wordpress) to -> Blogger, a step-by-step guide


Introduction:

I know many people have had trouble doing this, particularly on the step requiring the Google Blog Converter like this one here. I finally got it to work for me after an entire day and trial and error, so I thought I'd share what worked for me. Hopefully this should help those of you, like me, who are uncomfortable using the command line, and hopefully it can work for you also.

Background:

I had a very large LiveJournal (~700 entries) that I wanted moved to Blogger
But because LiveJournal has no convenient export feature (other than month-by-month, which would have taken forever by hand), I first copied the LiveJournal to WordPress.
So I signed-up for a dummy WordPress blog, and used their "Import" option under the "Tools" setting.
This took quite awhile and a few tries to get it right, so make sure it's done properly before you continue.
From here, you can now "Export" the blog (I just used the default option, exporting entries, comments, etc). as a WordPress-specific .xml file. Save this on your hard drive.

Using Google Blog Converter on the command line:

There is a fabulous online conversion tool to convert between various blog formats, but the problem is that it won't handle files over 1MB. My blog, in WordPress .xml format, was around 7MB. Too big.
So I downloaded the latest .tar.gz source files from here

(Note: ---- here begins what I did in Ubuntu. I have no idea how this would work in Windows or Mac, though it is probably very similar----)

In Ubuntu, I right-clicked the downloaded file and chose "Extract Here". The file was extracted into a folder containing all the necessary blog converters. 
Now then, I opened my terminal.
First we need to tell the terminal to "change directory" into the folder we just created (when we extracted the .tar.gz). So for me, I needed to input:
cd ~/Downloads/google-blog-converters-r89
Note that you may need to change the last part depending on the folder's title (which will depend on which release version you download)
Next, just for simplicity and to follow the Readme file as closely as possible, I went back to my desktop and moved my WordPress-exported blog file (the .xml file) into the folder called "samples" inside the "google-blog-converters-r89" folder (the one that was created when I right-clicked and extracted the .tar.gz download.
Now then, back in the terminal, I typed:
bin/wordpress2blogger.sh samples/myjournalsample-wordpress.xml
Of course, you can substitute whichever blog converter you want in the first part (to find the correct name, look inside the "bin" folder inside the "google-blog-converters-r89" folder). And the second part should be the name of your WordPress-exported file. Mine was "myjournalsample-wordpress.xml"

Now if everything worked well, the terminal should chug away working and working, eventually stopping with a huge chunk of text visible (part of your entries). When that's done, you can move to the next section "Importing to Blogger." If it didn't work, you might have this problem that I ran into, featured below.

My problem using LiveJournal via WordPress

This step in the terminal would return an error, claiming the file is not a real WordPress document. It turns out that the reason was that the file included a bunch of LiveJournal metadata mixed-in with the WordPress data that couldn't be processed by the converter. So I had to remove these parts. I chose to use the "Find / Replace" feature of LibreOffice.

However, before I could do this, I had to add a special extension to LibreOffice to allow me to remove all instances automatically. I downloaded the "Alternative dialog Find & Replace for Writer" and installed it to LibreOffice using the "Extensions Manager" in LibreOffice's "Tools" menu (using the "Add..." button). I then restarted LibreOffice.

Once this extension was installed, I could "Find / Replace" what I needed. As it turns out, all of the ""  tags needed to be removed, along with all the meta data information (left over from the import from LiveJournal) stored between them. So, using the new extension's "Find / Replace" feature, I input this string in the "Find" box:
[::BigBlock::]
The "big block" regular expression can be found in the "Extended" menu of the dialog box also.

Then, leaving the "Replace" field blank, I clicked "Replace All"

This took awhile, as my blog was over 2000 pages in LibreOffice. But it worked-- all these tags and the unprocessable data between them were removed. 

Then I saved the document as plain text in LibreOffice, closed LibreOffice, and renamed the document extension from ".txt" -> ".xml" (I didn't do an actual conversion in LibreOffice because it seemed to keep locking up on me.)

Importing to Blogger

Earlier I had done this command:
bin/wordpress2blogger.sh samples/myjournalsample-wordpress.xml
It should work, leaving the resulting output file in your terminal window. But how do you get it out of there? Turns out, it's quite simple. Run the command again with a small addition, telling the terminal to dump the converted blog into a text file.

bin/wordpress2blogger.sh samples/myjournalsample-wordpress.xml > hopefully.txt 

Adding that last part, the "> hopefully.txt" meant that the dump of converted blog data would be written to a file called hopefully.txt

Finally I am done with the Terminal!

Now I go to my file manager and find this file, which for me was just inside the "google-blog-converters-r89" folder. I renamed it "hopefully.xml" (since that's really what it is) and went to Blogger.

I set-up a new blog there, went to the Options page, chose "Import" and selected the file.
It seemed to be uploading Ok for about 10 minutes....... but then.......... ERROR! Cannot Import the Blog!


Don't panic. After closing out of that dialog, I discovered that in fact it had imported all ~700 of my entries, WITH COMMENTS!!!!! They just remained unpublished.

The last step was to manually publish them all, made easier by displaying 50 posts at a time on the Blogger Posts page (you can display 100 at a time, but batch operations only work up to 50). So by displaying 50 entries per page, I had about 13 pages of blog posts, unpublished.
All that remained was to click the top-left checkbox to select all entries on the page, and click "Publish" and let it post them! Then move to the next 50, repeat...... etc........etc....... it took about just 5 minutes.

Now they are all posted on Blogger! All in their original dates! All with original comments! FINALLY

Conclusion

This was an incredibly difficult and mind-boggling process for me, so don't give up. I'm sure there is an easier or more efficient way than I've done it, but I surely didn't see anything online about it. Hopefully something in this guide can help you get out of a rut. Good luck!

Read more ...