[wp-polyglots] Translation of Kubrick theme

[Nikolay Bachiyski]

2008/1/15, Milan Dinić <liste at srpski.biz>:
> I read this article on SVN Book, but from my understanding, those examples
> there are not same as WordPress, in mean of use branches and trunk
> directory. Thats why I'm asking here.
>
> I checked some language repositories ( e.g. Bulgarian) and I understood that
> use of branches and tags is:
> in branches we put latest files from current branch (e.g. currently in 2.3
> we put 2.3.2 and if there appears new version we put it there); if developed
> is moved to new branch ( e.g. 2.4), we leave this folder with latest version
> from current branch (e.g. in 2.2 that would be 2.2.3).
>
> In trunk we put latest development, so it should be same as latest branch
> folder.
>
> Is this correct?

Not exactly. The latest branch folder and trunk (current development)
are not the same thing.

Here is how it goes:

The current development is done in trunk. When version 2.3 was
released,  trunk was copied into branches/2.3 and 2.4 development
continued in trunk. The 2.3 was used to accomodate the bug-fixes for
the 2.3 series, for eTodayxample the 2.3.1 and 2.3.2 version were
built from the 2.3 branch.

Thus both current development was able to advance, adding new,
unstable, features and the 2.3 series could live their own life of bug
and security fixes.

In light of the translation process, it is best just to replicate the
wordpress branch structure in your repository, so that you can
translate different versions in parallel. For example, I am
translating 2.3.2 in bg_BG/branches/2.3 and the current 2.5 source in
bg_BG/trunk.

Nikolay.

>
> 2007/10/23, Nikolay Bachiyski <nbachiyski at developer.bg>:
> >
> > 2007/10/20, एस्.के <skichu at gmail.com>:
> > > Hi friends,
> > >
> > > I have translated the strings of Kubrick theme into Tamil and uploaded
> > > the .po and .mo files in the following URL:
> > >
> > >
> http://svn.automattic.com/wordpress-i18n/ta_IN/branches/messages/themes/Kubrick/
> > >
> > > 1. Is it ok?
> >
> > Kubrick with lowercase would be better. Also, the branches folder is
> > usually used to create specific branches in there. You can read more
> > on branches in the SVN book [0].
> >
> > >
> > > 2. I find the Kubrick theme files in the WP 2.3 package are not fully
> > > gettexted. Sould I put in the gettexted files found in the SVN
> > > repository also in my local folders? If so, in which main folder? (I
> > > am really confused with the comparative roles of "tags", "branches"
> > > and "Trunk", though codex has some explanation!).
> >
> > The default theme isn't i18n-ed, that's why we have a different
> > version in wordpress-i18n/theme.
> >
> > Regarding the trunk/branches/tags story, read the explanation in [0].
> > If you have further questions, we will be happy to answer :-)
> >
> > >
> > > 3. I have translated all the user-interface strings of the main WP pot
> > > file of 2.3. Is it ok to upload them also?
> >
> > The main pot file translations should go to messages/ta_IN.po.
> >
> > Happy translating,
> > Nikolay.
> >
> > [0]
> http://svnbook.red-bean.com/en/1.4/svn.branchmerge.whatis.html
> >
> > _______________________________________________
> > wp-polyglots mailing list
> > wp-polyglots at lists.automattic.com
> > http://lists.automattic.com/mailman/listinfo/wp-polyglots
> >
> >
>
>
> _______________________________________________
> wp-polyglots mailing list
> wp-polyglots at lists.automattic.com
> http://lists.automattic.com/mailman/listinfo/wp-polyglots
>
>