Okay, thanks.  I'll do some research on UTF-8 encoded text files.
Barton


On Mon, Jan 09, 2017 at 11:31 PM, Cathy Pinner wrote:
Sorry.

I have no idea.

I don't do web pages.

I just know where the various options for HTML output are in Legacy.



Cathy



BARTON LEWIS wrote:



Hi Cathy,



I tried that, but when I tried to open the page in my code editor

(Brackets), I got a message saying "Brackets currently only supports

UTF-8 encoded text files." I wonder if it's worth it to try a

different code editor? I assume that if I used one that were able to

open the page, it would already be formatted for me and I could make

global changes more easily than if I were trying to do so "from

scratch," is that true?



Thanks,



Barton







On Mon, Jan 09, 2017 at 10:23 PM, Cathy Pinner wrote:



    Barton,



    Why aren't you using the option of creating the Book
 report in

    HTML format and then editing that to add more?

    The option is in the same place you found the RTF option.



    Cathy



    gerald wrote:





    I don't know why you want to make all that extra work for yourself.

    Isn't there an option to publish web pages? In the Internet menu --

    there are all kinds of formats for the web pages you want -- you can

    customize them in so many ways Wouldn't that be much simpler?

    Just one

    click and it is done, without having to do any editing, although you

    can do that too, if you like. Or did I miss the point?

    *Sent:* Monday, January 09, 2017 at 5:36 PM

    *From:* "BARTON LEWIS" <[email protected]>

 
   *To:* "Legacy User Group" <[email protected]>

    *Cc:* "Legacy User Group " <[email protected]>

    *Subject:* Re: [LegacyUG] coding register reports (descendant book

    reports) for the web

    Thanks, Jennie, but no, I have not tried that as I want to actually

    enter the data as code (html) into my webpage.



    But I think I found the solution: if I export to rtf as a descendant

    book, as opposed to descendant narrative book, I do get tabs and

    spaces, each with a unique format depending on the generation. So I

    should be able to use either CSS or JS to manipulate the text into a

    particular format of my choosing.



    Barton







    On Mon, Jan 09, 2017 at 05:3
4 PM, Jennie Matheson wrote:



    Hi Lewis,

    Have you tried opening the report in a word processor such as Word

    and saving it as a web page - not sure if this will work, but it may

    Jennie

    On Tue, Jan 10, 2017 at 5:31 AM, BARTON LEWIS

    <[email protected] <mailto:[email protected]>> wrote:



    I am trying to figure out how to create custom-styled register

    reports ("descendant book reports" in Legacy parlance) for the

    web; I am building my genealogy website and would like to

    include the 1st 4 generations of my lines along with other

    data (images, narrative etc.) on individual pages. I exported

    a descendant book report to RTF. The result is a report which

    reta
ins formatting but uses ruler indents and if I just copy

    that text into a text editor, I will have to manually form at a

    lot of it using css. I was hoping to perhaps use Javascript to

    somehow format levels of text differently but I am not

    proficient in that language and don't know if I can do that.

    If anyone has had experience coding their own register reports

    to create cutom-styled formatting for the web, I would be

    interested in hearing. Thanks,



    Barton



    --





--



LegacyUserGroup mailing list

[email protected]

To manage your subscription and unsubscribe http://legacyusers.com/mailman/listinfo/legacyusergroup_legacyusers.com <http://legacyusers.com/mailman/listinfo/legacyusergroup_legacyusers.com>

Archives at:

http://www.mail-archive.com/[email protected]/ <http://www.mail-archive.com/[email protected]/>


-- 

LegacyUserGroup mailing list
[email protected]
To manage your subscription and unsubscribe 
http://legacyusers.com/mailman/listinfo/legacyusergroup_legacyusers.com
Archives at:
http://www.mail-archive.com/[email protected]/

Reply via email to