Curiously wondering if there's an explanation for all of these
various codings somewhere;
and if so, where?
From: Tim---Kracked_P_P---webmaster <webmaster@krackedpress.com>
Date: Sat, Nov 15, 2014 at 7:27 AM
Subject: Re: [libreoffice-users] Using LO Writer to edit HTML
To: users@global.libreoffice.org
Here is the list of languages that Bluefish's page states it has language
definitions for.
Yes there are a lot, but it seems to me that this package is more than a
HTML creation/modification page editor.
Ada
ASP .NET and VBS
C/C++
CSS
CFML
Clojure
D
gettext PO
Google Go
HTML, XHTML and HTML5
Java and JSP
JavaScript and jQuery
Lua
Octave/MATLAB
MediaWiki
NSIS
Pascal
Perl
PHP
Python
R
Ruby
Shell
Scheme
SQL
SVG
Vala
Wordpress
XML
On 11/14/2014 09:55 PM, Tom Davies wrote:
Hi :)
I think the coding is to be published in a book / manual / guide.
Perhaps
teaching people the basics or giving appropriate examples.
I think Ian was looking for some method to use coding in a document in
much
the same way that Math is used to write equations for documents so that
the
equation can be seen. We have been trying to push him into using the
equivalent of Calc to give the correct answer when he's really looking
for
something to show the equation in all it's intriguing beauty.
Bluefish is often recommended and i gather it's a bit like Dreamweaver in
having a wysiwyg alongside a coding window/pane. I only had a brief go
at
both those but they made me feel really uncomfortable. Real world
web-browsers have their own quirks and i'm not sure how faithfully a
wysiwyg editor reproduces their errors. So, i tend to have at least 1
web-browser open to see the real-world effect of code that i write (well,
mostly copy&paste & modify tbh) in a text-editor.
It's interesting to see this thread has forked in 2 directions. There
are
these sorts of answers on how to write good, reliable code to be used
directly and the other fork is about how to make it look pretty for
print.
Regards from
Tom :)
On 15 November 2014 00:27, Tim---Kracked_P_P---webmaster <
webmaster@krackedpress.com> wrote:
I use to "hand code" everything and then check my work in a browser.
Now
with more complex pages, it can be very hard to keep one edited without
using a WYSIWYG editor. Yes, I use text editors for some things, but
there
are a lot of things that need the editing while viewing the page, and
not
just the code.
On 11/14/2014 06:18 PM, Felmon Davis wrote:
On Fri, 14 Nov 2014, Tim---Kracked_P_P---webmaster wrote:
Yes, a text editor helps for some editing of an HTML file. Yet, for
some work I need a WYSIWYG editor for the look and feel of the web
document.
I use Kate [Ubuntu based Linux Mint] for the text editor. I use it
for
the Find/Replace option to change 91 links from [say] "4.3.3.2_" to
"4.3.4.1_". That takes too much time in a WYSIWYG editor, or at least
the
ones I have used.
Currently I use Kompozer, but when I upgrade from Mint 16 to 17 [14.04
based] and beyond, the graphical display methods do not like the
upgraded
version that Ubuntu 14.04/14.10 now uses. So I will be looking for a
different DEDICATED web page editor.
Yes, Writer can do the HTML editing, but I would prefer a WYSIWYG
editor
that was created specifically for web page editing and hopefully with
error
checking options.
I haven't followed the thread with great care so I may have
overlooked
a
reference to 'bluefish'. <http://bluefish.openoffice.nl/features.html>
I haven't used it in quite a spell so this isn't a 'recommendation',
just
a reference to a tool which might be of use.
it is not, I think, wysiwyg as such but it will open your browser for
inspection of results. (looking at the website it seems it may open
your
page within bluefish but I'm skimming too fast to be sure.)
see what you think.
(apologies if this has already been considered.)
F.
>
On 11/13/2014 07:29 AM, Virgil Arrington wrote:
On 11/13/2014 06:39 AM, Ian Whitfield wrote:
Hi Kolbjoern
Thanks for the reply.
The document already exists - so I'm selecting 'File Open', I change
the File Type to 'HTML Document (Writer)' and select my file. It
then
opens
in "view" mode - So how do I get to the code to edit it??
I just tried it again, and I think I see your problem. I did
exactly
as
you did, and the "HTML source" option did not appear on the View
menu.
I
think the problem is that, when opening the file, you are changing
the
File
Type to "HTML Document (Writer)." When you do that, all you get is a
WYSIWYG display along with no HTML source option. So, I tried it
again, but
instead of changing the file type to "HTML Document (Writer)" I kept
it at
"All types." Then when I opened an HTML file, I saw the source code
instead
of the WYSIWYG display.
Not sure if this is intended behavior or a bug.
(All this said, I agree with Tom that I would use a regular text
editor
to edit HTML code. Gedit works nicely on my Ubuntu machine.)
Virgil
On 11/13/2014 01:18 PM, Kolbjørn Stuestøl wrote:
When saving your document, select "HTML Document (Writer) (.html)"
in
the "File type:" drop down list in the Save dialog.
Kolbjoern
Den 13.11.2014 11:18, skreiv Ian Whitfield:
Hi All
Can I get some help on this please??
I have read about, and looked-up, the possibility of editing HTML
documents in Writer but can not get it to work!!
No matter what I do I can not fine 'HTML Mode' or 'View HTML' as
talked about ion the help files.
I can load my document but can not get at the HTML code.
What am I missing or doing wrong??
I'm using LO 4.3 on PClinuxOS (latest)
Thanks for any help.
IanW
Pretoria RSA
Privacy Policy |
Impressum (Legal Info) |
Copyright information: Unless otherwise specified, all text and images
on this website are licensed under the
Creative Commons Attribution-Share Alike 3.0 License.
This does not include the source code of LibreOffice, which is
licensed under the Mozilla Public License (
MPLv2).
"LibreOffice" and "The Document Foundation" are
registered trademarks of their corresponding registered owners or are
in actual use as trademarks in one or more countries. Their respective
logos and icons are also subject to international copyright laws. Use
thereof is explained in our
trademark policy.