Hi Hanshini,
(probably my mails don't make it to the list directly as I'm writing from a different account)

I think the width of elements in the output is a general issue that most users are aware of. Having visual feedback in LyX would be a nice enhancement of course. Still, I would not create too many bug reports for feature requests and enhancements, unless it is clear that we can go ahead and implement them.

It's a matter of taste. IMHO it's a very good idea to keep in mind for your proposal. As for the bug tracker, I tend to use bug reports only for things that are real bugs (or features that seem so broken that it feels like one).

Hashini Senaratne wrote:
Hello Cyrille,


Cyrille Artho <c.artho <at> aist.go.jp> writes:

Hi Hanshini,
You actually identified another problem. The original proposal targets the
LyX user interface, where a table or formula may be too wide.

This is an issue with the resulting text (typeset by LaTeX). I think it is
possible in principle to parse the LaTeX log and map the result back to the
LyX source code; some form of visual feedback could provide the user
information on items that are too wide in the final output. I think this is
a worthy secondary goal for this project.


Thank you for your response.

I like to contribute it if I could. So if the mentors allow, I will keep
that in mind as a secondary goal and try to work on it if I get time.

Is this bug already reported as a ticket? If so, could you please show me
the ticket? If not, can I report it by myself or shall I ask to do so from
someone else?
I am really enthusiastic to contribute in developing a product like LyX
where wide range of the public can get the use of it as it is open source.

Thank you
Hashini Senaratne



--
Regards,
Cyrille Artho - http://artho.com/
Murder is always a mistake -- one should never do anything one cannot
talk about after dinner.
                -- Oscar Wilde, "The Picture of Dorian Gray"

Reply via email to