Re: [LyX GSoC/odt2lyx] Updated Tests-Report.lyx and completed documenting parseodt.py which is the main script for ODT to LyX conversion

[Prannoy Pilligundla]

ᐧ
On Wed, Aug 20, 2014 at 12:00 AM, Scott Kostyshak skost...@lyx.org wrote:


  The actual problem is because of the difference in ODT syntax that
 tex4ht uses and that the latest versions of Libre Office or Open Office
 uses. Suppose we just open the ODT generated by tex4ht, make a slight
 change and save it there are large number of differences in all the xml
 files before and after saving. So I guess it becomes difficult for us to
 take an example file in these kind of cases and compare them. And as our
 main aim was semanticity, even verifying semanticity becomes very difficult
 to verify keeping in mind all these constraints.


 Did you mean to email this to me and not the list? We try to keep things
 on the list as much as possible.


Oh Sorry, just realized that I just mailed you and not the list. I wanted
to reply to all but maybe I clicked on reply by mistake. Again, I am sorry,
will be careful from next time on.


 I think we're talking about different kinds of tests. The kind I have in
 mind are the following: suppose you make a change to the ODT export. How
 can you be sure that that change doesn't break anything? One way to address
 this is to have tests. You would not need to open Libre Office or in fact
 even have it installed. The tests would just check that nothing changed in
 the other exports (it would do this just like tex2lyx by comparing a saved
 exported file to the new exported file and checking that they're
 identical). Of course, it might be expected that the tests change. In this
 case, you would want to check the new exported files manually and then save
 the new files as the files to compare to. Does that make sense? It
 shouldn't take much time to implement (although I know that even a little
 time can be hard to find and prioritize). You just run ODT export on a .lyx
 file, say test1.lyx, then save that .odt, test1.save.odt. Then suppose you
 change ODT export. You would have a script that exports test1.lyx to
 test1.odt and then compare test1.odt to test1.save.odt to see if they are
 identical. If they are not identical, then manual inspection would be
 needed to see if the differences are legitimate. If they are, rename
 test1.odt to test1.save.odt (overwriting) and explain the changes in the
 commit message.

 Does that make sense?


Thanks, now I understood what you meant. Ya, I guess this should not take
much time to implement. I didn't do this sort of testing in LyX to ODT as I
was not touching any of tex4ht's post-processors. I was only configuring
some new styles and fixing issues with some old ones, so we can say all
were kind of independent changes which don't effect each other(provided
mk4ht doesn't raise any error while running). Whenever I write a wrong XML
syntax, the generated ODT doesn't have a content.xml at all, so I used this
as feedback manytimes. But recently, when I tried converting a real life
lyx doc, then the resultant ODT file turned out to be corrupt. I was not
able to find out why the file was corrupt and I am still wondering on how
to fix these kind of issues.

Re: [LyX GSoC/odt2lyx] Updated Tests-Report.lyx and completed documenting parseodt.py which is the main script for ODT to LyX conversion

[Prannoy Pilligundla]

ᐧ
On Wed, Aug 20, 2014 at 8:12 PM, stefano franchi stefano.fran...@gmail.com
wrote:

 Hi Prannoy,

 are you familiar with test-driven development [1]? This is what Scott is
 referring to (or almost).


Yes, I am aware of test-driven development. I had actually written some
tests for RoR previously.

The basic idea is to write the tests first and then code until your code
 passes the all the tests (even those you haven't touched in your last
 iterations).


Yes, I understand this part but I was saying is that since we are mainly
fixing issues in styling for just configuring new environments mostly one
part of the code doesn't interfere with other parts. But I guess I have
been thinking in the wrong direction and neglecting good coding practices.
I also agree with you and Scott, it would be good to have such a thing and
it would definitely give structure to our otherwise manual testing process

Re: [LyX GSoC/odt2lyx] Updated Tests-Report.lyx and completed documenting parseodt.py which is the main script for ODT to LyX conversion

[Prannoy Pilligundla]

ᐧ
On Wed, Aug 20, 2014 at 12:00 AM, Scott Kostyshak  wrote:
>
>
>>  The actual problem is because of the difference in ODT syntax that
>> tex4ht uses and that the latest versions of Libre Office or Open Office
>> uses. Suppose we just open the ODT generated by tex4ht, make a slight
>> change and save it there are large number of differences in all the xml
>> files before and after saving. So I guess it becomes difficult for us to
>> take an example file in these kind of cases and compare them. And as our
>> main aim was semanticity, even verifying semanticity becomes very difficult
>> to verify keeping in mind all these constraints.
>>
>
> Did you mean to email this to me and not the list? We try to keep things
> on the list as much as possible.
>

Oh Sorry, just realized that I just mailed you and not the list. I wanted
to reply to all but maybe I clicked on reply by mistake. Again, I am sorry,
will be careful from next time on.

>
> I think we're talking about different kinds of tests. The kind I have in
> mind are the following: suppose you make a change to the ODT export. How
> can you be sure that that change doesn't break anything? One way to address
> this is to have tests. You would not need to open Libre Office or in fact
> even have it installed. The tests would just check that nothing changed in
> the other exports (it would do this just like tex2lyx by comparing a saved
> exported file to the new exported file and checking that they're
> identical). Of course, it might be expected that the tests change. In this
> case, you would want to check the new exported files manually and then save
> the new files as the files to compare to. Does that make sense? It
> shouldn't take much time to implement (although I know that even a little
> time can be hard to find and prioritize). You just run ODT export on a .lyx
> file, say test1.lyx, then save that .odt, test1.save.odt. Then suppose you
> change ODT export. You would have a script that exports test1.lyx to
> test1.odt and then compare test1.odt to test1.save.odt to see if they are
> identical. If they are not identical, then manual inspection would be
> needed to see if the differences are legitimate. If they are, rename
> test1.odt to test1.save.odt (overwriting) and explain the changes in the
> commit message.
>
> Does that make sense?
>

Thanks, now I understood what you meant. Ya, I guess this should not take
much time to implement. I didn't do this sort of testing in LyX to ODT as I
was not touching any of tex4ht's post-processors. I was only configuring
some new styles and fixing issues with some old ones, so we can say all
were kind of independent changes which don't effect each other(provided
mk4ht doesn't raise any error while running). Whenever I write a wrong XML
syntax, the generated ODT doesn't have a content.xml at all, so I used this
as feedback manytimes. But recently, when I tried converting a real life
lyx doc, then the resultant ODT file turned out to be corrupt. I was not
able to find out why the file was corrupt and I am still wondering on how
to fix these kind of issues.

Re: [LyX GSoC/odt2lyx] Updated Tests-Report.lyx and completed documenting parseodt.py which is the main script for ODT to LyX conversion

[Prannoy Pilligundla]

ᐧ
On Wed, Aug 20, 2014 at 8:12 PM, stefano franchi 
wrote:
>
> Hi Prannoy,
>
> are you familiar with test-driven development [1]? This is what Scott is
> referring to (or almost).
>

Yes, I am aware of test-driven development. I had actually written some
tests for RoR previously.

The basic idea is to write the tests first and then code until your code
> passes the all the tests (even those you haven't touched in your last
> iterations).
>

Yes, I understand this part but I was saying is that since we are mainly
fixing issues in styling for just configuring new environments mostly one
part of the code doesn't interfere with other parts. But I guess I have
been thinking in the wrong direction and neglecting good coding practices.
I also agree with you and Scott, it would be good to have such a thing and
it would definitely give structure to our otherwise manual testing process

[GSoC 2014]Roundtrip Conversion from LyX to ODT

[Prannoy Pilligundla]

Hi Everyone,

My GSoC project has come to an end and I updated the wiki with all the
details of the project. You can view it here
http://wiki.lyx.org/GSoC/LyxToWordConversion

In the wiki, Progress Section states about all the issues that have been
fixed. I have also written a Future Work section which outlines all the
work that needs to done and the remaining issues that need to be fixed. In
the GSoC repo branch named prannoy is the one which is up to date. LyX to
ODT testing is can be done inside the tests directory and ODT to LyX
testing can be done inside the odt2lyx directory.

For integrating both the scripts(lyx2odt and odt2lyx), I edited
configure.py and created a new file format named ODT(Roundtrip) and added
an Export option to it. I also added Import ODT option and added these
scripts into the scripts directory. I was doing all this in main LyX repo I
had cloned. I can't push this directly to any of the GSoC repos I have been
working on as none of them have the source code of LyX. How do I go about
this?

Looking forward for your views and suggestions

Thanks and Regards
Prannoy Pilligundla

ᐧ

Re: [LyX GSoC/odt2lyx] Updated Tests-Report.lyx and completed documenting parseodt.py which is the main script for ODT to LyX conversion

[Prannoy Pilligundla]

ᐧ
On Mon, Aug 18, 2014 at 6:01 AM, Scott Kostyshak skost...@lyx.org wrote:

 Thanks for the explanation Prannoy! So if I understand correctly, the
 tests require manual inspection of the output .odt file, right?


Yes, we had to to inspect the output ODT file manually.


 Do you have plans to make automated tests? Is there a reason why we can't
 do the same as tex2lyx? And if so, would this require a lot of work?


I didn't concentrate on writing automatic tests as I thought it would take
up lot of time and I wanted to focus on the conversion part at this stage
as we are just at the beginning. Actually I know that tests are automated
in tex2lyx but I am not aware of what happens there exactly.


 Additionally, is there any automatic way (command-line option) to check
 that a .odt file is valid (e.g. that if I open it in libre office it will
 not say there is a syntax error or a corrupted file)? I'd be interested in
 your thoughts.


I went through help manual of OO, I don't think there is a direct option
available

[GSoC 2014]Roundtrip Conversion from LyX to ODT

[Prannoy Pilligundla]

Hi Everyone,

My GSoC project has come to an end and I updated the wiki with all the
details of the project. You can view it here
http://wiki.lyx.org/GSoC/LyxToWordConversion

In the wiki, Progress Section states about all the issues that have been
fixed. I have also written a Future Work section which outlines all the
work that needs to done and the remaining issues that need to be fixed. In
the GSoC repo branch named prannoy is the one which is up to date. LyX to
ODT testing is can be done inside the tests directory and ODT to LyX
testing can be done inside the odt2lyx directory.

For integrating both the scripts(lyx2odt and odt2lyx), I edited
configure.py and created a new file format named ODT(Roundtrip) and added
an Export option to it. I also added Import ODT option and added these
scripts into the scripts directory. I was doing all this in main LyX repo I
had cloned. I can't push this directly to any of the GSoC repos I have been
working on as none of them have the source code of LyX. How do I go about
this?

Looking forward for your views and suggestions

Thanks and Regards
Prannoy Pilligundla

ᐧ

Re: [LyX GSoC/odt2lyx] Updated Tests-Report.lyx and completed documenting parseodt.py which is the main script for ODT to LyX conversion

[Prannoy Pilligundla]

ᐧ
On Mon, Aug 18, 2014 at 6:01 AM, Scott Kostyshak  wrote:

> Thanks for the explanation Prannoy! So if I understand correctly, the
> tests require manual inspection of the output .odt file, right?
>

Yes, we had to to inspect the output ODT file manually.


> Do you have plans to make automated tests? Is there a reason why we can't
> do the same as tex2lyx? And if so, would this require a lot of work?
>

I didn't concentrate on writing automatic tests as I thought it would take
up lot of time and I wanted to focus on the conversion part at this stage
as we are just at the beginning. Actually I know that tests are automated
in tex2lyx but I am not aware of what happens there exactly.


> Additionally, is there any automatic way (command-line option) to check
> that a .odt file is valid (e.g. that if I open it in libre office it will
> not say there is a syntax error or a corrupted file)? I'd be interested in
> your thoughts.
>

I went through help manual of OO, I don't think there is a direct option
available

Re: [LyX GSoC/odt2lyx] Updated Tests-Report.lyx and completed documenting parseodt.py which is the main script for ODT to LyX conversion

[Prannoy Pilligundla]

Hi Scott,

On Fri, Aug 15, 2014 at 2:49 AM, Scott Kostyshak skost...@lyx.org wrote:
ᐧ


 Hi Prannoy, I'm interested in your LyX to ODT tests. Do you have it
 documented how to run the tests? I have not even attempted to run the
 tests myself, so perhaps it is easy. Are the tests integrated into the
 Ctests for CMake and the automake test target for autotools? Are the
 tests similar to tex2lyx tests were the conversion is performed and
 the result is compared to a saved file to see if they are identical?


Tests I performed here are very much different from what happens in
tex2lyx. In this case Stefano had created many test files in LyX spanning
all the Environments, Math, Figures etc etc. So I wrote a shell script
which converts LyX to LaTeX first and then runs mk4ht on the generated tex
file. Then I manually see the generated ODT file to see the issues. This
way I fixed issues with every test file. You can see the latest results in
the branch tex4htTesting. All the tests have been run inside the tests
directory. The shell script is named convert.sh, so for converting a lyx
file named First-Test.lyx I need to run ./convert.sh First-Test.lyx and
the output ODT file can be seen in the same directory. While adding the
Export option inside LyX I ported this convert.sh to a python scripts and
put it inside scripts directory.

Thanks and Regards
Prannoy

Re: [LyX GSoC/odt2lyx] Updated Tests-Report.lyx and completed documenting parseodt.py which is the main script for ODT to LyX conversion

[Prannoy Pilligundla]

Hi Scott,

On Fri, Aug 15, 2014 at 2:49 AM, Scott Kostyshak  wrote:
ᐧ

>
> Hi Prannoy, I'm interested in your LyX to ODT tests. Do you have it
> documented how to run the tests? I have not even attempted to run the
> tests myself, so perhaps it is easy. Are the tests integrated into the
> Ctests for CMake and the automake test target for autotools? Are the
> tests similar to tex2lyx tests were the conversion is performed and
> the result is compared to a saved file to see if they are identical?
>

Tests I performed here are very much different from what happens in
tex2lyx. In this case Stefano had created many test files in LyX spanning
all the Environments, Math, Figures etc etc. So I wrote a shell script
which converts LyX to LaTeX first and then runs mk4ht on the generated tex
file. Then I manually see the generated ODT file to see the issues. This
way I fixed issues with every test file. You can see the latest results in
the branch tex4htTesting. All the tests have been run inside the tests
directory. The shell script is named convert.sh, so for converting a lyx
file named "First-Test.lyx" I need to run "./convert.sh First-Test.lyx" and
the output ODT file can be seen in the same directory. While adding the
Export option inside LyX I ported this convert.sh to a python scripts and
put it inside scripts directory.

Thanks and Regards
Prannoy

[GSoC 2014]ODT--LyX Conversion

[Prannoy Pilligundla]

Hi Everyone,

I am almost done with LyX to ODT part of my project and I started work on
the roundtrip i.e ODT to LyX part of the project. For LyX to ODT I
converted LyX to LaTeX first and then used tex4ht for converting LaTeX to
ODT. In case of math I am also storing the latex expression as it as in the
ODT file(using annotation property) as meta data.

Now for getting back to LyX from ODT I am thinking of writing a python
script which does this conversion. As of now I am planning to use the xml
parsers expat library https://docs.python.org/2/library/pyexpat.html.I
also had a look at lyx2lyx scripts. I tried using Writer2LaTeX but it
doesn't suit our purpose of getting back the same LyX file. I am not very
clear on how to go ahead from this juncture. For example I am not clear on
how I will get information about all the packages used from the ODT file. I
feel I am not aware of many issues which need to be taken care of during
this conversion process. It would be great to hear your comments and
suggestions on how to go ahead

Thanks and Regards
Prannoy Pilligundla

Re: [GSoC 2014]ODT--LyX Conversion

[Prannoy Pilligundla]

Hi Liviu,

On Thu, Jul 3, 2014 at 8:40 PM, Liviu Andronic landronim...@gmail.com
wrote:

 How can we test the feature, and where is the repo located? Also, are
 there some test documents available?


I am attaching the tests report, please have a look. I am using the LyX
GSoC repo. Everything is up to date on the branch tex4htTesting. There are
many test documents which can be seen in the tests folder inside the repo.


Tests-report.pdf
Description: Adobe PDF document

Re: [GSoC 2014]ODT--LyX Conversion

[Prannoy Pilligundla]

Hi Eberhard,

On Thu, Jul 3, 2014 at 9:34 PM, Dr Eberhard Lisse nos...@lisse.na wrote:

 Prannoy,

 what's wrong with the LaTeX Export from ODT?


I used Writer2LaTeX for doing this. Many things are interpreted wrong for
example math which was originally inline is now put into equation
environment. Align and Eqnarray which were used in the initial file don't
come back exactly as it is. Some sections are recognized as subsections and
so on. There are actually many issues like these

[GSoC 2014]ODT-->LyX Conversion

[Prannoy Pilligundla]

Hi Everyone,

I am almost done with LyX to ODT part of my project and I started work on
the roundtrip i.e ODT to LyX part of the project. For LyX to ODT I
converted LyX to LaTeX first and then used tex4ht for converting LaTeX to
ODT. In case of math I am also storing the latex expression as it as in the
ODT file(using annotation property) as meta data.

Now for getting back to LyX from ODT I am thinking of writing a python
script which does this conversion. As of now I am planning to use the xml
parsers expat library <https://docs.python.org/2/library/pyexpat.html>.I
also had a look at lyx2lyx scripts. I tried using Writer2LaTeX but it
doesn't suit our purpose of getting back the same LyX file. I am not very
clear on how to go ahead from this juncture. For example I am not clear on
how I will get information about all the packages used from the ODT file. I
feel I am not aware of many issues which need to be taken care of during
this conversion process. It would be great to hear your comments and
suggestions on how to go ahead

Thanks and Regards
Prannoy Pilligundla

Re: [GSoC 2014]ODT-->LyX Conversion

[Prannoy Pilligundla]

Hi Liviu,

On Thu, Jul 3, 2014 at 8:40 PM, Liviu Andronic 
wrote:

> How can we test the feature, and where is the repo located? Also, are
> there some test documents available?
>

I am attaching the tests report, please have a look. I am using the LyX
GSoC repo. Everything is up to date on the branch tex4htTesting. There are
many test documents which can be seen in the tests folder inside the repo.


Tests-report.pdf
Description: Adobe PDF document

Re: [GSoC 2014]ODT-->LyX Conversion

[Prannoy Pilligundla]

Hi Eberhard,

On Thu, Jul 3, 2014 at 9:34 PM, Dr Eberhard Lisse  wrote:

> Prannoy,
>
> what's wrong with the LaTeX Export from ODT?
>

I used Writer2LaTeX for doing this. Many things are interpreted wrong for
example math which was originally inline is now put into equation
environment. Align and Eqnarray which were used in the initial file don't
come back exactly as it is. Some sections are recognized as subsections and
so on. There are actually many issues like these

[GSoC 2014] Introduction

[Prannoy Pilligundla]

Hi Everyone,

I am Prannoy Pilligundla, a second year undergrad from India. I will be
working on Roundtrip Conversion from Lyx to ODT throughout the Summer as a
part of Google Summer of Code 2014. First of all I want to thank the
community for keeping faith in my abilities and selecting my proposal, I
will definitely put in my best efforts to complete this project. Also
Congratulations to the Co-GSoCer Sushant Raikar, all the best to you too.

I have already started work and currently my focus is to get accustomed to
TeX4ht. To start with I am fixing issues with some styles one by one. My
mid-term milestone
is to have Lyx to ODT conversion working for the decided feature set. After
tuning the export to ODT as per the requirements next thing to do would be
to replace the last step of TeX4ht with a Lua module in LuaTeX  which
relies on the same *.4ht files. In the last step TeX4ht processes the DVI
file which has special instructions to complete the conversion. A package
needs to be written in Lua which has full access to the nodes created by
LuaTeX and loads tex4ht.sty to have access to the *.4ht files. This needs
to be done because TeX4ht doesn’t support fonts without a tfm table,which
means that opentype and truetype fonts used by fontspec cannot be used.
After completing this part I will work on prototyping the reverse
conversion.

This is the brief overview of my project and I will definitely seek your
help,advice and suggestions for all the difficulties that arise on the
course of completing this project.

Looking forward for an exciting Summer!!

Thanks and Regards
Prannoy Pilligundla
ᐧ

Re: [GSoC 2014] Introduction

[Prannoy Pilligundla]

Hi Everyone.

I updated the wiki for this Project and from now on I will constantly
record my progress there. Here is the link
http://wiki.lyx.org/GSoC/LyxToWordConversion

Thanks and Regards
Prannoy Pilligundla
ᐧ


On Mon, Apr 28, 2014 at 2:03 PM, Prannoy Pilligundla prannoy.b...@gmail.com
 wrote:

 Hi Everyone,

 I am Prannoy Pilligundla, a second year undergrad from India. I will be
 working on Roundtrip Conversion from Lyx to ODT throughout the Summer as a
 part of Google Summer of Code 2014. First of all I want to thank the
 community for keeping faith in my abilities and selecting my proposal, I
 will definitely put in my best efforts to complete this project. Also
 Congratulations to the Co-GSoCer Sushant Raikar, all the best to you too.

 I have already started work and currently my focus is to get accustomed to
 TeX4ht. To start with I am fixing issues with some styles one by one. My
 mid-term milestone
 is to have Lyx to ODT conversion working for the decided feature set. After
 tuning the export to ODT as per the requirements next thing to do would be
 to replace the last step of TeX4ht with a Lua module in LuaTeX  which
 relies on the same *.4ht files. In the last step TeX4ht processes the DVI
 file which has special instructions to complete the conversion. A package
 needs to be written in Lua which has full access to the nodes created by
 LuaTeX and loads tex4ht.sty to have access to the *.4ht files. This needs
 to be done because TeX4ht doesn’t support fonts without a tfm table,which
 means that opentype and truetype fonts used by fontspec cannot be used.
 After completing this part I will work on prototyping the reverse
 conversion.

 This is the brief overview of my project and I will definitely seek your
 help,advice and suggestions for all the difficulties that arise on the
 course of completing this project.

 Looking forward for an exciting Summer!!

 Thanks and Regards
 Prannoy Pilligundla
 ᐧ

[GSoC 2014] Introduction

[Prannoy Pilligundla]

Hi Everyone,

I am Prannoy Pilligundla, a second year undergrad from India. I will be
working on Roundtrip Conversion from Lyx to ODT throughout the Summer as a
part of Google Summer of Code 2014. First of all I want to thank the
community for keeping faith in my abilities and selecting my proposal, I
will definitely put in my best efforts to complete this project. Also
Congratulations to the Co-GSoCer Sushant Raikar, all the best to you too.

I have already started work and currently my focus is to get accustomed to
TeX4ht. To start with I am fixing issues with some styles one by one. My
mid-term milestone
is to have Lyx to ODT conversion working for the decided feature set. After
tuning the export to ODT as per the requirements next thing to do would be
to replace the last step of TeX4ht with a Lua module in LuaTeX  which
relies on the same *.4ht files. In the last step TeX4ht processes the DVI
file which has special instructions to complete the conversion. A package
needs to be written in Lua which has full access to the nodes created by
LuaTeX and loads tex4ht.sty to have access to the *.4ht files. This needs
to be done because TeX4ht doesn’t support fonts without a tfm table,which
means that opentype and truetype fonts used by fontspec cannot be used.
After completing this part I will work on prototyping the reverse
conversion.

This is the brief overview of my project and I will definitely seek your
help,advice and suggestions for all the difficulties that arise on the
course of completing this project.

Looking forward for an exciting Summer!!

Thanks and Regards
Prannoy Pilligundla
ᐧ

Re: [GSoC 2014] Introduction

[Prannoy Pilligundla]

Hi Everyone.

I updated the wiki for this Project and from now on I will constantly
record my progress there. Here is the link
http://wiki.lyx.org/GSoC/LyxToWordConversion

Thanks and Regards
Prannoy Pilligundla
ᐧ


On Mon, Apr 28, 2014 at 2:03 PM, Prannoy Pilligundla <prannoy.b...@gmail.com
> wrote:

> Hi Everyone,
>
> I am Prannoy Pilligundla, a second year undergrad from India. I will be
> working on Roundtrip Conversion from Lyx to ODT throughout the Summer as a
> part of Google Summer of Code 2014. First of all I want to thank the
> community for keeping faith in my abilities and selecting my proposal, I
> will definitely put in my best efforts to complete this project. Also
> Congratulations to the Co-GSoCer Sushant Raikar, all the best to you too.
>
> I have already started work and currently my focus is to get accustomed to
> TeX4ht. To start with I am fixing issues with some styles one by one. My
> mid-term milestone
> is to have Lyx to ODT conversion working for the decided feature set. After
> tuning the export to ODT as per the requirements next thing to do would be
> to replace the last step of TeX4ht with a Lua module in LuaTeX  which
> relies on the same *.4ht files. In the last step TeX4ht processes the DVI
> file which has special instructions to complete the conversion. A package
> needs to be written in Lua which has full access to the nodes created by
> LuaTeX and loads tex4ht.sty to have access to the *.4ht files. This needs
> to be done because TeX4ht doesn’t support fonts without a tfm table,which
> means that opentype and truetype fonts used by fontspec cannot be used.
> After completing this part I will work on prototyping the reverse
> conversion.
>
> This is the brief overview of my project and I will definitely seek your
> help,advice and suggestions for all the difficulties that arise on the
> course of completing this project.
>
> Looking forward for an exciting Summer!!
>
> Thanks and Regards
> Prannoy Pilligundla
> ᐧ
>

Re: Non Uniform behavior with command line export

[Prannoy Pilligundla]

ᐧ

On Fri, Apr 18, 2014 at 4:15 AM, Pavel Sanda sa...@lyx.org wrote:

 Prannoy Pilligundla wrote:
  I feel we need to either modify the man page according to the present
  behavior or make a change in the script to have a uniform behavior.

 Can you create the patch for the man page?


I made the required change. I am attaching the patch to this mail.

Thanks and Regards
Prannoy Pilligundla
From ab48a76a0bc1d53b7e92ba59a0e0dee0f18bb7a1 Mon Sep 17 00:00:00 2001
From: Prannoy Pilligundla prannoyp.1...@gmail.com
Date: Fri, 18 Apr 2014 08:45:03 +0530
Subject: [PATCH] Minor correction in Man page

---
 lyx.1in |2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/lyx.1in b/lyx.1in
index 8c07f5a..8f81660 100644
--- a/lyx.1in
+++ b/lyx.1in
@@ -67,7 +67,7 @@ Use \fBlyx@version_suffix@ \-dbg\fR to see the list of available debug feature
 where command is a lyx command.
 .TP
 \fB \-e [\-\-export]\fP \fIfmt
-where fmt is the export format of choice (latex, pdflatex, lualatex, xelatex, xhtml, text, lyx, ps, pdf, ...).
+where fmt is the export format of choice (latex, pdflatex, luatex, xetex, xhtml, text, lyx, ps, pdf, ...).
 Note that the order of \-e and \-x switches matters.
 .TP
 \fB \-E [\-\-export\-to]\fP \fIfmt \fIfilename
-- 
1.7.10.4

Re: Non Uniform behavior with command line export

[Prannoy Pilligundla]

ᐧ

On Fri, Apr 18, 2014 at 4:15 AM, Pavel Sanda <sa...@lyx.org> wrote:

> Prannoy Pilligundla wrote:
> > I feel we need to either modify the man page according to the present
> > behavior or make a change in the script to have a uniform behavior.
>
> Can you create the patch for the man page?
>

I made the required change. I am attaching the patch to this mail.

Thanks and Regards
Prannoy Pilligundla
From ab48a76a0bc1d53b7e92ba59a0e0dee0f18bb7a1 Mon Sep 17 00:00:00 2001
From: Prannoy Pilligundla <prannoyp.1...@gmail.com>
Date: Fri, 18 Apr 2014 08:45:03 +0530
Subject: [PATCH] Minor correction in Man page

---
 lyx.1in |2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/lyx.1in b/lyx.1in
index 8c07f5a..8f81660 100644
--- a/lyx.1in
+++ b/lyx.1in
@@ -67,7 +67,7 @@ Use "\fBlyx@version_suffix@ \-dbg\fR" to see the list of available debug feature
 where command is a lyx command.
 .TP
 \fB \-e [\-\-export]\fP \fIfmt
-where fmt is the export format of choice (latex, pdflatex, lualatex, xelatex, xhtml, text, lyx, ps, pdf, ...).
+where fmt is the export format of choice (latex, pdflatex, luatex, xetex, xhtml, text, lyx, ps, pdf, ...).
 Note that the order of \-e and \-x switches matters.
 .TP
 \fB \-E [\-\-export\-to]\fP \fIfmt \fIfilename
-- 
1.7.10.4

Non Uniform behavior with command line export

[Prannoy Pilligundla]

Hi Everyone,

I was trying to convert some LyX files via command line and came across a
non uniform behavior

In the lyx man page,this is the text under options part

-e [--export] fmt
 where fmt is the export format of choice (latex, pdflatex,
luala‐
 tex, xelatex, xhtml, text, lyx, ps, pdf,  ...).   Note  that
 the
 order of -e and -x switches matters.

xelatex and lualtex are stated here but lyx -e xelatex foo.lyx  and lyx -e
lualatex foo.lyx don't work but instead lyx -e xetex foo.lyx and lyx -e
luatex foo.lyx are the ones which work.

But in case of pdflatex lyx -e pdflatex foo.lyx works but lyx -e pdftex
foo.lyx doesn't.

I feel we need to either modify the man page according to the present
behavior or make a change in the script to have a uniform behavior.

Thanks and Regards
Prannoy
ᐧ

Non Uniform behavior with command line export

[Prannoy Pilligundla]

Hi Everyone,

I was trying to convert some LyX files via command line and came across a
non uniform behavior

In the lyx man page,this is the text under options part

-e [--export] fmt
 where fmt is the export format of choice (latex, pdflatex,
luala‐
 tex, xelatex, xhtml, text, lyx, ps, pdf,  ...).   Note  that
 the
 order of -e and -x switches matters.

xelatex and lualtex are stated here but lyx -e xelatex foo.lyx  and lyx -e
lualatex foo.lyx don't work but instead lyx -e xetex foo.lyx and lyx -e
luatex foo.lyx are the ones which work.

But in case of pdflatex lyx -e pdflatex foo.lyx works but lyx -e pdftex
foo.lyx doesn't.

I feel we need to either modify the man page according to the present
behavior or make a change in the script to have a uniform behavior.

Thanks and Regards
Prannoy
ᐧ

[GSoC 2014][Proposal]Roundtrip Conversion between Lyx and ODT

[Prannoy Pilligundla]

Hi Everyone,

I am done with the initial draft of my Proposal. Please have a look and
suggest changes. Here is the
linkhttps://docs.google.com/document/d/1vyTqXajpYroyU7kVjamRK4BPtuhfPh1rGpElrL9vyug/edit?usp=sharing

Thanks and Regards
Prannoy Pilligundla
ᐧ

[GSoC 2014][Proposal]Roundtrip Conversion between Lyx and ODT

[Prannoy Pilligundla]

Hi Everyone,

I am done with the initial draft of my Proposal. Please have a look and
suggest changes. Here is the
link<https://docs.google.com/document/d/1vyTqXajpYroyU7kVjamRK4BPtuhfPh1rGpElrL9vyug/edit?usp=sharing>

Thanks and Regards
Prannoy Pilligundla
ᐧ

Re: About Source code download

[Prannoy Pilligundla]

Hi Kamal,

Can you please elaborate more on what kind of problem you are facing?

If you have git installed then you can run git clone git://git.lyx.org/lyx
from within the directory where you initially wanted your download to be.

Thanks and Regards
Prannoy Pilligundla
ᐧ


On Sat, Mar 15, 2014 at 4:24 PM, Kamal Garg kmlgrg2...@gmail.com wrote:

  sir, i am not able to download the source code from the provided link on
 the lyx site.can you provide me a download link for source code.

Re: About Source code download

[Prannoy Pilligundla]

On Sat, Mar 15, 2014 at 5:34 PM, Kamal Garg kmlgrg2...@gmail.com wrote:

 Sir,i am using ubuntu 13.04 in the terminal when i run this command:git
 clone git://git.lyx.org/lyx
 Give me this error
 Cloning into 'lyx'...
 fatal: unable to connect to git.lyx.org:
 git.lyx.org: System error


I am not sure why you are facing this error but i feel this is because of
some firewall issues



 Sir,when i run this command:git clone http://git.lyx.org/lyx
 then give me this error:fatal:
 http://git.lyx.org/lyx/info/refs?service=git-upload-pack not found: did
 you run git update-server-info on the server?

 Can you tell me that what is reason behind this error?


 Try using https instead of http. There are high chances that you may still
get an error.If you face an error,you may most probably face an
gnutls_handshake() failed error. Then go to this
linkhttp://askubuntu.com/questions/186847/error-gnutls-handshake-falied
and
follow these instructions. You may need to rebuild git core which is
modified to use openssl instead of gnutls by following the instructions
given there.
After fixing this issue run git config --global url. https://; ,insteadOf
git:// so that you will never face this problem again.

Hope that helped. I am not very good at git and these were the issues i
could think of.Someone else in the community might be able to help you
better.
ᐧ


On Sat, Mar 15, 2014 at 5:34 PM, Kamal Garg kmlgrg2...@gmail.com wrote:

 Sir,i am using ubuntu 13.04 in the terminal when i run this command:git
 clone git://git.lyx.org/lyx
 Give me this error
 Cloning into 'lyx'...
 fatal: unable to connect to git.lyx.org:
 git.lyx.org: System error

 Sir,when i run this command:git clone http://git.lyx.org/lyx
 then give me this error:fatal:
 http://git.lyx.org/lyx/info/refs?service=git-upload-pack not found: did
 you run git update-server-info on the server?

 Can you tell me that what is reason behind this error?



 On Sat, Mar 15, 2014 at 4:54 PM, Prannoy Pilligundla 
 prannoy.b...@gmail.com wrote:

 Hi Kamal,

 Can you please elaborate more on what kind of problem you are facing?

 If you have git installed then you can run git clone git://
 git.lyx.org/lyx from within the directory where you initially wanted
 your download to be.

 Thanks and Regards
 Prannoy Pilligundla
 ᐧ


 On Sat, Mar 15, 2014 at 4:24 PM, Kamal Garg kmlgrg2...@gmail.com wrote:

  sir, i am not able to download the source code from the provided link
 on the lyx site.can you provide me a download link for source code.

Re: About Source code download

[Prannoy Pilligundla]

Hi Kamal,

Can you please elaborate more on what kind of problem you are facing?

If you have git installed then you can run "git clone git://git.lyx.org/lyx"
from within the directory where you initially wanted your download to be.

Thanks and Regards
Prannoy Pilligundla
ᐧ


On Sat, Mar 15, 2014 at 4:24 PM, Kamal Garg <kmlgrg2...@gmail.com> wrote:

>  sir, i am not able to download the source code from the provided link on
> the lyx site.can you provide me a download link for source code.
>

Re: About Source code download

[Prannoy Pilligundla]

On Sat, Mar 15, 2014 at 5:34 PM, Kamal Garg <kmlgrg2...@gmail.com> wrote:

> Sir,i am using ubuntu 13.04 in the terminal when i run this command:git
> clone git://git.lyx.org/lyx
> Give me this error
> Cloning into 'lyx'...
> fatal: unable to connect to git.lyx.org:
> git.lyx.org: System error
>

I am not sure why you are facing this error but i feel this is because of
some firewall issues


>
> Sir,when i run this command:git clone http://git.lyx.org/lyx
> then give me this error:fatal:
> http://git.lyx.org/lyx/info/refs?service=git-upload-pack not found: did
> you run git update-server-info on the server?
>
> Can you tell me that what is reason behind this error?
>

 Try using https instead of http. There are high chances that you may still
get an error.If you face an error,you may most probably face an
"gnutls_handshake() failed" error. Then go to this
link<http://askubuntu.com/questions/186847/error-gnutls-handshake-falied>
and
follow these instructions. You may need to rebuild git core which is
modified to use openssl instead of gnutls by following the instructions
given there.
After fixing this issue run "git config --global url. "https://; ,insteadOf
git://" so that you will never face this problem again.

Hope that helped. I am not very good at git and these were the issues i
could think of.Someone else in the community might be able to help you
better.
ᐧ


On Sat, Mar 15, 2014 at 5:34 PM, Kamal Garg <kmlgrg2...@gmail.com> wrote:

> Sir,i am using ubuntu 13.04 in the terminal when i run this command:git
> clone git://git.lyx.org/lyx
> Give me this error
> Cloning into 'lyx'...
> fatal: unable to connect to git.lyx.org:
> git.lyx.org: System error
>
> Sir,when i run this command:git clone http://git.lyx.org/lyx
> then give me this error:fatal:
> http://git.lyx.org/lyx/info/refs?service=git-upload-pack not found: did
> you run git update-server-info on the server?
>
> Can you tell me that what is reason behind this error?
>
>
>
> On Sat, Mar 15, 2014 at 4:54 PM, Prannoy Pilligundla <
> prannoy.b...@gmail.com> wrote:
>
>> Hi Kamal,
>>
>> Can you please elaborate more on what kind of problem you are facing?
>>
>> If you have git installed then you can run "git clone git://
>> git.lyx.org/lyx" from within the directory where you initially wanted
>> your download to be.
>>
>> Thanks and Regards
>> Prannoy Pilligundla
>> ᐧ
>>
>>
>> On Sat, Mar 15, 2014 at 4:24 PM, Kamal Garg <kmlgrg2...@gmail.com> wrote:
>>
>>>  sir, i am not able to download the source code from the provided link
>>> on the lyx site.can you provide me a download link for source code.
>>>
>>
>>
>

Re: problem building lyx

[Prannoy Pilligundla]

Hi Chirag,


ᐧ
On Tue, Mar 4, 2014 at 1:50 PM, Chirag Chauhan chirag.hol...@gmail.comwrote:

 1.made some changes to the GuiPrefs.cpp file
 2.make
 3.run

 what am i doing wrong ?


Are you running Lyx from the src folder or are you opening the already
installed one?For the changes to reflect in the installed version i guess
you need to run make install also.If you still are not able to see the
changes,I think you should have a look at the changes you made in the
GuiPrefs.cpp file.

Thanks and Regards
Prannoy Pilligundla

Re: problem building lyx

[Prannoy Pilligundla]

Hi Chirag,


ᐧ
On Tue, Mar 4, 2014 at 1:50 PM, Chirag Chauhan <chirag.hol...@gmail.com>wrote:

> 1.made some changes to the GuiPrefs.cpp file
> 2.make
> 3.run
>
> what am i doing wrong ?
>

Are you running Lyx from the src folder or are you opening the already
installed one?For the changes to reflect in the installed version i guess
you need to run "make install" also.If you still are not able to see the
changes,I think you should have a look at the changes you made in the
GuiPrefs.cpp file.

Thanks and Regards
Prannoy Pilligundla

Re: LyX--word -- Latex to XML

[Prannoy Pilligundla]

http://jblevins.org/log/xml-tools

This is an other link where the author has written about his experiences
with various Latex to XML converters
ᐧ


On Sun, Mar 2, 2014 at 11:35 AM, Prannoy Pilligundla prannoy.b...@gmail.com
 wrote:

 I found an other software which does the same thing
 http://www-sop.inria.fr/marelle/tralics/
 ᐧ


 On Sat, Mar 1, 2014 at 8:33 PM, stefano franchi stefano.fran...@gmail.com
  wrote:

 I just discovered the LaTeXtoXML  project:

 http://dlmf.nist.gov/LaTeXML/

 which is actively developed and may actually come very close to what
 we are aiming at. It is a perl-based attempt to recreate a subset of
 TeX with XML output. It is very math-oriented and, from a first look,
 not so bibliorgaphy oriented (although it does parse bibtex).

 did anyone know of it? I am going to try it on our test document and
 will report back on its current performance.
 In the meanwhile, if you have any reactions to such an approach, do
 not hesitate to share them.


 Stefano

 --
 __
 Stefano Franchi
 Associate Research Professor
 Department of Hispanic Studies Ph:   +1 (979) 845-2125
 Texas AM University  Fax:  +1 (979) 845-6421
 College Station, Texas, USA

 stef...@tamu.edu
 http://stefano.cleinias.org

Re: LyX<-->word --> Latex to XML

[Prannoy Pilligundla]

http://jblevins.org/log/xml-tools

This is an other link where the author has written about his experiences
with various Latex to XML converters
ᐧ


On Sun, Mar 2, 2014 at 11:35 AM, Prannoy Pilligundla <prannoy.b...@gmail.com
> wrote:

> I found an other software which does the same thing
> http://www-sop.inria.fr/marelle/tralics/
> ᐧ
>
>
> On Sat, Mar 1, 2014 at 8:33 PM, stefano franchi <stefano.fran...@gmail.com
> > wrote:
>
>> I just discovered the LaTeXtoXML  project:
>>
>> http://dlmf.nist.gov/LaTeXML/
>>
>> which is actively developed and may actually come very close to what
>> we are aiming at. It is a perl-based attempt to recreate a subset of
>> TeX with XML output. It is very math-oriented and, from a first look,
>> not so bibliorgaphy oriented (although it does parse bibtex).
>>
>> did anyone know of it? I am going to try it on our test document and
>> will report back on its current performance.
>> In the meanwhile, if you have any reactions to such an approach, do
>> not hesitate to share them.
>>
>>
>> Stefano
>>
>> --
>> __
>> Stefano Franchi
>> Associate Research Professor
>> Department of Hispanic Studies Ph:   +1 (979) 845-2125
>> Texas A University  Fax:  +1 (979) 845-6421
>> College Station, Texas, USA
>>
>> stef...@tamu.edu
>> http://stefano.cleinias.org
>>
>
>

Re: GSoC Student Application

[Prannoy Pilligundla]

ᐧ
Hi Jicksy

On Sat, Mar 1, 2014 at 6:02 PM, Jicksy John jicksy.j...@gmail.com wrote:

  git clone git://git.lyx.org/lyx

 If I do this clone',I would still be able to edit the code right? While
 fixing bugs. Just wanted to make sure that.


Ya you can. git clone just copies the online repo into your comp

Thanks and Regards
Prannoy Pilligundla

Re: LyX--word -- Latex to XML

[Prannoy Pilligundla]

I found an other software which does the same thing
http://www-sop.inria.fr/marelle/tralics/
ᐧ


On Sat, Mar 1, 2014 at 8:33 PM, stefano franchi
stefano.fran...@gmail.comwrote:

 I just discovered the LaTeXtoXML  project:

 http://dlmf.nist.gov/LaTeXML/

 which is actively developed and may actually come very close to what
 we are aiming at. It is a perl-based attempt to recreate a subset of
 TeX with XML output. It is very math-oriented and, from a first look,
 not so bibliorgaphy oriented (although it does parse bibtex).

 did anyone know of it? I am going to try it on our test document and
 will report back on its current performance.
 In the meanwhile, if you have any reactions to such an approach, do
 not hesitate to share them.


 Stefano

 --
 __
 Stefano Franchi
 Associate Research Professor
 Department of Hispanic Studies Ph:   +1 (979) 845-2125
 Texas AM University  Fax:  +1 (979) 845-6421
 College Station, Texas, USA

 stef...@tamu.edu
 http://stefano.cleinias.org

Re: GSoC Student Application

[Prannoy Pilligundla]

ᐧ
Hi Jicksy

On Sat, Mar 1, 2014 at 6:02 PM, Jicksy John <jicksy.j...@gmail.com> wrote:

>  git clone git://git.lyx.org/lyx
>
> If I do this clone',I would still be able to edit the code right? While
> fixing bugs. Just wanted to make sure that.
>

Ya you can. "git clone" just copies the online repo into your comp

Thanks and Regards
Prannoy Pilligundla

Re: LyX<-->word --> Latex to XML

[Prannoy Pilligundla]

I found an other software which does the same thing
http://www-sop.inria.fr/marelle/tralics/
ᐧ


On Sat, Mar 1, 2014 at 8:33 PM, stefano franchi
wrote:

> I just discovered the LaTeXtoXML  project:
>
> http://dlmf.nist.gov/LaTeXML/
>
> which is actively developed and may actually come very close to what
> we are aiming at. It is a perl-based attempt to recreate a subset of
> TeX with XML output. It is very math-oriented and, from a first look,
> not so bibliorgaphy oriented (although it does parse bibtex).
>
> did anyone know of it? I am going to try it on our test document and
> will report back on its current performance.
> In the meanwhile, if you have any reactions to such an approach, do
> not hesitate to share them.
>
>
> Stefano
>
> --
> __
> Stefano Franchi
> Associate Research Professor
> Department of Hispanic Studies Ph:   +1 (979) 845-2125
> Texas A University  Fax:  +1 (979) 845-6421
> College Station, Texas, USA
>
> stef...@tamu.edu
> http://stefano.cleinias.org
>

Re: [GSoC 2014]Interested in Round trip conversion between LyX and .docx formats

[Prannoy Pilligundla]

I have been following the discussion going on in this thread and have been
exploring Lyx at the same time.I understood how to integrate python scripts
into the editor and all but i have a some queries regarding the round trip
conversion

Since we have something like eLyxer which parses the Lyx format,can we
modify the eLyxer program and use this python-docx library(
https://github.com/python-openxml/python-docx) or anyother library which
helps in creating .docx files?In this way maybe we can also inject metadata
which MS Word ignores.Since we already have the .docx---.lyx converter
written by Rob(http://blog.oak-tree.us/index.php/2012/03/08/word2lyx01-2)
we can modify it to read the metadata also.I feel we should be able to do a
roundtrip conversion this way but i am not sure of the math part.I mean i
should read more how can we convert mathematical expressions from .lyx to
.docx. Can someone please brief me on what's the crucial information that
is absent in Lyx but produced by Latex?

I also had a look at pandoc and tex4ht but as they are converters from
Latex,i feel we should only consider them as secondary options.

I am new to the Lyx community so please forgive me if you find any of my
suggestions too lame because i may not have complete overview and insight
into things.Also it would be great if someone could provide me links to
understand the .lyx format.I wrote a simple .lyx file and opened it in a
text editor and found a lot of stuff,i think i should be able to understand
this properly if i want to parse a .lyx file and convert it to something
else

Thanks and Regards
Prannoy Pilligundla
ᐧ

Re: [GSoC 2014]Interested in Round trip conversion between LyX and .docx formats

[Prannoy Pilligundla]

ᐧ

stefano franchi wrote:

  Well, pandoc handles LaTex already (although not very successfully in
  my tests. Management of citation, for instance leaves a lot to be
  desired), so all it's missing is a docx reader to make the
  back-conversion possible.
 
  That is, I understand pandoc to work this way:
 
  Reader module from format X produces --- internal representation in
  pandoc format which is used by -- writer module to produce format Y
 
  So we would need to add a doc writer module and possibly a lyx reader
 module.
  I assume both would have to be written in Haskell (haven't really
  looked carefully into this).
 

 Correction after morning coffee:

 The needed modules would be:

 1. a docx|odt reader module
 2. (possibly) a LyX reader module


I feel we need to decide on the minimum set of features to support first.If
we want the features like cross references,bibliography,Indexes etc which
are  there in Latex but not Lyx,we can use pandoc but then we need to think
on how to get back from docx\odt to Lyx. Otherwise as we have access to the
parsed data of Lyx then we can go ahead in these lines and decide on how to
convert to docx|odt. Before deciding to write reader modules for Lyx and
docx|odt in pandoc i feel we should think on what are the formats that we
want to support in the future and seeing whether pandoc has support for
them or not.One advantage i see is that if we write a reader module for
pandoc then we can convert it into both into docx and odt(reverse is still
a problem).But since the results are also poor in pandoc,we should think
twice before choosing this way.

If we decide not to go with pandoc then question comes back to which format
needs to be supported first,docx or odt. If we are targeting docx,i still
feel we can modify elyxer and use some python docx library for converting
into docx and then modifying and using Rob's program for getting back .lyx
and completing the round trip

Or we may do something like what Rainer had suggested earlier in this
thread.I am quoting him

1) read supported round-trip feature list from config file
1) extract metadata, i.e. features which are not supported by round-trip,
into file
2) convert remaining round-trip-suitable data into new format
3) possibly merge metadata into file, or leave in sidecar file
- file goes away
- do something in other format (edits, ...)
- file returns
4) extract metadata, i.e. features which are not supported by
round-trip, from file / sidecar file
5) convert remaining round-trip-suitable data into lyx format
6) merge metadata back into lyx file 

This way we maybe we can  extend support to many formats in the future but
we need to think on what we need to support first.I have no experience to
comment on the feasibility of this

Re: [GSoC 2014]Interested in Round trip conversion between LyX and .docx formats

[Prannoy Pilligundla]

I have been following the discussion going on in this thread and have been
exploring Lyx at the same time.I understood how to integrate python scripts
into the editor and all but i have a some queries regarding the round trip
conversion

Since we have something like eLyxer which parses the Lyx format,can we
modify the eLyxer program and use this python-docx library(
https://github.com/python-openxml/python-docx) or anyother library which
helps in creating .docx files?In this way maybe we can also inject metadata
which MS Word ignores.Since we already have the .docx--->.lyx converter
written by Rob(http://blog.oak-tree.us/index.php/2012/03/08/word2lyx01-2)
we can modify it to read the metadata also.I feel we should be able to do a
roundtrip conversion this way but i am not sure of the math part.I mean i
should read more how can we convert mathematical expressions from .lyx to
.docx. Can someone please brief me on what's the crucial information that
is absent in Lyx but produced by Latex?

I also had a look at pandoc and tex4ht but as they are converters from
Latex,i feel we should only consider them as secondary options.

I am new to the Lyx community so please forgive me if you find any of my
suggestions too lame because i may not have complete overview and insight
into things.Also it would be great if someone could provide me links to
understand the .lyx format.I wrote a simple .lyx file and opened it in a
text editor and found a lot of stuff,i think i should be able to understand
this properly if i want to parse a .lyx file and convert it to something
else

Thanks and Regards
Prannoy Pilligundla
ᐧ

Re: [GSoC 2014]Interested in Round trip conversion between LyX and .docx formats

[Prannoy Pilligundla]

ᐧ

stefano franchi wrote:
>
> > Well, pandoc handles LaTex already (although not very successfully in
> > my tests. Management of citation, for instance leaves a lot to be
> > desired), so all it's missing is a docx "reader" to make the
> > back-conversion possible.
> >
> > That is, I understand pandoc to work this way:
> >
> > Reader module from format X produces ---> internal representation in
> > pandoc format which is used by --> writer module to produce format Y
> >
> > So we would need to add a doc writer module and possibly a lyx reader
> module.
> > I assume both would have to be written in Haskell (haven't really
> > looked carefully into this).
> >
>
> Correction after morning coffee:
>
> The needed modules would be:
>
> 1. a docx|odt reader module
> 2. (possibly) a LyX reader module
>

I feel we need to decide on the minimum set of features to support first.If
we want the features like cross references,bibliography,Indexes etc which
are  there in Latex but not Lyx,we can use pandoc but then we need to think
on how to get back from docx\odt to Lyx. Otherwise as we have access to the
parsed data of Lyx then we can go ahead in these lines and decide on how to
convert to docx|odt. Before deciding to write reader modules for Lyx and
docx|odt in pandoc i feel we should think on what are the formats that we
want to support in the future and seeing whether pandoc has support for
them or not.One advantage i see is that if we write a reader module for
pandoc then we can convert it into both into docx and odt(reverse is still
a problem).But since the results are also poor in pandoc,we should think
twice before choosing this way.

If we decide not to go with pandoc then question comes back to which format
needs to be supported first,docx or odt. If we are targeting docx,i still
feel we can modify elyxer and use some python docx library for converting
into docx and then modifying and using Rob's program for getting back .lyx
and completing the round trip

Or we may do something like what Rainer had suggested earlier in this
thread.I am quoting him

"1) read supported round-trip feature list from config file
1) extract metadata, i.e. features which are not supported by round-trip,
into file
2) convert remaining round-trip-suitable data into new format
3) possibly merge metadata into file, or leave in sidecar file
- file goes away
- do something in other format (edits, ...)
- file returns
4) extract metadata, i.e. features which are not supported by
round-trip, from file / sidecar file
5) convert remaining round-trip-suitable data into lyx format
6) merge metadata back into lyx file "

This way we maybe we can  extend support to many formats in the future but
we need to think on what we need to support first.I have no experience to
comment on the feasibility of this

Contribution license

[Prannoy Pilligundla]

I hereby license my contributions to LyX under the General Public
License, Version 2 or any later version

Prannoy Pilligundla

ᐧ

Re: Diff for Ticket #8816

[Prannoy Pilligundla]

ᐧ

There was one whitespace error in the LyXRC.h file.I am sorry for the
carelessness

On Tue, Feb 25, 2014 at 11:05 AM, Pavel Sanda sa...@lyx.org wrote:

 Prannoy Pilligundla wrote:
  index ce78d29..4ffe7d6 100644
  --- a/src/frontends/qt4/GuiView.cpp
  +++ b/src/frontends/qt4/GuiView.cpp
  @@ -3879,7 +3879,9 @@ void GuiView::toggleFullScreen()
setContentsMargins(-2, -2, -2, -2);
saveLayout();
setWindowState(windowState() ^ Qt::WindowFullScreen);
  - statusBar()-hide();
  + //statusBar()-hide();

 this line can be completely kicked out


Do i have to send an other patch with this change?

Re: Diff for Ticket #8816

[Prannoy Pilligundla]

I did send my GPL mail and i removed the unwanted comment that Pavel had
pointed out.I am attaching both the patches

Thanks and Regards
Prannoy Pilligundla
ᐧ


On Tue, Feb 25, 2014 at 4:06 PM, Prannoy Pilligundla prannoy.b...@gmail.com
 wrote:

 ᐧ

 There was one whitespace error in the LyXRC.h file.I am sorry for the
 carelessness

 On Tue, Feb 25, 2014 at 11:05 AM, Pavel Sanda sa...@lyx.org wrote:

 Prannoy Pilligundla wrote:
  index ce78d29..4ffe7d6 100644
  --- a/src/frontends/qt4/GuiView.cpp
  +++ b/src/frontends/qt4/GuiView.cpp
  @@ -3879,7 +3879,9 @@ void GuiView::toggleFullScreen()
setContentsMargins(-2, -2, -2, -2);
saveLayout();
setWindowState(windowState() ^ Qt::WindowFullScreen);
  - statusBar()-hide();
  + //statusBar()-hide();

 this line can be completely kicked out


 Do i have to send an other patch with this change?


From ee2fb5b24ad03bb31c27dc09e352dbec3eb55951 Mon Sep 17 00:00:00 2001
From: Prannoy Pilligundla prannoyp.1...@gmail.com
Date: Tue, 25 Feb 2014 09:29:24 +0530
Subject: [PATCH 1/2] Fix Ticket #8816

---
 src/LyXRC.cpp  |   14 ++
 src/LyXRC.h|3 +++
 src/frontends/qt4/GuiPrefs.cpp |4 
 src/frontends/qt4/GuiView.cpp  |4 +++-
 src/frontends/qt4/ui/PrefEditUi.ui |7 +++
 5 files changed, 31 insertions(+), 1 deletion(-)

diff --git a/src/LyXRC.cpp b/src/LyXRC.cpp
index c0a6467..8b186f9 100644
--- a/src/LyXRC.cpp
+++ b/src/LyXRC.cpp
@@ -110,6 +110,7 @@ LexerKeyword lyxrcTags[] = {
 	{ \\fullscreen_limit, LyXRC::RC_FULL_SCREEN_LIMIT },
 	{ \\fullscreen_menubar, LyXRC::RC_FULL_SCREEN_MENUBAR },
 	{ \\fullscreen_scrollbar, LyXRC::RC_FULL_SCREEN_SCROLLBAR },
+{ \\fullscreen_statusbar, LyXRC::RC_FULL_SCREEN_STATUSBAR },
 	{ \\fullscreen_tabbar, LyXRC::RC_FULL_SCREEN_TABBAR },
 	{ \\fullscreen_toolbars, LyXRC::RC_FULL_SCREEN_TOOLBARS },
 	{ \\fullscreen_width, LyXRC::RC_FULL_SCREEN_WIDTH },
@@ -1237,6 +1238,9 @@ LyXRC::ReturnValues LyXRC::read(Lexer  lexrc, bool check_format)
 		case RC_FULL_SCREEN_SCROLLBAR:
 			lexrc  full_screen_scrollbar;
 			break;
+case RC_FULL_SCREEN_STATUSBAR:
+			lexrc  full_screen_statusbar;
+			break;
 		case RC_FULL_SCREEN_TABBAR:
 			lexrc  full_screen_tabbar;
 			break;
@@ -1945,6 +1949,15 @@ void LyXRC::write(ostream  os, bool ignore_system_lyxrc, string const  name) c
 		}
 		if (tag != RC_LAST)
 			break;
+case RC_FULL_SCREEN_STATUSBAR:
+		if (ignore_system_lyxrc ||
+		full_screen_statusbar != system_lyxrc.full_screen_statusbar) {
+			os  \\fullscreen_statusbar 
+			convertstring(full_screen_statusbar)
+			'\n';
+		}
+		if (tag != RC_LAST)
+			break;
 	case RC_FULL_SCREEN_TABBAR:
 		if (ignore_system_lyxrc ||
 		full_screen_tabbar != system_lyxrc.full_screen_tabbar) {
@@ -3061,6 +3074,7 @@ void actOnUpdatedPrefs(LyXRC const  lyxrc_orig, LyXRC const  lyxrc_new)
 	case LyXRC::RC_FULL_SCREEN_LIMIT:
 	case LyXRC::RC_FULL_SCREEN_SCROLLBAR:
 	case LyXRC::RC_FULL_SCREEN_MENUBAR:
+case LyXRC::RC_FULL_SCREEN_STATUSBAR:
 	case LyXRC::RC_FULL_SCREEN_TABBAR:
 	case LyXRC::RC_FULL_SCREEN_TOOLBARS:
 	case LyXRC::RC_FULL_SCREEN_WIDTH:
diff --git a/src/LyXRC.h b/src/LyXRC.h
index 94914cc..9a45f93 100644
--- a/src/LyXRC.h
+++ b/src/LyXRC.h
@@ -86,6 +86,7 @@ public:
 		RC_FORWARD_SEARCH_PDF,
 		RC_FULL_SCREEN_LIMIT,
 		RC_FULL_SCREEN_SCROLLBAR,
+RC_FULL_SCREEN_STATUSBAR,
 		RC_FULL_SCREEN_TABBAR,
 		RC_FULL_SCREEN_MENUBAR,
 		RC_FULL_SCREEN_TOOLBARS,
@@ -499,6 +500,8 @@ public:
 	bool full_screen_tabbar;
 	/// Toggle menubar in fullscreen mode?
 	bool full_screen_menubar;
+	///Toggle statusbar in fullscreen mode?
+bool full_screen_statusbar;
 	/// Limit the text width?
 	bool full_screen_limit;
 	/// Width of limited screen (in pixels) in fullscreen mode
diff --git a/src/frontends/qt4/GuiPrefs.cpp b/src/frontends/qt4/GuiPrefs.cpp
index 8686690..feebf76 100644
--- a/src/frontends/qt4/GuiPrefs.cpp
+++ b/src/frontends/qt4/GuiPrefs.cpp
@@ -2723,6 +2723,8 @@ PrefEdit::PrefEdit(GuiPreferences * form)
 		this, SIGNAL(changed()));
 	connect(toggleScrollbarCB, SIGNAL(toggled(bool)),
 		this, SIGNAL(changed()));
+connect(toggleStatusbarCB, SIGNAL(toggled(bool)),
+		this, SIGNAL(changed()));
 	connect(toggleToolbarsCB, SIGNAL(toggled(bool)),
 		this, SIGNAL(changed()));
 }
@@ -2743,6 +2745,7 @@ void PrefEdit::apply(LyXRC  rc) const
 	rc.cursor_width = cursorWidthSB-value();
 	rc.full_screen_toolbars = toggleToolbarsCB-isChecked();
 	rc.full_screen_scrollbar = toggleScrollbarCB-isChecked();
+rc.full_screen_statusbar = toggleStatusbarCB-isChecked();
 	rc.full_screen_tabbar = toggleTabbarCB-isChecked();
 	rc.full_screen_menubar = toggleMenubarCB-isChecked();
 	rc.full_screen_width = fullscreenWidthSB-value();
@@ -2760,6 +2763,7 @@ void PrefEdit::update(LyXRC const  rc)
 	macroEditStyleCO-setCurrentIndex(rc.macro_edit_style

Re: Diff for Ticket #8816

[Prannoy Pilligundla]

Thanks for the approval
ᐧ


On Wed, Feb 26, 2014 at 7:24 AM, Richard Heck rgh...@lyx.org wrote:

  On 02/25/2014 12:40 PM, Prannoy Pilligundla wrote:

 I did send my GPL mail and i removed the unwanted comment that Pavel had
 pointed out.I am attaching both the patches


 Committed. Thanks.

 rh



  Thanks and Regards
 Prannoy Pilligundla
  ᐧ


 On Tue, Feb 25, 2014 at 4:06 PM, Prannoy Pilligundla 
 prannoy.b...@gmail.com wrote:

  ᐧ

  There was one whitespace error in the LyXRC.h file.I am sorry for the
 carelessness

   On Tue, Feb 25, 2014 at 11:05 AM, Pavel Sanda sa...@lyx.org wrote:

 Prannoy Pilligundla wrote:
  index ce78d29..4ffe7d6 100644
  --- a/src/frontends/qt4/GuiView.cpp
  +++ b/src/frontends/qt4/GuiView.cpp
  @@ -3879,7 +3879,9 @@ void GuiView::toggleFullScreen()
setContentsMargins(-2, -2, -2, -2);
saveLayout();
setWindowState(windowState() ^ Qt::WindowFullScreen);
  - statusBar()-hide();
  + //statusBar()-hide();

 this line can be completely kicked out


   Do i have to send an other patch with this change?

Contribution license

[Prannoy Pilligundla]

I hereby license my contributions to LyX under the General Public
License, Version 2 or any later version

Prannoy Pilligundla

ᐧ

Re: Diff for Ticket #8816

[Prannoy Pilligundla]

ᐧ

There was one whitespace error in the LyXRC.h file.I am sorry for the
carelessness

On Tue, Feb 25, 2014 at 11:05 AM, Pavel Sanda <sa...@lyx.org> wrote:

> Prannoy Pilligundla wrote:
> > index ce78d29..4ffe7d6 100644
> > --- a/src/frontends/qt4/GuiView.cpp
> > +++ b/src/frontends/qt4/GuiView.cpp
> > @@ -3879,7 +3879,9 @@ void GuiView::toggleFullScreen()
> >   setContentsMargins(-2, -2, -2, -2);
> >   saveLayout();
> >   setWindowState(windowState() ^ Qt::WindowFullScreen);
> > - statusBar()->hide();
> > + //statusBar()->hide();
>
> this line can be completely kicked out


Do i have to send an other patch with this change?

Re: Diff for Ticket #8816

[Prannoy Pilligundla]

I did send my GPL mail and i removed the unwanted comment that Pavel had
pointed out.I am attaching both the patches

Thanks and Regards
Prannoy Pilligundla
ᐧ


On Tue, Feb 25, 2014 at 4:06 PM, Prannoy Pilligundla <prannoy.b...@gmail.com
> wrote:

> ᐧ
>
> There was one whitespace error in the LyXRC.h file.I am sorry for the
> carelessness
>
> On Tue, Feb 25, 2014 at 11:05 AM, Pavel Sanda <sa...@lyx.org> wrote:
>
>> Prannoy Pilligundla wrote:
>> > index ce78d29..4ffe7d6 100644
>> > --- a/src/frontends/qt4/GuiView.cpp
>> > +++ b/src/frontends/qt4/GuiView.cpp
>> > @@ -3879,7 +3879,9 @@ void GuiView::toggleFullScreen()
>> >   setContentsMargins(-2, -2, -2, -2);
>> >   saveLayout();
>> >   setWindowState(windowState() ^ Qt::WindowFullScreen);
>> > - statusBar()->hide();
>> > + //statusBar()->hide();
>>
>> this line can be completely kicked out
>
>
> Do i have to send an other patch with this change?
>
>
From ee2fb5b24ad03bb31c27dc09e352dbec3eb55951 Mon Sep 17 00:00:00 2001
From: Prannoy Pilligundla <prannoyp.1...@gmail.com>
Date: Tue, 25 Feb 2014 09:29:24 +0530
Subject: [PATCH 1/2] Fix Ticket #8816

---
 src/LyXRC.cpp  |   14 ++
 src/LyXRC.h|3 +++
 src/frontends/qt4/GuiPrefs.cpp |4 
 src/frontends/qt4/GuiView.cpp  |4 +++-
 src/frontends/qt4/ui/PrefEditUi.ui |7 +++
 5 files changed, 31 insertions(+), 1 deletion(-)

diff --git a/src/LyXRC.cpp b/src/LyXRC.cpp
index c0a6467..8b186f9 100644
--- a/src/LyXRC.cpp
+++ b/src/LyXRC.cpp
@@ -110,6 +110,7 @@ LexerKeyword lyxrcTags[] = {
 	{ "\\fullscreen_limit", LyXRC::RC_FULL_SCREEN_LIMIT },
 	{ "\\fullscreen_menubar", LyXRC::RC_FULL_SCREEN_MENUBAR },
 	{ "\\fullscreen_scrollbar", LyXRC::RC_FULL_SCREEN_SCROLLBAR },
+{ "\\fullscreen_statusbar", LyXRC::RC_FULL_SCREEN_STATUSBAR },
 	{ "\\fullscreen_tabbar", LyXRC::RC_FULL_SCREEN_TABBAR },
 	{ "\\fullscreen_toolbars", LyXRC::RC_FULL_SCREEN_TOOLBARS },
 	{ "\\fullscreen_width", LyXRC::RC_FULL_SCREEN_WIDTH },
@@ -1237,6 +1238,9 @@ LyXRC::ReturnValues LyXRC::read(Lexer & lexrc, bool check_format)
 		case RC_FULL_SCREEN_SCROLLBAR:
 			lexrc >> full_screen_scrollbar;
 			break;
+case RC_FULL_SCREEN_STATUSBAR:
+			lexrc >> full_screen_statusbar;
+			break;
 		case RC_FULL_SCREEN_TABBAR:
 			lexrc >> full_screen_tabbar;
 			break;
@@ -1945,6 +1949,15 @@ void LyXRC::write(ostream & os, bool ignore_system_lyxrc, string const & name) c
 		}
 		if (tag != RC_LAST)
 			break;
+case RC_FULL_SCREEN_STATUSBAR:
+		if (ignore_system_lyxrc ||
+		full_screen_statusbar != system_lyxrc.full_screen_statusbar) {
+			os << "\\fullscreen_statusbar "
+			   << convert(full_screen_statusbar)
+			   << '\n';
+		}
+		if (tag != RC_LAST)
+			break;
 	case RC_FULL_SCREEN_TABBAR:
 		if (ignore_system_lyxrc ||
 		full_screen_tabbar != system_lyxrc.full_screen_tabbar) {
@@ -3061,6 +3074,7 @@ void actOnUpdatedPrefs(LyXRC const & lyxrc_orig, LyXRC const & lyxrc_new)
 	case LyXRC::RC_FULL_SCREEN_LIMIT:
 	case LyXRC::RC_FULL_SCREEN_SCROLLBAR:
 	case LyXRC::RC_FULL_SCREEN_MENUBAR:
+case LyXRC::RC_FULL_SCREEN_STATUSBAR:
 	case LyXRC::RC_FULL_SCREEN_TABBAR:
 	case LyXRC::RC_FULL_SCREEN_TOOLBARS:
 	case LyXRC::RC_FULL_SCREEN_WIDTH:
diff --git a/src/LyXRC.h b/src/LyXRC.h
index 94914cc..9a45f93 100644
--- a/src/LyXRC.h
+++ b/src/LyXRC.h
@@ -86,6 +86,7 @@ public:
 		RC_FORWARD_SEARCH_PDF,
 		RC_FULL_SCREEN_LIMIT,
 		RC_FULL_SCREEN_SCROLLBAR,
+RC_FULL_SCREEN_STATUSBAR,
 		RC_FULL_SCREEN_TABBAR,
 		RC_FULL_SCREEN_MENUBAR,
 		RC_FULL_SCREEN_TOOLBARS,
@@ -499,6 +500,8 @@ public:
 	bool full_screen_tabbar;
 	/// Toggle menubar in fullscreen mode?
 	bool full_screen_menubar;
+	///Toggle statusbar in fullscreen mode?
+bool full_screen_statusbar;
 	/// Limit the text width?
 	bool full_screen_limit;
 	/// Width of limited screen (in pixels) in fullscreen mode
diff --git a/src/frontends/qt4/GuiPrefs.cpp b/src/frontends/qt4/GuiPrefs.cpp
index 8686690..feebf76 100644
--- a/src/frontends/qt4/GuiPrefs.cpp
+++ b/src/frontends/qt4/GuiPrefs.cpp
@@ -2723,6 +2723,8 @@ PrefEdit::PrefEdit(GuiPreferences * form)
 		this, SIGNAL(changed()));
 	connect(toggleScrollbarCB, SIGNAL(toggled(bool)),
 		this, SIGNAL(changed()));
+connect(toggleStatusbarCB, SIGNAL(toggled(bool)),
+		this, SIGNAL(changed()));
 	connect(toggleToolbarsCB, SIGNAL(toggled(bool)),
 		this, SIGNAL(changed()));
 }
@@ -2743,6 +2745,7 @@ void PrefEdit::apply(LyXRC & rc) const
 	rc.cursor_width = cursorWidthSB->value();
 	rc.full_screen_toolbars = toggleToolbarsCB->isChecked();
 	rc.full_screen_scrollb

Re: Diff for Ticket #8816

[Prannoy Pilligundla]

Thanks for the approval
ᐧ


On Wed, Feb 26, 2014 at 7:24 AM, Richard Heck <rgh...@lyx.org> wrote:

>  On 02/25/2014 12:40 PM, Prannoy Pilligundla wrote:
>
> I did send my GPL mail and i removed the unwanted comment that Pavel had
> pointed out.I am attaching both the patches
>
>
> Committed. Thanks.
>
> rh
>
>
>
>  Thanks and Regards
> Prannoy Pilligundla
>  ᐧ
>
>
> On Tue, Feb 25, 2014 at 4:06 PM, Prannoy Pilligundla <
> prannoy.b...@gmail.com> wrote:
>
>>  ᐧ
>>
>>  There was one whitespace error in the LyXRC.h file.I am sorry for the
>> carelessness
>>
>>   On Tue, Feb 25, 2014 at 11:05 AM, Pavel Sanda <sa...@lyx.org> wrote:
>>
>>> Prannoy Pilligundla wrote:
>>> > index ce78d29..4ffe7d6 100644
>>> > --- a/src/frontends/qt4/GuiView.cpp
>>> > +++ b/src/frontends/qt4/GuiView.cpp
>>> > @@ -3879,7 +3879,9 @@ void GuiView::toggleFullScreen()
>>> >   setContentsMargins(-2, -2, -2, -2);
>>> >   saveLayout();
>>> >   setWindowState(windowState() ^ Qt::WindowFullScreen);
>>> > - statusBar()->hide();
>>> > + //statusBar()->hide();
>>>
>>> this line can be completely kicked out
>>
>>
>>   Do i have to send an other patch with this change?
>>
>>
>
>

Re: [GSoC 2014]Interested in Round trip conversion between LyX and .docx formats

[Prannoy Pilligundla]

 and Regards
Prannoy Pilligundla

Diff for Ticket #8816

[Prannoy Pilligundla]

Hi Everyone,

I am Prannoy Pilligundla from BITS-Pilani,India and i am a newcomer to the
LyX community.I added the feature of Allowing configuration of status bar
visibility in the fullscreen mode listed here
http://www.lyx.org/trac/ticket/8816

I am attaching a diff file to this mail.I am not aware of the formal
procedure of submitting a diff,forgive me for my mistakes if any and please
guide me by pointing out my mistakes.

Looking forward to hear from you guys

​
 
Ticket#8816.diffhttps://docs.google.com/file/d/0B08XpIdbyToXRy1NenpkaFhQdjA/edit?usp=drive_web
​
ᐧ

Re: Diff for Ticket #8816

[Prannoy Pilligundla]

Thanks for the reply Richard.

I dont know why but the size of the diff is around 29MB. I think i made
some mistake while making a patch maybe.Can you guide me through this?

I actually made two commits but after doing one commit i pulled the code
and merged it.While making the first commit lot of files which i didn't
change like *.gmo and *.po got added.Then i realized there was a small bug
in the code,so i changed it and made a commit again.The patch after the
second commit is small but there is a pull in between.I am confused on how
to proceed

Thanks and Regards
Prannoy Pilligundla
ᐧ


On Mon, Feb 24, 2014 at 8:52 PM, Richard Heck rgh...@lyx.org wrote:

  On 02/24/2014 08:07 AM, Prannoy Pilligundla wrote:

  Hi Everyone,

  I am Prannoy Pilligundla from BITS-Pilani,India and i am a newcomer to
 the LyX community.I added the feature of Allowing configuration of
 status bar visibility in the fullscreen mode listed here
 http://www.lyx.org/trac/ticket/8816

  I am attaching a diff file to this mail.I am not aware of the formal
 procedure of submitting a diff,forgive me for my mistakes if any and please
 guide me by pointing out my mistakes.


 Thanks for the submission. Unfortunately, though, the patch seems to be on
 a Google Drive somewhere, to which none of us would have access. Can you
 just attach it as a text file? Alternatively, attach it to the bug itself.

 Richard

Re: Diff for Ticket #8816

[Prannoy Pilligundla]

Thanks for the help Richard,i did fix it and made a patch.I am attaching
the patch to this mail
ᐧ


On Tue, Feb 25, 2014 at 1:59 AM, Richard Heck rgh...@lyx.org wrote:

  On 02/24/2014 10:53 AM, Prannoy Pilligundla wrote:

 Thanks for the reply Richard.

  I dont know why but the size of the diff is around 29MB. I think i made
 some mistake while making a patch maybe.Can you guide me through this?

 I actually made two commits but after doing one commit i pulled the code
 and merged it.While making the first commit lot of files which i didn't
 change like *.gmo and *.po got added.Then i realized there was a small bug
 in the code,so i changed it and made a commit again.The patch after the
 second commit is small but there is a pull in between.I am confused on how
 to proceed


 Yes, these po and gmo changes usually happen when you first configure.
 They can be reverted at that point.

 Can you post the output of git log -n 10? We can probably do an
 interactive rebase to fix things.

 Richard



  On Mon, Feb 24, 2014 at 8:52 PM, Richard Heck rgh...@lyx.org wrote:

  On 02/24/2014 08:07 AM, Prannoy Pilligundla wrote:

  Hi Everyone,

  I am Prannoy Pilligundla from BITS-Pilani,India and i am a newcomer to
 the LyX community.I added the feature of Allowing configuration of
 status bar visibility in the fullscreen mode listed here
 http://www.lyx.org/trac/ticket/8816

  I am attaching a diff file to this mail.I am not aware of the formal
 procedure of submitting a diff,forgive me for my mistakes if any and please
 guide me by pointing out my mistakes.


  Thanks for the submission. Unfortunately, though, the patch seems to be
 on a Google Drive somewhere, to which none of us would have access. Can you
 just attach it as a text file? Alternatively, attach it to the bug itself.

 Richard





From ee2fb5b24ad03bb31c27dc09e352dbec3eb55951 Mon Sep 17 00:00:00 2001
From: Prannoy Pilligundla prannoyp.1...@gmail.com
Date: Tue, 25 Feb 2014 09:29:24 +0530
Subject: [PATCH 1/1] Fix Ticket #8816

---
 src/LyXRC.cpp  |   14 ++
 src/LyXRC.h|3 +++
 src/frontends/qt4/GuiPrefs.cpp |4 
 src/frontends/qt4/GuiView.cpp  |4 +++-
 src/frontends/qt4/ui/PrefEditUi.ui |7 +++
 5 files changed, 31 insertions(+), 1 deletion(-)

diff --git a/src/LyXRC.cpp b/src/LyXRC.cpp
index c0a6467..8b186f9 100644
--- a/src/LyXRC.cpp
+++ b/src/LyXRC.cpp
@@ -110,6 +110,7 @@ LexerKeyword lyxrcTags[] = {
 	{ \\fullscreen_limit, LyXRC::RC_FULL_SCREEN_LIMIT },
 	{ \\fullscreen_menubar, LyXRC::RC_FULL_SCREEN_MENUBAR },
 	{ \\fullscreen_scrollbar, LyXRC::RC_FULL_SCREEN_SCROLLBAR },
+{ \\fullscreen_statusbar, LyXRC::RC_FULL_SCREEN_STATUSBAR },
 	{ \\fullscreen_tabbar, LyXRC::RC_FULL_SCREEN_TABBAR },
 	{ \\fullscreen_toolbars, LyXRC::RC_FULL_SCREEN_TOOLBARS },
 	{ \\fullscreen_width, LyXRC::RC_FULL_SCREEN_WIDTH },
@@ -1237,6 +1238,9 @@ LyXRC::ReturnValues LyXRC::read(Lexer  lexrc, bool check_format)
 		case RC_FULL_SCREEN_SCROLLBAR:
 			lexrc  full_screen_scrollbar;
 			break;
+case RC_FULL_SCREEN_STATUSBAR:
+			lexrc  full_screen_statusbar;
+			break;
 		case RC_FULL_SCREEN_TABBAR:
 			lexrc  full_screen_tabbar;
 			break;
@@ -1945,6 +1949,15 @@ void LyXRC::write(ostream  os, bool ignore_system_lyxrc, string const  name) c
 		}
 		if (tag != RC_LAST)
 			break;
+case RC_FULL_SCREEN_STATUSBAR:
+		if (ignore_system_lyxrc ||
+		full_screen_statusbar != system_lyxrc.full_screen_statusbar) {
+			os  \\fullscreen_statusbar 
+			convertstring(full_screen_statusbar)
+			'\n';
+		}
+		if (tag != RC_LAST)
+			break;
 	case RC_FULL_SCREEN_TABBAR:
 		if (ignore_system_lyxrc ||
 		full_screen_tabbar != system_lyxrc.full_screen_tabbar) {
@@ -3061,6 +3074,7 @@ void actOnUpdatedPrefs(LyXRC const  lyxrc_orig, LyXRC const  lyxrc_new)
 	case LyXRC::RC_FULL_SCREEN_LIMIT:
 	case LyXRC::RC_FULL_SCREEN_SCROLLBAR:
 	case LyXRC::RC_FULL_SCREEN_MENUBAR:
+case LyXRC::RC_FULL_SCREEN_STATUSBAR:
 	case LyXRC::RC_FULL_SCREEN_TABBAR:
 	case LyXRC::RC_FULL_SCREEN_TOOLBARS:
 	case LyXRC::RC_FULL_SCREEN_WIDTH:
diff --git a/src/LyXRC.h b/src/LyXRC.h
index 94914cc..9a45f93 100644
--- a/src/LyXRC.h
+++ b/src/LyXRC.h
@@ -86,6 +86,7 @@ public:
 		RC_FORWARD_SEARCH_PDF,
 		RC_FULL_SCREEN_LIMIT,
 		RC_FULL_SCREEN_SCROLLBAR,
+RC_FULL_SCREEN_STATUSBAR,
 		RC_FULL_SCREEN_TABBAR,
 		RC_FULL_SCREEN_MENUBAR,
 		RC_FULL_SCREEN_TOOLBARS,
@@ -499,6 +500,8 @@ public:
 	bool full_screen_tabbar;
 	/// Toggle menubar in fullscreen mode?
 	bool full_screen_menubar;
+	///Toggle statusbar in fullscreen mode?
+bool full_screen_statusbar;
 	/// Limit the text width?
 	bool full_screen_limit;
 	/// Width of limited screen (in pixels) in fullscreen mode
diff --git a/src/frontends/qt4/GuiPrefs.cpp b/src/frontends/qt4/GuiPrefs.cpp
index 8686690..feebf76 100644
--- a/src/frontends/qt4/GuiPrefs.cpp
+++ b/src/frontends/qt4/GuiPrefs.cpp
@@ -2723,6 +2723,8

Re: [GSoC 2014]Interested in Round trip conversion between LyX and .docx formats

[Prannoy Pilligundla]

h yet,
>   but my first impression is that Microsoft's is  more complex.
>

I did go through the complete conversion in the thread you had posted and i
basically understood the project's motives.I was working on fixing the bug
so didn't go deep into the technicalities of the project.Now that i fixed
that bug,i will start exploring more about this and reply back on this
thread with my opinions or questions


Thanks and Regards
Prannoy Pilligundla

>

Diff for Ticket #8816

[Prannoy Pilligundla]

Hi Everyone,

I am Prannoy Pilligundla from BITS-Pilani,India and i am a newcomer to the
LyX community.I added the feature of "Allowing configuration of status bar
visibility in the fullscreen mode" listed here
http://www.lyx.org/trac/ticket/8816

I am attaching a diff file to this mail.I am not aware of the formal
procedure of submitting a diff,forgive me for my mistakes if any and please
guide me by pointing out my mistakes.

Looking forward to hear from you guys

​
 
Ticket#8816.diff<https://docs.google.com/file/d/0B08XpIdbyToXRy1NenpkaFhQdjA/edit?usp=drive_web>
​
ᐧ

Re: Diff for Ticket #8816

[Prannoy Pilligundla]

Thanks for the reply Richard.

I dont know why but the size of the diff is around 29MB. I think i made
some mistake while making a patch maybe.Can you guide me through this?

I actually made two commits but after doing one commit i pulled the code
and merged it.While making the first commit lot of files which i didn't
change like *.gmo and *.po got added.Then i realized there was a small bug
in the code,so i changed it and made a commit again.The patch after the
second commit is small but there is a pull in between.I am confused on how
to proceed

Thanks and Regards
Prannoy Pilligundla
ᐧ


On Mon, Feb 24, 2014 at 8:52 PM, Richard Heck <rgh...@lyx.org> wrote:

>  On 02/24/2014 08:07 AM, Prannoy Pilligundla wrote:
>
>  Hi Everyone,
>
>  I am Prannoy Pilligundla from BITS-Pilani,India and i am a newcomer to
> the LyX community.I added the feature of "Allowing configuration of
> status bar visibility in the fullscreen mode" listed here
> http://www.lyx.org/trac/ticket/8816
>
>  I am attaching a diff file to this mail.I am not aware of the formal
> procedure of submitting a diff,forgive me for my mistakes if any and please
> guide me by pointing out my mistakes.
>
>
> Thanks for the submission. Unfortunately, though, the patch seems to be on
> a Google Drive somewhere, to which none of us would have access. Can you
> just attach it as a text file? Alternatively, attach it to the bug itself.
>
> Richard
>
>
>

Re: Diff for Ticket #8816

[Prannoy Pilligundla]

Thanks for the help Richard,i did fix it and made a patch.I am attaching
the patch to this mail
ᐧ


On Tue, Feb 25, 2014 at 1:59 AM, Richard Heck <rgh...@lyx.org> wrote:

>  On 02/24/2014 10:53 AM, Prannoy Pilligundla wrote:
>
> Thanks for the reply Richard.
>
>  I dont know why but the size of the diff is around 29MB. I think i made
> some mistake while making a patch maybe.Can you guide me through this?
>
> I actually made two commits but after doing one commit i pulled the code
> and merged it.While making the first commit lot of files which i didn't
> change like *.gmo and *.po got added.Then i realized there was a small bug
> in the code,so i changed it and made a commit again.The patch after the
> second commit is small but there is a pull in between.I am confused on how
> to proceed
>
>
> Yes, these po and gmo changes usually happen when you first configure.
> They can be reverted at that point.
>
> Can you post the output of "git log -n 10"? We can probably do an
> interactive rebase to fix things.
>
> Richard
>
>
>
>  On Mon, Feb 24, 2014 at 8:52 PM, Richard Heck <rgh...@lyx.org> wrote:
>
>>  On 02/24/2014 08:07 AM, Prannoy Pilligundla wrote:
>>
>>  Hi Everyone,
>>
>>  I am Prannoy Pilligundla from BITS-Pilani,India and i am a newcomer to
>> the LyX community.I added the feature of "Allowing configuration of
>> status bar visibility in the fullscreen mode" listed here
>> http://www.lyx.org/trac/ticket/8816
>>
>>  I am attaching a diff file to this mail.I am not aware of the formal
>> procedure of submitting a diff,forgive me for my mistakes if any and please
>> guide me by pointing out my mistakes.
>>
>>
>>  Thanks for the submission. Unfortunately, though, the patch seems to be
>> on a Google Drive somewhere, to which none of us would have access. Can you
>> just attach it as a text file? Alternatively, attach it to the bug itself.
>>
>> Richard
>>
>>
>>
>
>
From ee2fb5b24ad03bb31c27dc09e352dbec3eb55951 Mon Sep 17 00:00:00 2001
From: Prannoy Pilligundla <prannoyp.1...@gmail.com>
Date: Tue, 25 Feb 2014 09:29:24 +0530
Subject: [PATCH 1/1] Fix Ticket #8816

---
 src/LyXRC.cpp  |   14 ++
 src/LyXRC.h|3 +++
 src/frontends/qt4/GuiPrefs.cpp |4 
 src/frontends/qt4/GuiView.cpp  |4 +++-
 src/frontends/qt4/ui/PrefEditUi.ui |7 +++
 5 files changed, 31 insertions(+), 1 deletion(-)

diff --git a/src/LyXRC.cpp b/src/LyXRC.cpp
index c0a6467..8b186f9 100644
--- a/src/LyXRC.cpp
+++ b/src/LyXRC.cpp
@@ -110,6 +110,7 @@ LexerKeyword lyxrcTags[] = {
 	{ "\\fullscreen_limit", LyXRC::RC_FULL_SCREEN_LIMIT },
 	{ "\\fullscreen_menubar", LyXRC::RC_FULL_SCREEN_MENUBAR },
 	{ "\\fullscreen_scrollbar", LyXRC::RC_FULL_SCREEN_SCROLLBAR },
+{ "\\fullscreen_statusbar", LyXRC::RC_FULL_SCREEN_STATUSBAR },
 	{ "\\fullscreen_tabbar", LyXRC::RC_FULL_SCREEN_TABBAR },
 	{ "\\fullscreen_toolbars", LyXRC::RC_FULL_SCREEN_TOOLBARS },
 	{ "\\fullscreen_width", LyXRC::RC_FULL_SCREEN_WIDTH },
@@ -1237,6 +1238,9 @@ LyXRC::ReturnValues LyXRC::read(Lexer & lexrc, bool check_format)
 		case RC_FULL_SCREEN_SCROLLBAR:
 			lexrc >> full_screen_scrollbar;
 			break;
+case RC_FULL_SCREEN_STATUSBAR:
+			lexrc >> full_screen_statusbar;
+			break;
 		case RC_FULL_SCREEN_TABBAR:
 			lexrc >> full_screen_tabbar;
 			break;
@@ -1945,6 +1949,15 @@ void LyXRC::write(ostream & os, bool ignore_system_lyxrc, string const & name) c
 		}
 		if (tag != RC_LAST)
 			break;
+case RC_FULL_SCREEN_STATUSBAR:
+		if (ignore_system_lyxrc ||
+		full_screen_statusbar != system_lyxrc.full_screen_statusbar) {
+			os << "\\fullscreen_statusbar "
+			   << convert(full_screen_statusbar)
+			   << '\n';
+		}
+		if (tag != RC_LAST)
+			break;
 	case RC_FULL_SCREEN_TABBAR:
 		if (ignore_system_lyxrc ||
 		full_screen_tabbar != system_lyxrc.full_screen_tabbar) {
@@ -3061,6 +3074,7 @@ void actOnUpdatedPrefs(LyXRC const & lyxrc_orig, LyXRC const & lyxrc_new)
 	case LyXRC::RC_FULL_SCREEN_LIMIT:
 	case LyXRC::RC_FULL_SCREEN_SCROLLBAR:
 	case LyXRC::RC_FULL_SCREEN_MENUBAR:
+case LyXRC::RC_FULL_SCREEN_STATUSBAR:
 	case LyXRC::RC_FULL_SCREEN_TABBAR:
 	case LyXRC::RC_FULL_SCREEN_TOOLBARS:
 	case LyXRC::RC_FULL_SCREEN_WIDTH:
diff --git a/src/LyXRC.h b/src/LyXRC.h
index 94914cc..9a45f93 100644
--- a/src/LyXRC.h
+++ b/src/LyXRC.h
@@ -86,6 +86,7 @@ public:
 		RC_FORWARD_SEARCH_PDF,
 		RC_FULL_SCREEN_LIMIT,
 		RC_FULL_SCREEN_SCROLLBAR,
+RC_FULL_SCREEN_STATUSBAR,
 		RC_FULL_SCREEN_TABBAR,
 		RC_FULL_SCREEN_MENUBAR,
 		RC_FULL_SCREEN_TOOLBARS,
@@ -499,6 +500,

[GSoC 2014]Interested in Round trip conversion between LyX and .docx formats

[Prannoy Pilligundla]

Hi Everyone,

I am Prannoy Pilligundla pursuing undergraduation in BITS-Pilani,India.I am
proficient in C,Java,Python and RoR. Here is the link to my bitbucket
profile https://bitbucket.org/prannoy1994

I had a look at 2014 ideas page(
http://wiki.lyx.org/GSoC/GSoCProjectIdeasFor2014) and i am interested to
work on Round trip conversion between LyX and .docx formats. It would be
great if someone can guide me on how to start work on this.I want to get
accustomed to the existing code base and start contributing before writing
my application for GSoC 2014

Thanks and Regards
Prannoy Pilligundla
ᐧ

[GSoC 2014]Interested in Round trip conversion between LyX and .docx formats

[Prannoy Pilligundla]

Hi Everyone,

I am Prannoy Pilligundla pursuing undergraduation in BITS-Pilani,India.I am
proficient in C,Java,Python and RoR. Here is the link to my bitbucket
profile https://bitbucket.org/prannoy1994

I had a look at 2014 ideas page(
http://wiki.lyx.org/GSoC/GSoCProjectIdeasFor2014) and i am interested to
work on Round trip conversion between LyX and .docx formats. It would be
great if someone can guide me on how to start work on this.I want to get
accustomed to the existing code base and start contributing before writing
my application for GSoC 2014

Thanks and Regards
Prannoy Pilligundla
ᐧ