On 13/04/2016 08:46, Pedro Rosmaninho wrote:
> but if you held and released it only when it has a 1024 color
> palette it would have bigger impact because you would release something
> already much more polished and usable. The marketing team could then give
> more emphasis to that.
I realize I
I know this goes a bit against the philosophy usually followed by Libre
Office, but if you held and released it only when it has a 1024 color
palette it would have bigger impact because you would release something
already much more polished and usable. The marketing team could then give
more
On 11/04/2016 06:58, Heiko Tietze wrote:
> We run some of the previous studies localized. Even Chinese was
> included in one of the surveys. The problem is that not only waiting
> for the translation team heavily reduces the velocity but also the
> analysis of free text answers needs language
2016-04-10 15:51 GMT+02:00 toki :
> Is the only locale in the survey « EN »?
We run some of the previous studies localized. Even Chinese was
included in one of the surveys. The problem is that not only waiting
for the translation team heavily reduces the velocity but also
On 25/03/2016 08:12, Heiko Tietze wrote:
> My intention was to summarize in terms of use-cases. And the article should
> contain all high-level things. Not sure if it is exhaustive, but you should
> be
> able to get an idea yourself from the results.
Is the only locale in the survey « EN »?
Thanks a lot. The remark means that GDocs cannot handle captions for
floating figures like Wordpress.
2016-03-29 14:07 GMT+02:00 Mike Saunders :
> Hi Heiko,
>
> OK, I've gone through the document now and done a few small English
> cleanups. The only bit I
Hi Heiko,
OK, I've gone through the document now and done a few small English
cleanups. The only bit I didn't understand was this: "Remark: Goes to
figure caption of the legend"
Anyway, it's a fascinating read so when you make it live on the Design
blog I can generate some interest around
On Freitag, 25. März 2016 01:29:46 CET toki wrote:
> On 24/03/2016 09:29, Heiko Tietze wrote:
> >> Can you redo the charts in colour, rather than B
> > Sure. But why?
> Improve3s readability/ease of understanding.
> >And what color?
> Each one a different colour.
Too many colors are rather
On 24/03/2016 09:29, Heiko Tietze wrote:
>> Can you redo the charts in colour, rather than B
> Sure. But why?
Improve3s readability/ease of understanding.
>And what color?
Each one a different colour.
>> comprehensive, and more complete set of citations.
> I'm afraid of making the post
Hi Mike,
I suspect Google to always change my setting. Pretty sure that I enabled at
least commenting. Anyway, now it should be okay.
And I'm glad to have you onboard since the documentation part is mostly a
communication and marketing thing.
All the best,
Heiko
On Donnerstag, 24. März 2016
Hi Heiko,
On 23.03.2016 17:51, Heiko Tietze wrote:
As usual the English is a shame and needs proof-reading from natives.
Not a shame; the English is mostly great! But I'm a native speaker and
can do a few cleanups if you like -- just grant access to my Google
account (oka...@gmail.com) and
On Mittwoch, 23. März 2016 21:09:54 CET toki wrote:
> On 23/03/2016 16:51, Heiko Tietze wrote:
> > read critical to make sure that it's not too concise, not boring, and
> > that you can follow the argumentation.
>
> Can you redo the charts in colour, rather than B
Sure. But why? And what color?
On 23/03/16 14:09, toki wrote:
> Whist it was obvious to me that the house plan from 1991 was not
> originally created with LibO, I couldn't tell from either your
> report, or from reading the blog it came from, if the new house plan
> was created with LibO, or if the user thought that they should
On 23/03/2016 16:51, Heiko Tietze wrote:
> read critical to make sure that it's not too concise, not boring, and
> that you can follow the argumentation.
Can you redo the charts in colour, rather than B
> The result is a personal conclusion that should be verified.
I didn't read the individual
14 matches
Mail list logo