It has been a few days since my last status update, so here is a new, quick one:
@Scrutiziner and @Neo continue to work on the migration and are getting closer. The migration script provided OOTB by Discourse (the various BBCODE converters) mangled a lot of text; and @Scrutinzer has been leading the effort to get the various bbcode conversions as error free as practical. So far, so good.
Today, after more discussions with @Scrutinzer, I modified a Discourse theme component and added four new editor / composer buttons:
This was my first Discourse theme component modification, and frankly speaking, it was really easy (orders of magnitude easier, and infinitely faster debugging, than Discourse plugin development and testing).
Frankly, we don't want to get too much into editor / composer button modifications until people use it more; so this will probably be the only changes to the composer before going live (sooner than later). We can look for better icons on FontAwesome and get input from the people who matter the most, all of you!
@Scruitizer informs that he is getting closer to have his new Ruby preprocessing script ready for testing against the database, and he says he has been having a lot of fun with Ruby as well!
Hi All,
We will be doing a Solaris 8 to Solaris 10 migration migration, just wanted to know if there are any known / common issues arise from this migration from Shell script point of view.
I tried searching this site but mostly post are related to SA's question and jumpstart, etc. If there's... (4 Replies)
All,
We are migrating an application from HP-UX B.11.00 to HP-UX B.11.31 and both of them have the same informix version - 7.25se. However the compilers are different on both servers.
HP-UX B.11.00 - has B3913DB C.03.33 HP aC++ Compiler (S800)
HP-UX B.11.31 - has PHSS_40631 1.0 HP C/aC++... (2 Replies)
Dear Team
I am using DB2 v10 z/os database . Need expert guidance to figure out best way to track table activities ( Ex Delete, Insert,Update )
Scenario
We have a table which is critical and many developer/testing team access on daily basis . We had instance where some deleted... (1 Reply)
First a bit of history ....
A number of years ago one of our admins built a number of plugin systems for moderation, including (1) a voting system, (2) a "user feelings" system and (3) a confidential posting system. During this time, I was busy on other projects, not very active in the forums,... (1 Reply)
OK.
Like we all do, we learn a lot from tests, test migrations, and so forth.
Today, I started from scratch on test migration 2, armed with a lot more knowledge,
The main differences are as follows:
Installed discourse plugin ruby-bbcode-to-md before starting the install
Modified... (30 Replies)
Test Build 4 on New Server, with changes identified in discourse test builds 2 and 3, primarily:
Insuring ruby-bbcode-to-markdown is enabled.
Removing line breaks from ICODE to markdown in migration script.
Added vbpostid to posts in discourse to setup migrating vb "thanks" to discourse... (28 Replies)
Discussion started by: Neo
28 Replies
LEARN ABOUT DEBIAN
theme
THEME(1) BSD General Commands Manual THEME(1)NAME
theme -- create a web page from a template file
SYNOPSIS
theme [-d root] [-E] [-f] [-o file] [-p pagename] [-t template] [-V] [textfile]
DESCRIPTION
The theme utility takes a markdown(7)-formatted textfile (or stdin if not specified,) compiles it, and combines it with a template
(page.theme by default) to produce a web page. If a path to the template is not specified, theme looks for page.theme in the current direc-
tory, then each parent directory up to the document root (set with -d or, if unset, the root directory of the system.) If page.theme is
found, theme copies it to the output, looking for <?theme action?> html tags and processing the embedded action as appropriate.
theme processes the following actions:
author Prints the author name(s) from the mkd_doc_author(3) function.
body Prints the formatted markdown(7) input file.
date Prints the date returned by mkd_doc_date(3) or, if none, the date the input file was last modified.
dir Prints the directory part of the pagename
include(file)
Prints the contents of file. Markdown(7) translation will NOT be done on this file.
source The filename part of the pagename.
style Print any stylesheets (see mkd-extensions(7)) found in the input file.
title Print the title returned by mkd_doc_title(3), or, if that does not exist, the source filename.
version Print the version of discount(7) that this copy of theme was compiled with.
If input is coming from a file and the output was not set with the -o option, writes the output to file-sans-text.html (if) file has a .text
suffix, that will be stripped off and replaced with .html; otherwise a .html will be appended to the end of the filename.)
The options are as follows:
-d root Set the document root to root
-E Normally theme will not expand <?theme body?> or <?theme toc?> in the <head> section, or <?theme style?> in the <body> section, but
the -E option overrides this and allows expansions everywhere.
-f Forcibly overwrite existing html files.
-o filename
Write the output to filename.
-p path Set the pagename to path.
-t filename
Use filename as the template file.
RETURN VALUES
The theme utility exits 0 on success, and >0 if an error occurs.
SEE ALSO markdown(1), markdown(3), markdown(7), mkd-extensions(7).
AUTHOR
David Parsons (orc@pell.chi.il.us)
MASTODON January 23, 2008 MASTODON
04-09-2020
