Sponsored Content
The Lounge What is on Your Mind? Update on vB3 Migration to Discourse - Issues and Status of BBCode Transformations Post 303045840 by Neo on Wednesday 15th of April 2020 02:04:42 AM
Old 04-15-2020
Update:

Long baking (staging server, discourse1) done after close to 15 hours:

Update on vB3 Migration to Discourse - Issues and Status of BBCode Transformations-screen-shot-2020-04-15-73504-amjpg


It is much improved, but @Scrutiziner, with his eagle eye for details, has plans for more refinements to make it even better; as there are still some chars "lost in migration" outside of the code tag fences.
These 3 Users Gave Thanks to Neo For This Post:
 

6 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

Shell Script migration issues

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)
Discussion started by: arvindcgi
4 Replies

2. HP-UX

Migration - Compiler Issues.

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)
Discussion started by: helper
2 Replies

3. Programming

How to track table status delete/update/insert status in DB2 V10 z/os?

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)
Discussion started by: Perlbaby
1 Replies

4. What is on Your Mind?

Status of Migration of Moderation Systems

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)
Discussion started by: Neo
1 Replies

5. What is on Your Mind?

VBulletin 3.8 to Discourse on Docker Migration Test Take Two

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)
Discussion started by: Neo
30 Replies

6. What is on Your Mind?

VBulletin 3.8 to Discourse on Docker Migration Test Take Four

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
Font::TTF::GDEF(3pm)					User Contributed Perl Documentation				      Font::TTF::GDEF(3pm)

NAME
Font::TTF::GDEF - Opentype GDEF table support DESCRIPTION
The GDEF table contains various global lists of information which are apparantly used in other places in an OpenType renderer. But precisely where is open to speculation... INSTANCE VARIABLES
There are 4 tables in the GDEF table, each with their own structure: GLYPH This is an Font::TTF::Coverage Class Definition table containing information as to what type each glyph is. ATTACH The attach table consists of a coverage table and then attachment points for each glyph in the coverage table: COVERAGE This is a coverage table POINTS This is an array of point elements. Each element is an array of curve points corresponding to the attachment points on that glyph. The order of the curve points in the array corresponds to the attachment point number specified in the MARKS coverage table (see below). LIG This contains the ligature caret positioning information for ligature glyphs COVERAGE A coverage table to say which glyphs are ligatures LIGS An array of elements for each ligature. Each element is an array of information for each caret position in the ligature (there being number of components - 1 of these, generally) FMT This is the format of the information and is important to provide the semantics for the value. This value must be set correctly before output VAL The value which has meaning according to FMT DEVICE For FMT = 3, a device table is also referenced which is stored here MARKS Due to confusion in the GDEF specification, this field is currently withdrawn until the confusion is resolved. That way, perhaps this stuff will work! This class definition table stores the mark attachment point numbers for each attachment mark, to indicate which attachment point the mark attaches to on its base glyph. METHODS
$t->read Reads the table into the data structure $t->out($fh) Writes out this table. perl v5.10.1 2009-01-29 Font::TTF::GDEF(3pm)
All times are GMT -4. The time now is 05:19 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy