Bhuvaneswaran Arumugam wrote:
>>> Index: subversion/po/pt_BR.po
>>> ===================================================================
>>> --- subversion/po/pt_BR.po (revision 21268)
>>> +++ subversion/po/pt_BR.po (working copy)
>>> @@ -4,7 +4,7 @@
>>> #
>>> msgid ""
>>> msgstr ""
>>> -"Project-Id-Version: subversion 1.1.0\n"
>>> +"Project-Id-Version: subversion trunk\n"
>>> "Report-Msgid-Bugs-To: dev@subversion.tigris.org\n"
>>> "POT-Creation-Date: 2006-08-23 13:50-0500\n"
>>> "PO-Revision-Date: 2004-07-26 19:19-300\n"
>>
>> Either we should remove the version from this value completely, or we
>> should add it to the release-process documentation that updating all of
>> these is necessary at the same time as changing svn_version.h.
>
> Oh ok, thank you.
> So, I guess it'd be good to update the release-process document in
> "Creating and maintaining release branches" section, unless we know the
> purpose of including "Project-Id-Version" field in these files!
Ideally, we need someone wise in the ways of translation to explain how
important this field is. I have seen some comments which imply it is
optional, which makes me wonder if the best solution is to simply delete
it - after all, no point in maintaining it if nothing makes use of it.
If it is seriously used, knowing what for can help us decide whether we
bother to put specific versions there, or just identify the branch:
i.e., "1.4.x", "1.5.x", etc.
Max.
Received on Sun Aug 27 22:34:26 2006