Even if you don't get textual diffs, merely keeping a history is a good
start to preserving documents.

And, btw, XML is not really any better than binary for doc storage because
you generally cannot merge it.... One of the reasons I hate those IDEs that
store project files in XLM.

On Tue, Dec 30, 2014 at 5:58 AM, Maurizio Vitale <mrz....@gmail.com> wrote:

>
>
> On Tue, Dec 23, 2014 at 1:55 PM, Florian Coste <fcost...@gmail.com> wrote:
>
>>  Hello,
>>
>> Thank you for your answer ;) Other people said me yesterday on Git irc
>> channel that .odt files are binary, and Git will not handle them correctly.
>> I don't know DocBook XML, or Markdown, but after some research, I don't
>> think this format will be easy for me to use it. Others people advised me
>> start learning Latex. It's a good advice I think.
>>
>> But, even with Latex, I think that Git will make diff between textual
>> files, and I would only need to have a graphical diff tool. I will keep
>> searching it ;)
>>
>
> It does give you textual diffs, but this has always been good enough for
> me.
> With LaTeX there're tools that take two version (which might come from two
> different git commits) and generate a LaTeX document that contains change
> bars and strike-out for deleted text (latexdiff is one of them, see
> https://www.sharelatex.com/blog/2013/02/16/using-latexdiff-for-marking-changes-to-tex-documents.html
> ).
> This is useful for reviewing multiple revisions, as you can generate pdf
> and collect comments added to it.
>
> As soon as you have to collaborate with people, I've found that LaTeX is a
> problem, though (unless everybody is already happy with it and you can
> guarantee that any new project member will be). At that point it is just
> easier to use version tracking inside Microsoft Office or Open Office.
>
>>
>> Thank you so much for your help ;)
>> Florian
>>
>>
>>
>> 2014-12-23 16:57 GMT+01:00 Gergely Polonkai <gerg...@polonkai.eu>:
>>
>>> Hello,
>>>
>>> .odt files (I assume you are talking about OpenOffice documents) are
>>> binary, and as such, Git doesn't handle them very well. If you want to
>>> manage such documents in Git, you must use a textual format, such as
>>> DocBook XML or Markdown.
>>>
>>> Now that we are here, to answer your other questions, yes, I do manage
>>> my tech papers, novels, API documentations and pretty much every text is
>>> Git. But once again, these are textual files (most of them are DocBook
>>> XMLs). Even the Pro Git book's sources are versioned in Git :-)
>>>
>>> Best,
>>> Gergely
>>> On 23 Dec 2014 16:44, "Florian Coste" <fcost...@gmail.com> wrote:
>>>
>>>> Hi,
>>>>
>>>> I'm a recently user of Git. I think it's a great tool for development
>>>> project ;) I've already used it on university project, but, in practise,
>>>> we've worked without it, badly...
>>>>
>>>> Recently I started to read documentation because I wanted to join open
>>>> source projects on Github. And I had one idea. I'm wondering if Git could
>>>> be use for other things ? For example, I would like to use Git for my CV's
>>>> redaction. Indeed, it would be interesting to have different versions of my
>>>> CV, and having the possibility to get an older version.
>>>>
>>>> Have you no-traditional use of Git ? Which ? What do you think about my
>>>> project ? Git will need process .odt files. Maybe, it would be better to
>>>> use graphical uses for making diff between two versions, don't you think ?
>>>>
>>>> Thank you so much.
>>>> Nairolf
>>>>
>>>> --
>>>> You received this message because you are subscribed to the Google
>>>> Groups "Git for human beings" group.
>>>> To unsubscribe from this group and stop receiving emails from it, send
>>>> an email to git-users+unsubscr...@googlegroups.com.
>>>> For more options, visit https://groups.google.com/d/optout.
>>>>
>>>  --
>>> You received this message because you are subscribed to the Google
>>> Groups "Git for human beings" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to git-users+unsubscr...@googlegroups.com.
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>>  --
>> You received this message because you are subscribed to the Google Groups
>> "Git for human beings" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to git-users+unsubscr...@googlegroups.com.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>  --
> You received this message because you are subscribed to the Google Groups
> "Git for human beings" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to git-users+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups "Git 
for human beings" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to git-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to