Release 2: Contribution to open source project

In release 2, we are asked to contribute to an open source project. I choose Brave browser to make some contributions. About this project, click my previous blog: https://qchen102.blogspot.ca/2018/03/brave-browser-for-laptop.html


Build the Project

It's easy to build the project. Download the package from Brave github. CD to browser-laptop. Then run several commands:

'npm install'
'npm run watch'
'npm start'

Then the project is successfully built.

Here is the interface of Brave:


Using in my language

After I installed it, I want to know if it supports in my language. So I set it to Chinese. It does suppot Chinese, but I found some of strings haven't been translated yet.



Well, it's interesting to translate it.

Translate..

I find all languages file are located in "app/browser/extensions/brave/locales". There're 26 folders. Each of them has different language. US English is in "en-US". Japanese is in "ja-JP". Simplified Chinese is in "zh-CH". This is the part I need to work on.

Expand the folder, there're several files.

Most of the properties for browser can be found here. Click the file, it looks like this:

So I could find the specific properties and translate them.

To find the properties, we could go to Brave browser, go to where we want to translate, right click then click "Inspect Element".

Then we can easily find the properties' id. For example, I want to translate the string below, I find the property' id is "spellCheckLanguage".



After I get the property's id, I go to the files with properties and search this property. When I find it, I can translate it.


Reload the browser and check it..

Got it...

Here're some views of my translation.

Before:                                                                                                  After:


Before:                                           After:


Before:

After:


Now it looks much better.






Comments

Post a Comment

Popular posts from this blog

OSD - Release 03

Image
In this release, I'm going to find projects which I'm interested. In this release, I'm going to fix some bugs if possible. I hope to find projects to keep contribute not only for release but also in the future. I really like Android projects. So I want to find some Android projects to work on. I Googled 'Android open source project', and I found some articles introduce it. Link: https://medium.mybridge.co/38-amazing-android-open-source-apps-java-1a62b7034c40 I tried some of the projects. I reviewed some issues information. At last I choose Leafpic to contribute. Leafpic Introduce Leafpic is an Android open source project provide some basic features for photos viewing, managing, editing and sharing. It's a light application running very smooth in Android devices. It has Simple interface and I like it very much. It has around 1300 commits, 9 releases and 50 contributors. It's a good project for our practices.  Potential Bugs to Fix 1. Leafpic: Rat
Read more

OSD600 - Lab 6: Fixing URL bug in Brave browser

Image
In this lab, we are going to fix URL searching bug in Brave browser. Although each browser has its method to handle URL parsing, we hope Brave browser can get the same searching result as those famous browser does. For me, I like Chrome browser the best. So I'm going to fix Brave URL bug to make it have the same result as Chrome does. Here's the link of our lab: https://wiki.cdot.senecacollege.ca/wiki/OSD600_and_DPS909_Winter_2018_Lab_6 After a few try, we get result from Chrome and Brave. They have different results in some way. The results are different in URLs which have space inside URL. Then I compare the URL results of them. Chrome: Brave: So I think Brave doesn't replace the space in URL like Chrome does. So Brave separates the URL into 2 parts and search them through searching engine. Our main purpose is to replace it to "%20" in order to let it work in Brave browser. First we know, Brave already handle the trim function. When Brave get
Read more

Studying for open standard

Image
In recent couple of classes, we learned about the standard of programming world. There're thousands of programmers in the world. All of them have different coding style. Before a language become a "language", it needs a "standard" so that the language developers can design it with those standard rules. That's why Java looks like this and Javascript looks like that. But standard is not unchangeable. Programming world is developing fast. Many languages need to be upgrade too. In this lab, make "reverse" for example. Long time ago reverse is not a standard in Javascript language. Programmers want to reverse array so they designed this function and made it work without bug. They name it, use it again and again, fix all bugs they found. Then more and more programmers used it. Finally, it became standard in Javascript and many other language such as Java. One of the way to find bugs is to write a tester. In this lab, we will test ECMA262. ECMA262 is a
Read more