Mailing-List: contact ooo-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: ooo-dev@incubator.apache.org
Received-SPF: pass (nike.apache.org: domain of jancasacondor@gmail.com
 designates 209.85.219.47 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <50863A5E.6010801@gmail.com>
References: 
 <CAK2iWdTKh8zAC6CyVt1F=AumY83xtuEZgf9-m3DKrCPFMAgfOg@mail.gmail.com>
	<50852F47.2030908@gmail.com>
	<CAK2iWdRWOXCE43EwD6Pn__Gkw4YQv_FBjCTkphMkBZp3mBPOgg@mail.gmail.com>
	<k63qje$5s6$1@ger.gmane.org>
	<CAK2iWdS=0eHWSg=SmiHzuhNUEdZG-pZ=x4Dqft0UH6u4qU3LVQ@mail.gmail.com>
	<k64bkb$2le$1@ger.gmane.org>
	<50863A5E.6010801@gmail.com>
Date: Tue, 23 Oct 2012 10:43:06 +0200
Message-ID: 
 <CAK2iWdTdKMAfFN=kF_=PmMpmrENUEoVt_LU31zY183yuiwBddQ@mail.gmail.com>
Subject: Re: File: readme.xrm
From: jan iversen <jancasacondor@gmail.com>
To: ooo-dev@incubator.apache.org
Content-Type: multipart/alternative; boundary=f46d04479f0b7af88e04ccb5f55c

--f46d04479f0b7af88e04ccb5f55c
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Juergen:

Is it just textual refresh or also content ?

If it is just textual I can do it, for content I would need input.

jan.

On 23 October 2012 08:34, J=FCrgen Schmidt <jogischmidt@gmail.com> wrote:

> On 10/22/12 10:51 PM, Keith N. McKenna wrote:
> > jan iversen wrote:
> >> +1, That is a very good point !!
> >>
> >> But may we can still write it as plain text, put some tags in, and use
> >> "sed" to split when generating installation sets ?
>
> The readme needs some refresh anyway, we should start to prepare a new
> readme first for all supported platforms and should think later on how
> we can manage it best during the build process and with the translation.
>
> Juergen
>
> >>
> >> janI
> >>
> >> On 22 October 2012 18:00, Keith N. McKenna
> >> <keith.mckenna@comcast.net>wrote:
> >>
> >>> jan iversen wrote:
> >>>
> >>>> As far as I can see on the usage are your assumption correct, and
> there
> >>>> must be other ways to make different readme text platform dependent.
> >>>>
> >>>> Would it not be ok, to have one readme for all platforms, and in the
> >>>> text
> >>>> mention the specics ?
> >>>>
> >>>> janI
> >>>>
> >>>> On 22 October 2012 13:34, J=FCrgen Schmidt <jogischmidt@gmail.com>
> wrote:
> >>>>
> >>>>   On 10/21/12 2:16 PM, jan iversen wrote:
> >>>>>
> >>>>>> There is exactly one file with extension .xrm
> >>>>>>
> >>>>>> main/read_license_oo/docs/**readme/readme.xrm
> >>>>>>
> >>>>>> is there a reason (apart from history) for it being in .xrm or
> >>>>>> could it
> >>>>>>
> >>>>> be
> >>>>>
> >>>>>> converted to e.g. .xhp ?
> >>>>>>
> >>>>>> If so we could get rid of one more conversion tool (read: does not
> >>>>>> need
> >>>>>>
> >>>>> to
> >>>>>
> >>>>>> be converted to new code).
> >>>>>>
> >>>>>>
> >>>>> I am not sure if xhp would be a good option here. But we can probab=
ly
> >>>>> switch to something else. Maybe a common readme file that gets
> >>>>> extended
> >>>>> with platform specific portions from other files. When I remember i=
t
> >>>>> correctly the xrm files contains the content for the readme file an=
d
> >>>>> depending on the platform different content is extracted from this
> >>>>> file.
> >>>>>
> >>>>> Juergen
> >>>>>
> >>>>>
> >>>>>
> >>>>   Jan;
> >>>
> >>> That may indeed be one way to do it. My concern is that users will ge=
t
> >>> frustrated trying to wade through the info for the other platforms
> >>> and just
> >>> not bother with it at all. Of course based on the way they read the
> >>> release
> >>> notes they probably don't read it anyway. Be that as it may do we
> >>> want to
> >>> give them another reason not to read it and possible miss pertinent
> >>> information.
> >>>
> >>> Regards
> >>> Keith
> >>>
> >>>
> >>
> > +1 Works for me.
> >
>
>

--f46d04479f0b7af88e04ccb5f55c--