After few days to test, mess up, fix and use, I get Content Localization to work, and I understand how is the flow and how to make it work fine. Honestly is very easy and is great, but I think is having a very important bug.

My scene is this:

I have one page in english (homepage), and I added a standard HTML module, then I translate page to spanish and automatically, I created the new page, with the new HTML module for the Spanish content, then I deattached module from default language and translate module to spanish, and till now everything is working fine, I have one page with one html module in 2 languages with different content.

Then, I created a second page (Information) and I added Existing module html from page homepage into default language page. Im still fine into this point.

Then, when I made click into "ready for translate", into page settings for the new page, system automatically create the new translated page, but original translated module from home page (spanish), automatically is modified and copy original content from default language HTML module (english)

I hope to be clear with my explanation.

I think this is a bug related with content localization in Dotnetnuke.