Keep track of changes

[GoogleCodeExporter]

Add a mechanism or rule to keep track of changes in the translation sources.

Original issue reported on code.google.com by haertl.mike@gmail.com on 19 Feb 2009 at 1:21

[GoogleCodeExporter]

Additional thoughts:
The linked in sources for the guide are from the /trunk branch of the project 
instead
the brances/1.0. I guess this might lead to problems (e.g. with features for 
1.1.x
already documented in /trunk but not available in any 1.0.x release) Shouldn't 
we
create the same trunk/branches structure for the docs?

Original comment by haertl.mike@gmail.com on 19 Feb 2009 at 1:31

[GoogleCodeExporter]

changed to 1.0 branch. also added syncguide command to help detect the source 
change.

Original comment by qiang.xue on 20 Feb 2009 at 6:49

• Changed state: Fixed

[GoogleCodeExporter]

I tried the syncguide command and, among other valid changes, found the 
following
where my saved originals from trunk have higher revisions. So far I have double
checked basics.* and while the first three only differs in revision and 
timestamp,
basics.workflow had a link removed at line 44 in revision 323. Seems like I 
should
stick to the higher revisions for now.

        basics.application.txt: outdated (source: 616, target: 626).
                basics.mvc.txt: outdated (source: 418, target: 419).
               basics.view.txt: outdated (source: 409, target: 416).
           basics.workflow.txt: outdated (source: 169, target: 323).
          caching.fragment.txt: outdated (source: 245, target: 323).
          caching.overview.txt: outdated (source: 461, target: 468).
              database.dao.txt: outdated (source: 365, target: 367).
               form.action.txt: outdated (source: 625, target: 626).
                form.model.txt: outdated (source: 595, target: 598).
                form.table.txt: outdated (source: 463, target: 468).
   quickstart.installation.txt: outdated (source: 349, target: 359).
               topics.i18n.txt: outdated (source: 580, target: 584).
        topics.performance.txt: outdated (source: 568, target: 571).

/Tommy

Original comment by triboe@gmail.com on 21 Feb 2009 at 12:08

[GoogleCodeExporter]

Never mind. I made another svn update and it seems to be fixed now. All 
differences
in higher revisions now (the following was omitted from my previous msg):

          basics.component.txt: outdated (source: r679, translation: r584).
         basics.controller.txt: outdated (source: r713, translation: r598).
          basics.namespace.txt: outdated (source: r718, translation: r169).
               database.ar.txt: outdated (source: r684, translation: r546).
              database.arr.txt: outdated (source: r678, translation: r626).
                 form.view.txt: outdated (source: r708, translation: r297).
                     index.txt: outdated (source: r686, translation: r440).
      quickstart.first-app.txt: outdated (source: r716, translation: r446).
               topics.auth.txt: outdated (source: r651, translation: r564).
              topics.prado.txt: outdated (source: r417, translation: r416).

/Tommy

Original comment by triboe@gmail.com on 21 Feb 2009 at 12:17

[GoogleCodeExporter]

Qiang, it seems like the contents of trunk vs bransch need to be 
double-checked. More
specific, the downgrades I mentioned earlier today.

/Tommy

Original comment by triboe@gmail.com on 21 Feb 2009 at 1:48

[GoogleCodeExporter]

Agree with you. I just switched the source back to trunk.

Original comment by qiang.xue on 21 Feb 2009 at 1:52

[GoogleCodeExporter]

Sorry to say, I don't think that will solve the mismatch problem. I think the
versions of the 13 files I listed needs (needed) to be selected from trunk, the 
rest
should  have been ok from branch (I think).

Now for instance, ver 718 of source/basics.namespace has become ver 169 after 
the
switch back to trunk. It also seems like the syncguide tool doesn't detect 
this, I
think it compares source files to files in the subdir containing already 
released
translations.

Original comment by triboe@gmail.com on 21 Feb 2009 at 4:10

[GoogleCodeExporter]

I think it's fine to use trunk. I am periodically merging branch 1.0 to trunk. 
So
after the next merging, you will see the namespace file is the latest in trunk. 
Code
in trunk is relatively stable compared with 1.0 branch. That's why I switched 
back to it.

Original comment by qiang.xue on 21 Feb 2009 at 4:23

[GoogleCodeExporter]

I've done some tweak to make yiic happily live in every environment in r468.

Original comment by haertl.mike@gmail.com on 21 Feb 2009 at 2:47

[GoogleCodeExporter]

syncguide is complaining now, that source file toc.txt has no revision info.

Original comment by haertl.mike@gmail.com on 21 Feb 2009 at 2:51

• Changed state: Accepted

[GoogleCodeExporter]

I still don't understand all the events I saw happen yesterday. From _where_ 
did I
get the higher rev # I already used for translation several days ago? If _all_
updates first goes to bransch, that shouldn't have happened. I agree we should 
wait
for things to stabilize. Hopefully it does before the 1.03 translations are 
grabbed
for release.

The tweaked yiic worked for me (had to remove lines/clean up).
I expect toc.txt to be fine after merge to trunk.

What I said about syncguide subdir usage in #c7 was wrong. Still no explanation 
why
it doesn't detect the 169<>718 mismatch (i.e. not 718<>169).

Original comment by triboe@gmail.com on 21 Feb 2009 at 3:58

[GoogleCodeExporter]

Original comment by qiang.xue on 21 Mar 2009 at 5:39

• Changed state: Fixed