mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Kyle Moffett <mrmacman_g4@mac.com>
To: Tony Luck <tony.luck@gmail.com>
Cc: Matt Mackall <mpm@selenic.com>, Greg KH <gregkh@suse.de>,
	Matthias Schniedermeyer <ms@citd.de>,
	Jesper Juhl <jesper.juhl@gmail.com>,
	Tsugikazu Shibata <tshibata@ab.jp.nec.com>,
	LKML Kernel <linux-kernel@vger.kernel.org>,
	m-ikeda@ds.jp.nec.com, git@vger.kernel.org
Subject: Re: [RFD] Documentation/HOWTO translated into Japanese
Date: Thu, 14 Jun 2007 20:29:09 -0400	[thread overview]
Message-ID: <29741172-099F-499B-8A73-A85C6360129D@mac.com> (raw)
In-Reply-To: <12c511ca0706111038j37e188b6n2677b1789d14de23@mail.gmail.com>

On Jun 11, 2007, at 13:38:10, Tony Luck wrote:
>> I'd rather have a single file, marked "Japanese" (in Japanese),  
>> that had pointers to current translations. These will always be at  
>> least as current as whatever we have in the tree, if not more so.  
>> Especially when someone is trying to figure out how to work based  
>> on the year-old kernel their embedded vendor gave them.
>
> Knowing whether a translation is current or not would be useful ...  
> perhaps the translated files could include the GIT blob SHA1 of the  
> version they were translated from (and some human readable version  
> string too :-) This would allow someone reading the documentation  
> to know whether is really was current.  If it isn't, it provides an  
> easy path to see what changed in the source document since the  
> translation was made. This same diff should lighten the load for  
> people maintaining the translation.

Well, actually, if you're going that route then extend GIT to have  
support for "related" files.  Essentially you should be able to add  
metadata to a git tree which says: "files $SHA1-$PATH1, $SHA2-$PATH2,  
[...], are related".  Then there would be a "git list-related"  
command with a "--mismatch" option which would list paths for which  
$SHA1 doesn't correspond to $PATH1 or $SHA2 doesn't correspond to  
$PATH2, etc.  Some clever updating of related-status during commit/ 
clone/pull/etc could store information in the index about whether or  
not any given file is up-to-date with respect to its co-related files.

For translations, when the English version of a document is updated  
it will automatically result in a "mismatch", allowing translators to  
do a simple git-diff and see what happened.  Likewise, if the  
Japanese document is updated without changing the relationship then  
it might mean that somebody should see what changed and update the  
English version as well.  If you determine that the change was  
irrelevant for the other language (spelling/grammar fixes, etc), then  
you just update the relationship and commit that change.

It would probably be pretty trivial to implement a prototype using a  
'.gitrelated' file in the root of the git tree, although better  
integration with the index would really speed handling with lots of  
related files; instead of linear searching just iterate over the  
prepared-during-checkout "out-of-date" list.

Cheers,
Kyle Moffett


  reply	other threads:[~2007-06-15  0:29 UTC|newest]

Thread overview: 52+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-10 11:48 Tsugikazu Shibata
2007-06-10 12:03 ` [RFD] Documentation/stable_api_nonsense.txt " IKEDA Munehiro
2007-06-10 12:23   ` Jan Engelhardt
2007-06-10 17:00   ` Alistair John Strachan
2007-06-11  1:33     ` IKEDA Munehiro
2007-06-10 12:24 ` [RFD] Documentation/HOWTO " Jesper Juhl
2007-06-10 12:29   ` Jan Engelhardt
2007-06-10 14:25   ` IKEDA Munehiro
2007-06-10 16:22   ` Greg KH
2007-06-10 16:34     ` Tsugikazu Shibata
2007-06-10 16:46       ` Jan Engelhardt
2007-06-11  0:25         ` Adrian Bunk
2007-06-10 17:52     ` kconfig .po files in kernel tree? [Was: Documentation/HOWTO translated into Japanese] Sam Ravnborg
2007-06-10 18:35       ` Jan Engelhardt
2007-06-10 19:04         ` Sam Ravnborg
2007-06-10 22:13         ` Matt Mackall
2007-06-10 18:58       ` Rene Herman
2007-06-10 21:13         ` Rene Herman
2007-06-10 23:59         ` Denis Vlasenko
2007-06-11  0:14           ` Adrian Bunk
2007-06-11  9:28             ` Rene Herman
2007-06-11  0:56           ` Paul Mundt
2007-06-11  7:46             ` Denis Vlasenko
2007-06-11  8:34               ` Paul Mundt
2007-06-11  9:08             ` Rene Herman
2007-06-10 19:41       ` Diego Calleja
2007-06-11  0:21         ` Adrian Bunk
2007-06-11  0:29       ` Adrian Bunk
2007-06-11  6:02       ` Greg KH
2007-06-10 17:56     ` [RFD] Documentation/HOWTO translated into Japanese Matthias Schniedermeyer
2007-06-11  6:07       ` Greg KH
2007-06-11  7:24         ` Matthias Schniedermeyer
2007-06-11 13:43         ` Matt Mackall
2007-06-11 17:38           ` Tony Luck
2007-06-15  0:29             ` Kyle Moffett [this message]
2007-06-12  0:55         ` Tsugikazu Shibata
2007-06-12  1:07           ` IKEDA Munehiro
2007-06-12  7:44           ` Junio C Hamano
2007-06-12  8:44             ` IKEDA Munehiro
2007-07-03 21:32               ` Rob Landley
2007-06-13 14:18         ` Pavel Machek
2007-06-13 20:37           ` Greg KH
2007-06-13 20:43             ` Pavel Machek
2007-06-10 22:08 ` Matt Mackall
2007-06-11  2:55 ` KAMEZAWA Hiroyuki
2007-06-11  6:09   ` Greg KH
2007-06-11  8:45     ` Hiro Yoshioka
2007-06-11 10:21   ` Qi Yong
2007-06-11 10:46     ` KAMEZAWA Hiroyuki
2007-06-11 11:16       ` Rene Herman
2007-06-11 11:28         ` KAMEZAWA Hiroyuki
2007-06-11 11:34           ` Rene Herman

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=29741172-099F-499B-8A73-A85C6360129D@mac.com \
    --to=mrmacman_g4@mac.com \
    --cc=git@vger.kernel.org \
    --cc=gregkh@suse.de \
    --cc=jesper.juhl@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=m-ikeda@ds.jp.nec.com \
    --cc=mpm@selenic.com \
    --cc=ms@citd.de \
    --cc=tony.luck@gmail.com \
    --cc=tshibata@ab.jp.nec.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®