How to use easiest version control system

When you lost your data or history by crash or accidently saving process, you might be very frustrated. People usually use Dropbox, but Dropbox cannot sync into custom directories, multiple history branches, and massive collaborators. I will introduce intuitive guide to one of version control system 'git', which supports multi-branch, multi-collaborator projects.

The only point people might hesitate may be that git is open-source-based: mostly you are forced to share your sources you uploaded on the git repositories. There is good service which avoid this license: bitbucket, which gives up to 5 free private repositories per user. This service is provided by Atlassian who also provides git client program with intuitive user interface: SourceTree.

First, you should make your repository on the server e.g. bitbucket. Then, you should clone your server repository into a blank directory of your local disk. When you change your local file, the sourcetree app shows what is changed, and you can 'commit' to make a node to the history line. 'push' pushes the nodes to the server and make changes to the server which are shared to all collaborators. If there are conflicts between collaborators, it automatically merges, or you can fix it in your way. When you transfer into another branch, data of the local repository changes, so you should be aware of it.

CBZ File Extension Standard Format Proposal 1207

Terminology

• "can" means permission of additional features
• "should" means mandatory features/ mandatory element in template
• "may" means mandatory features for programmer, but optional element in template.

File Type

• The infrastructural template of a CBZ file is a "Deflated" zip file in which names of all the files are in UFT-8.
• Program developer can add another decompression protocols but should include the protocol above.
• If there is any conflict such as encoding problem, the protocol should be primary.

Archive Structure

• The archive should include "index.xml" which follows XML 1.0 and is encoded by UTF-8.
• The other elements may be JPG, PNG files.
• Any other files can be ignored.

Index Header

• In the XML, tag for "title" of the book should exist.
• XML tags for "subtitle", "author", "tags", "isbn", "publisher", "publish-date", "addition" may exist.
• "series-title" and "volume" should exist if "title" does not exist. In this case, "publish-date" means the date each volume is published.
• The content of "publish-date" should be in "YYYY-MM-DD" format.
• "isbn" can be character string for variations and duplications.
• "addition" means 'additional information', and both "addition" and "author" may include <a> tag for hyperlink.

Index Body

• The body should be embedded in the tag "pages". The whole body can be omitted, and then the default properties are loaded.
• The tag "pages" has an attribute "direction" value of which is allowed for "rtl", "ltr", "btt", "ttb". All allowed direction should be noted. The default value should be "ltr, btt".
• All the image file should be in a stack in which indexed images comes front. If any file is not indexed, the order should be in order of the filenames.
• Tag "page" has attribute "filename" and "number". The tag may be ordered by the "number" and no duplicate "number" exists. The "number" is allowed for any integer. The nonpositive numbers may be used for frontmatters.

Posted with Blogsy