Hi Cor,
thank you for your input!
Cor Nouws wrote:
> Hi all,
>
> Related to Issue 20386, I've finaly made a first draft
of the specs for
> this feature.
Yes, it's good starting point.
> I've some questions, that I posted to Andreas Martens
some weeks ago.
> But it seems he is on holiday. Therefore a repost on
this list.
I'm back again
>
> Writing this first draft was mot a quick go (lots of
information,
> checks) however, well guided by the template and the
Wiki. Compliments!
>
> Before submitting info to issueTracker, I write
seperately, because I'm
> only able to meet a part of the requirements.
It's no problem to submit a draft to issue tracker, don't
hesitate to
attach your first draft to issue 20386.
> Plus my knowlegde of some aspects is limited, so it
will take
> considerable investments to specify more details. For
example (enough
> place for) strings, file formats, ...
Let's clarify these things later. The first and most
important questions
are:
1. Do we want this feature?
2. Do we have a developer for implementation?
I think your spec. draft is precise enough to discuss these
questions.
If we have answered both question with yes, we should spend
more work to
the specification to get it perfect.
Okay, first question:
Do we want these feature?
On the one hand it has been on our wish list for OOo2.0 but
on the other
hand it got a low priority (5). Why? It's a known feature
and would help
us to improve our interoperability with other office suites.
But I've
seen only few documents which make use of this feature. The
request for
it has been low.
This changed a little bit because you showed your interest
and spent
your time to create this specification, so there must be a
request for
this feature at least from your side. Even I will not
implement it by
myself, I will support anyone who volunteers for it.
Second question:
Do we have a developer for implementation?
I don't, but I'm very interested to attract developers for
our word
processing engine. If a volunteer has overcome the obstacles
of
compiling and building our source code I will be pleased
with showing
him the secrets of the Writer code
>
> Currently, the full list in section 5 Open Issues of
the specs reads:
> 1 - i-team members (I can
askfor QA-representative dev qa.OOo. But
> finding a developer is harder for me.)
Yeah, definitely we need to find a developer...
> 2 - Current choise is not to support setting
'Justified' – discussion
> needed.
Justification brings more complexity to the feature, so
maybe we should
start without it.
> 3 - No detailed information about exchanging with other
file formats
> available yet
If we got an implementation in Writer the filter experts
will adopt it
very quickly.
> 4 - Strings for German not yet filled in
This should be resolvable.
> 5 - Not checked if strings (also that of moved controls
!) for different
> languages (incl. CJK) fit
> 6 - Section for File format is made up with limited
knowledge of the
> file format and (automatic-) styles format!
> 7 - Not known yet if the ODF file format supports this
page property.
No, but if we implement it, we will sent a proposal to the
OASIS committee.
>
> Nevertheless, my contribution might be useful.
Yes, of course!
> If so, I will be pleased to do some next steps, within
my capabilities.
> For example, discussing (discuss OOo, with informing others
that were
> involved at users OOo) if Justifying is usefull or not (I
skipped it
> because I think it adds extra complexity (interference
with paragraph
> styles properties) while it is seldom used. Just my
gues )
>
> OK. Pls let me know what you think.
If we find a developer we will step deeper into the
specification. There
are some lacks of clarity e.g. what happens with objects.
>
> Thanks for your help,
> Cor
>
Thank you!
Andreas
------------------------------------------------------------
---------
To unsubscribe, e-mail: dev-unsubscribe specs.openoffice.org
For additional commands, e-mail: dev-help specs.openoffice.org
|