1. Introduction
This document specifies a simple compressed file format for fonts, designed primarily for use on the Web and known as WOFF (Web Open Font Format). Despite this name, WOFF should be regarded as a container format or "wrapper" for font data in already-existing formats rather than an actual font format in its own right.
The WOFF format is a container for the table-based sfnt structure used in e.g. TrueType [TrueType], OpenType [OpenType] and Open Font Format [OFF] fonts, hereafter referred to as sfnt fonts. A WOFF file is simply a repackaged version of a sfnt font with optional compression of the font data tables. The WOFF file format also allows font metadata and private-use data to be included separately from the font data. WOFF encoding tools convert an input sfnt font into a WOFF formatted file, and user agents restore the sfnt font data for use with a Web document.
The structure and contents of decoded font data exactly match those of a well-formed input font file. Tools producing WOFF files may provide other font editing features such as glyph subsetting, validation or font feature additions but these are considered outside the scope of this format. Independent of these features, both tools and user agents are expected to assure that the validity of the underlying font data is preserved.
Notational Conventions
The all-uppercase key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119 [RFC-2119]. If these words occur in lower- or mixed case, they should be interpreted in accordance with their normal English meaning.
This document includes sections of text that are called out as "Notes" and set off from the main text of the specification. These notes are intended as informative explanations or clarifications, to serve as hints or guides to implementers and users, but are not part of the normative text.
2. General Requirements
The primary purpose of the WOFF format is to package fonts linked to Web documents by means of CSS @font-face rules. User agents supporting the WOFF file format for linked fonts must respect the requirements of the CSS3 Fonts specification ([CSS3-Fonts] Section 4.1: The @font-face rule). In particular, such linked fonts are only available to the documents that reference them; they MUST NOT be made available to other applications or documents on the user's system.
The WOFF format is intended for use with @font-face to provide fonts linked to specific Web documents. Therefore, WOFF files must not be treated as an installable font format in desktop operating systems or similar environments. The WOFF-packaged data will typically be decoded to sfnt format for use by existing font-rendering APIs that expect OpenType font data, but such decoded font must not be exposed to other documents or applications.
3. Overall File Structure
The structure of WOFF files is similar to the structure of sfnt fonts: a table directory containing lengths and offsets to individual font data tables, followed by the data tables themselves. The sfnt structure is described fully in the TrueType [TrueType], OpenType [OpenType] and Open Font Format [OFF] specifications.
The main body of the file consists of the same collection of font data tables as the input sfnt font, stored in the same order, except that each table MAY be compressed, and the sfnt table directory is replaced by the WOFF table directory.
The WOFF specification does not guarantee that the actual font data packaged in a valid WOFF container is in fact correct and usable. It requires only that the WOFF packaging structure—header, table directory, and compressed tables—conforms to this specification. The contained data must be used with just as much caution as font data delivered in "raw" form or via any other packaging method.
A complete WOFF file consists of several blocks: a 44-byte header, immediately followed (in this order) by a variable-size table directory, a variable number of font tables, an optional block of extended metadata, and an optional block of private data. Except for padding with a maximum of three null bytes in places where 4-byte alignment of a table length or block offset is specified, there MUST NOT be any extraneous data between the data blocks or font data tables indicated by the WOFF header and table directory, or beyond the last such block or table. If such extraneous data is present a conforming user agent MUST reject the file as invalid. The file MUST also be rejected as invalid if the offsets and lengths of any data blocks or font tables indicate overlapping byte ranges of the file, or ranges that would extend beyond the end of the file.
| WOFF File | |
|---|---|
| WOFFHeader | File header with basic font type and version, along with offsets to metadata and private data blocks. |
| TableDirectory | Directory of font tables, indicating the original size, compressed size and location of each table within the WOFF file. |
| FontTables | The font data tables from the input sfnt font, compressed to reduce bandwidth requirements. |
| ExtendedMetadata | An optional block of extended metadata, represented in XML format and compressed for storage in the WOFF file. |
| PrivateData | An optional block of private data for the font designer, foundry, or vendor to use. |
Data values stored in the WOFF Header and WOFF Table Directory sections are stored in big-endian format, just as values are within sfnt fonts. The following basic data types are used in the description:
| Data types | |
|---|---|
| UInt32 | 32-bit (4-byte) unsigned integer in big-endian format |
| UInt16 | 16-bit (2-byte) unsigned integer in big-endian format |
All sizes and offsets described in this document are assumed to be in bytes unless otherwise noted.
4. WOFF Header
The header includes an identifying signature and indicates the specific kind of font data included in the file (TrueType or CFF outline data); it also has a font version number, offsets to additional data chunks, and the number of entries in the table directory that immediately follows the header:
| WOFFHeader | ||
|---|---|---|
| UInt32 | signature | 0x774F4646 'wOFF' |
| UInt32 | flavor | The "sfnt version" of the input font. |
| UInt32 | length | Total size of the WOFF file. |
| UInt16 | numTables | Number of entries in directory of font tables. |
| UInt16 | reserved | Reserved; set to zero. |
| UInt32 | totalSfntSize | Total size needed for the uncompressed font data, including the sfnt header, directory, and font tables (including padding). |
| UInt16 | majorVersion | Major version of the WOFF file. |
| UInt16 | minorVersion | Minor version of the WOFF file. |
| UInt32 | metaOffset | Offset to metadata block, from beginning of WOFF file. |
| UInt32 | metaLength | Length of compressed metadata block. |
| UInt32 | metaOrigLength | Uncompressed size of metadata block. |
| UInt32 | privOffset | Offset to private data block, from beginning of WOFF file. |
| UInt32 | privLength | Length of private data block. |
The signature field in the WOFF header MUST contain the "magic number" 0x774F4646. If the field does not contain this value, user agents MUST reject the file as invalid.
The flavor field corresponds to the "sfnt version" field found at the beginning of an sfnt file, indicating the type of font data contained. Although only fonts of type 0x00010000 (the version number 1.0 as a 16.16 fixed-point value, indicating TrueType glyph data) and 0x4F54544F (the tag 'OTTO', indicating CFF glyph data) are widely supported at present, it is not an error in the WOFF file if the flavor field contains a different value, indicating a WOFF-packaged version of a different sfnt flavor. (The value 0x74727565 'true' has been used for some TrueType-flavored fonts on Mac OS, for example.) Whether client software will actually support other types of sfnt font data is outside the scope of the WOFF specification, which simply describes how the sfnt is repackaged for Web use.
The WOFF majorVersion and minorVersion fields specify the version number for a given WOFF file, which can be based on the version number of the input font but is not required to be. These fields have no effect on font loading or usage behavior in user agents.
The totalSfntSize field is the sum of the uncompressed font table sizes, each padded to a multiple of 4 bytes, plus the size of the sfnt header and table directory. Thus, this is the size of buffer needed to decode the complete WOFF-packaged font (but not metadata, which is not part of the input sfnt file) into a standard sfnt structure. This value MUST be a multiple of 4, because all font tables including the last are to be padded to a 4-byte boundary. If this value is incorrect, a conforming user agent MUST reject the file as invalid.
The sfnt header includes three fields (searchRange, entrySelector and rangeShift) that are designed to facilitate a binary search of the table directory. As the proper value for each of these fields can be computed directly from the number of font tables, they are not stored in the WOFF file. User agents that decode WOFF files back to an sfnt structure MUST therefore compute the correct values for these fields in the sfnt header, as described in the OpenType/OFF specification.[OFF]
The correct value for totalSfntSize may be computed as illustrated by the following pseudo-code:
totalSfntSize = 12 // size of sfnt header ("offset table" in the OpenType spec) totalSfntSize += 16 * numTables // size of table record (directory of font tables) for each table: totalSfntSize += (table.origLength + 3) & 0xFFFFFFFC // table size, padded
If either or both of the metadata or private blocks is not present, the relevant offset and length fields MUST be set to zero. If the metadata or private data offset and length fields indicate byte ranges that overlap other data blocks or tables, or extend beyond the end of the file, a conforming user agent MUST reject the file as invalid.
The header includes a reserved field; this MUST be set to zero. If this field is non-zero, a conforming user agent MUST reject the file as invalid.
5. Table Directory
The table directory is an array of WOFF table directory entries, as defined below. The directory follows immediately after the WOFF file header; therefore, there is no explicit offset in the header pointing to this block. Its size is calculated by multiplying the numTables value in the WOFF header times the size of a single WOFF table directory. Each table directory entry specifies the size and location of a single font data table.
| WOFF TableDirectoryEntry | ||
|---|---|---|
| UInt32 | tag | 4-byte sfnt table identifier. |
| UInt32 | offset | Offset to the data, from beginning of WOFF file. |
| UInt32 | compLength | Length of the compressed data, excluding padding. |
| UInt32 | origLength | Length of the uncompressed table, excluding padding. |
| UInt32 | origChecksum | Checksum of the uncompressed table. |
The format of tag values are defined by the specifications for sfnt fonts. The offset and compLength fields identify the location of the compressed font table. The origLength and origCheckSum fields are the length and checksum of the input font table from the table directory of the input font.
The sfnt format specifications require that font tables be aligned on 4-byte boundaries. Font tables whose length is not a multiple of 4 are padded with null bytes up to the next 4-byte boundary. Font data tables in the WOFF file have the same requirement: they MUST begin on 4-byte boundaries and be zero-padded to the next 4-byte boundary. The compLength and origLength fields in the table directory store the exact, unpadded length.
If the offset and compLength values indicate a byte range that overlaps other data blocks or font tables, or if the byte range extends beyond the end of the file, a conforming user agent MUST reject the file as invalid.
If the length of a compressed font table would be the same as or greater than the length of the input font table, the font table MUST be stored uncompressed in the WOFF file and the compLength set equal to the origLength. Tools MAY also opt to leave other tables uncompressed (e.g. all tables less than a certain size), in which case compLength will be equal to origLength for these tables as well. WOFF files containing table directory entries for which compLength is greater than origLength are considered invalid and MUST NOT be loaded by user agents. Files containing compressed font tables that decompress to a size other than origLength are also considered invalid and MUST NOT be loaded.
The sfnt font specifications require that table directory entries are sorted in ascending order of tag value. To simplify processing, WOFF-producing tools MUST produce a table directory with entries in ascending tag value order. User agents MUST likewise assure that the sfnt table directory is recreated in ascending tag order when restoring the font data to its uncompressed state. The ordering of the font tables themselves is independent of the order of directory entries, as described below.
sfnt fonts store a checksum for each table in the table directory, and an overall checksum for the entire font in the head table (see the TrueType, OpenType or Open Font Format specifications for the definition of each calculation). Tools producing WOFF files MUST validate these checksums, and reject the font if errors are found.
A WOFF file contains the same set of font tables as the input font from which it was created. This means that the overall font checksum of a font decompressed from a conformant WOFF file will always match the checksum in the well-formed input font. In the case where the input font included unreferenced data between or after the actual tables, this would affect the overall checksum of the input font, but would be dropped during creation of the WOFF file.
A well-formed input font does not have structural anomalies such as incorrect padding, overlapping font tables, extraneous data between tables (which will be discarded by the WOFF generator), or incorrect checksums.
To ensure that lossless round-trip conversion from sfnt to WOFF and back will be possible, a well-formed input font should conform to certain norms that are not strictly required by the OpenType/OFF specification, although they are common practice:
- Font table padding
- The OpenType/OFF specification is not entirely clear about whether all tables in an sfnt font must be padded with 0-3 zero bytes to a multiple of 4 bytes in length, or whether this applies only between tables, and the final table of the file may be left unpadded. Most current tools and fonts seem to expect all tables to be padded to a 4-byte boundary, including the last. The WOFF specification assumes this behavior, and specifies that the totalSfntLength field in the WOFF header provides for such padding. To ensure that a given font can be packaged as a WOFF file and then decoded to its original format and give a byte-for-byte identical result, the input font should therefore be padded to a multiple of 4 bytes in length.
- No "hidden" data
- The OpenType/OFF specification does not explicitly prohibit the presence of "extra" data or padding in between the font tables; as the table directory includes the offset and length of each actual table, such data would simply be ignored. However, the WOFF format makes no provision to preserve such non-font-table data when packaging a font, and therefore it would not survive a round-trip format conversion.
- Header fields are correct
- The OpenType/OFF header fields (searchRange, entrySelector, rangeShift) that are designed to facilitate a binary search of the table directory must be correct in the input sfnt file, as the WOFF format does not directly preserve these fields but assumes a WOFF decoder will recompute them as needed.
- Checksums are correct
- The WOFF specification says that table checksums must be validated (and corrected if necessary) by WOFF creators. In order for complete round-trip fidelity, therefore, the checksums in the input sfnt file must also be correct prior to WOFF packaging.
- No overlapping tables
- The offset and length values in the input sfnt table directory must not indicate overlapping byte ranges of the input font.
The result of creating a WOFF file and then decoding this to regenerate an sfnt font MUST result in a final font that is bitwise-identical to the well-formed input font.. If the input font has defects or anomalies that make this impossible, the WOFF-generating tool SHOULD either reject the font or issue an appropriate warning that lossless round-trip conversion will not be possible.
6. Font Data Tables
The font data tables in the WOFF file are exactly the same as the tables in the input font, except that each table MAY have been compressed. If compressed, it MUST have been compressed by the compress2() function of zlib [Compress2] (or an equivalent, compatible algorithm). User agents use the uncompress() function of zlib [Uncompress](or an equivalent, compatible algorithm) to decompress each table. The underlying format these functions use is described in the ZLIB specification [ZLib]. User agents or other programs that decode WOFF files MUST be able to handle tables that have been compressed. If the decompression function fails for any table, the WOFF file is invalid and MUST NOT be loaded.
The font data tables MUST be stored immediately following the table directory, without gaps except for any padding that is required (up to three null bytes at the end of each table) to ensure 4-byte alignment.
Font tables in WOFF files MUST be stored in the same order as the well-formed input font. The table order is implied by offset values in the table directory; sorting table directory entries into ascending offset value order produces a list of entries in an order equivalent to that of the font tables.
User agents need not necessarily reconstitute the input font as a whole, and may reorder tables when decoding the WOFF file to sfnt form; they may access individual tables directly as needed. Under these circumstances the resulting sfnt will no longer be an exact copy of the input font, and checksums or digital signature data may be invalidated as a result.
In some cases, sites deploying WOFF files as Web fonts may wish to subset the character repertoire, optimize table ordering for efficient text layout or rasterization, or remove (or add) optional font tables depending on the particular features needed for a site. User agents might make similar modifications to the font during decoding, such as omitting tables that are not needed by their particular text display system.
The automatic removal of OpenType features such as GPOS and GSUB information at any stage in the process of deploying a WOFF file is strongly discouraged. Many writing systems around the world rely on these features for very basic display of text in the script that they use.
If either a WOFF-creation tool or a WOFF-consuming user agent reorders or otherwise modifies the collection of font tables, the font checksum in the head table will need to be recalculated as it will be affected by the changed offsets in the sfnt table directory. Any DSIG table in the input font will also be invalidated by such changes, and should therefore be removed from the modified font. A new signature could be added to the modified font, as described by the OpenType and Open Font Format specifications (if appropriate signing credentials are available to the tool involved). Any such pre- and/or post-processing represents a modification of the font data being packaged; while it might be done in conjunction with WOFF packaging for Web deployment, it falls outside the scope of the WOFF specification.
The OpenType/OFF specification does not explicitly prohibit the presence of "extra" data or padding in between the font tables in the sfnt format; as the table directory includes the offset and length of each actual table, such data would simply be ignored. However, the WOFF format makes no provision to preserve such "hidden" non-font-table data when packaging a font, and therefore it would not survive a round-trip format conversion.
7. Extended Metadata Block
The WOFF file MAY include a block of extended metadata. This may be more extensive and more easily accesible than metadata present in sfnt tables. The metadata block consists of XML data compressed by zlib; the file header specifies both the size of the actual compressed and the original uncompressed size in order to facilitate memory allocation.
The presence (or absence) and content of the metadata block MUST NOT affect font loading or rendering behavior of user agents; it is intended to be purely informative. User agents MAY provide a means for users to view information about fonts (such as a "Font Information" panel). If such information is provided, then they MUST treat the metadata block as the primary source, and MAY fall back to presenting information from the font's name table entries when relevant extended metadata elements are not present.
If present, the metadata MUST be compressed; it is never stored in uncompressed form.
The metadata block MUST follow immediately after the last font table. As all font data tables are padded with up to three null bytes if needed to reach a 4-byte boundary, the beginning of the metadata block will always be 4-byte aligned. If the metadata block is the last block in the WOFF file, there SHOULD be no additional padding after the end of the block.
The extended metadata MUST be well-formed XML encoded in UTF-8.
The schema for the extended metadata XML is described below. If the extended metadata does not match this schema, it is invalid. It is also invalid if it cannot be decompressed by zlib's uncompress() function (or equivalent), or if the length of the decompressed data does not match the metaOrigLength value specified in the WOFF header. Thus, valid metadata is well formed, conforms to the schema below, and is stored in compressed form in the WOFF file. A conforming user agent MUST ignore an invalid metadata block, as if the block were not present.
This description is also available as a RelaxNG schema. In the event of a discrepancy between the RelaxNG schema and the text of the specification, the text takes precedence.
Several elements store their data in text child elements; this is to support localization. The text elements MAY be given a lang attribute in the XML namespace [XML]. For backwards compatibility, lang attributes in the default namepsace are also accepted in older content, and SHOULD be treated the same as xml:lang. New content SHOULD instead use xml:lang.
The syntax of values of the xml:lang attribute can be found in BCP47 [BCP47]. A user agent displaying metadata SHOULD choose a preferred language/locale to display from among those available, following BCP47.
The user agent SHOULD choose which of the available text elements to display as follows:
- If a text element is available that matches the user's preferred language, as determined via an explicit preference or implied by the current locale, use this language.
- If the user agent has a concept of a list of "acceptable" languages or defaults, try each of these in turn and use the first one for which a match found.
- If there is a text element with no xml:lang attribute, use this; in the event that more than one exists, use the first of them.
- If no match is found yet, use the first text element. (Thus, the metadata creator can determine the "localization of last resort" simply by choosing which language to put first in each group of text elements.)
Such localizable elements are indicated by the statement "This element may be localized using text child elements" in the description below; the internal structure of text elements with xml:lang attributes is not repeated for each element type. In each of these localizable elements, at least one text child element MUST be present, except in the case of the license element (as described below).
- metadata element
-
The main element. This element is REQUIRED.
attributes version A version number indicating the format version of the metadata element. This is currently 1.0. This attribute is REQUIRED. children uniqueid Zero or one child elements vendor Zero or one child elements credits Zero or one child elements description Zero or one child elements license Zero or one child elements copyright Zero or one child elements trademark Zero or one child elements licensee Zero or one child elements extension Zero or more child elements
All first-level child elements of the metadata are OPTIONAL, and may occur in any order as children of the top-level metadata element.
The extension element is intended to allow vendors to include metadata that is not covered by the specific elements defined here, while following a standard model. User agents that provide a means for the user to view WOFF file metadata SHOULD include such extension elements in the metadata presented to the user.
- uniqueid element
-
A unique identifier string for the font. This element is recommended, but not required for the metadata to be valid. This element MUST be a child of the metadata element. This is an empty element.
attributes id The identification string. This attribute is REQUIRED. The string defined in the uniqueid element is not guaranteed to be truly unique, as there is no central registry or authority to ensure this, but it is intended to allow vendors to reliably identify the exact version of a particular font. The use of "reverse-DNS" prefixes to provide a "namespace" is recommended; this can be augmented by additional identification data of the vendor's own design.
The id attribute of the uniqueid element, and of several further metadata elements defined below, is not required to conform to the rules for the XML type ID; its form is at the discretion of the font creator or vendor.
- vendor element
-
Information about the font vendor. This element is recommended, but not required for the metadata to be valid. This element MUST be a child of the metadata element. This is an empty element.
attributes name The name of the font vendor. This attribute is REQUIRED. url The url for the font vendor. This attribute is OPTIONAL. dir The text direction, either ltr (for "left to right") or rtl (for "right to left"). This attribute is OPTIONAL and, if omitted, defaults to ltr. class An arbitrary set of space-separated tokens. This attribute is OPTIONAL. - credits element
-
Credit information for the font. This can include any type of credit the vendor desires: designer, hinter, and so on. This element is OPTIONAL. If present, it MUST be a child of the metadata element and it MUST contain at least one credit element. This element has no attributes.
children credit One or more child elements - credit element
-
A single credit record. If present, it MUST be a child of the credits element. This is an empty element.
attributes name The name of the entity being credited. This attribute is REQUIRED. url The url for the entity being credited. This attribute is OPTIONAL. role The role of the entity being credited. This attribute is OPTIONAL. dir The text direction, either ltr (for "left to right") or rtl (for "right to left"). This attribute is OPTIONAL and, if omitted, defaults to ltr. class An arbitrary set of space-separated tokens. This attribute is OPTIONAL. - description element
-
An arbitrary text description of the font's design, its history, etc. This element is OPTIONAL. If present, it MUST be a child of the metadata element. This element may be localized using text child elements.
attributes url The url for more information about the font design, history, etc. This attribute is OPTIONAL. children text One or more child elements containing character data and optionally div and/or span children - license element
-
Licensing information for the font. This element is OPTIONAL. If present, it MUST be a child of the metadata element. This element may be localized using text child elements; however, it is permitted to be empty (for example, if the vendor prefers to just provide a license URL rather than including the actual text of the license.)
attributes url The url for the license, more information about the license, etc. This attribute is OPTIONAL. id An identifying string for the license. This attribute is OPTIONAL. children text Zero or more child elements containing character data and optionally div and/or span children - copyright element
-
The copyright for the font. This element is OPTIONAL. If present, it MUST be a child of the metadata element. This element may be localized using text child elements. This element has no attributes.
children text One or more child elements containing character data and optionally div and/or span children - trademark element
-
The trademark for the font. This element is OPTIONAL. If present, it MUST be a child of the metadata element. This element may be localized using text child elements. This element has no attributes.
children text One or more child elements containing character data and optionally div and/or span children - licensee element
-
The licensee of the font. This element is OPTIONAL. If present, it MUST be a child of the metadata element. This is an empty element.
attributes name The name of the licensee. This attribute is REQUIRED. dir The text direction, either ltr (for "left to right") or rtl (for "right to left"). This attribute is OPTIONAL and, if omitted, defaults to ltr. class An arbitrary set of space-separated tokens. This attribute is OPTIONAL.
Although the metadata elements and structure defined above are expected to be sufficient for most needs, an extension mechanism is also provided so that font vendors can include arbitrary metadata items that do not fit the standard elements above:
- extension element
-
A container element for extended metadata provided by the vendor. Zero or more extension elements may be present as children of the top-level metadata element. Each such metadata extension has an optional name, which may be provided in multiple languages, and one or more item elements.
attributes id An arbitrary identifier defined by the vendor. This attribute is OPTIONAL. children name Zero or more child elements item One or more child elements - item element
-
At least one item element MUST be present in each extension container.
attributes id An arbitrary identifier defined by the vendor. This attribute is OPTIONAL. children name One or more child elements value One or more child elements - name element
-
Zero or more name elements may be used to provide a human-friendly name for the collection of extended metadata items in an extension element. A user agent that displays metadata SHOULD choose the name with most the appropriate language from among those available for each named extension element. This child element is OPTIONAL in extension elements; anonymous extension elements are also permissible.
One or more name elements are also used to provide a human-friendly name for a specific extended metadata item. A user agent that displays metadata SHOULD choose the name with the most appropriate language from among those available for each item element. This child element is REQUIRED in item elements; an item element with no name is invalid and SHOULD be ignored.
attributes xml:lang A language tag as defined in BCP47 [BCP47]. This attribute is OPTIONAL. dir The text direction, either ltr (for "left to right") or rtl (for "right to left"). This attribute is OPTIONAL and, if omitted, defaults to ltr. class An arbitrary set of space-separated tokens. This attribute is OPTIONAL. - value element
One or more value elements are used to provide the value of a specific extended metadata item. A user agent that displays metadata SHOULD choose the value with the most appropriate language from among those available for each item element. This child element is REQUIRED; an item element with no value is invalid and SHOULD be ignored.
attributes xml:lang A language tag as defined in BCP47 [BCP47]. This attribute is OPTIONAL. dir The text direction, either ltr (for "left to right") or rtl (for "right to left"). This attribute is OPTIONAL and, if omitted, defaults to ltr. class An arbitrary set of space-separated tokens. This attribute is OPTIONAL.
Where text elements are used to contain (localizable) content, further structure MAY also be provided using div and span child elements similar to those used in HTML.
- text element
-
An element used to contain a particular localization of a metadata element's contents. This element has a mixed content model; in addition to the child elements mentioned below, it may directly contain character data.
attributes xml:lang A language tag (as specified in BCP47 [BCP47]) indicating the language of this particular version of the metadata element's content. This attribute is OPTIONAL; however, for multiple text children of a metadata element to be usefully distinguished, they SHOULD all be tagged with appropriate different language codes. dir The text direction, either ltr (for "left to right") or rtl (for "right to left"). This attribute is OPTIONAL and, if omitted, defaults to ltr. class An arbitrary set of space-separated tokens. This attribute is OPTIONAL. children div Contains a block of text, such as a paragraph or heading. span Contains an inline run of text.
- div element
-
A block-level element used, for example, to contain a paragraph.
attributes dir The text direction, either ltr (for "left to right") or rtl (for "right to left"). This attribute is OPTIONAL and, if omitted, defaults to ltr. class An arbitrary set of space-separated tokens. This attribute is OPTIONAL. - span element
-
An inline element used, for example, to indicate a run of text with a different text direction, or in a different language.
attributes dir The text direction, either ltr (for "left to right") or rtl (for "right to left"). This attribute is OPTIONAL and, if omitted, defaults to ltr. class An arbitrary set of space-separated tokens. This attribute is OPTIONAL.
The text elements used to hold (localizable) text for a number of the individual pieces of metadata thus have a mixed content model consisting of text content, div and span elements; div elements have a mixed content model of text content, div and span elements; and span elements have a mixed content model of text content and span elements. In other words, div can contain other div elements; span can contain other span elements; span does not require a containing div.
Appendix A includes several examples of the content of the metadata block.
Although the metadata block is optional, and there is no requirement for user agents to process it in order to render the font, clients such as Web browsers are encouraged to provide a means (such as a "Font Information" dialog for the current page) for users to view the metadata included in WOFF files. Not every client will necessarily have an appropriate context for this, but any client that enables the user to find out about the resources used by a Web document should consider exposing information about the fonts used, and in the case of WOFF-packaged fonts, the metadata block is the primary source of this information.
8. Private Data Block
The WOFF file MAY include a block of arbitrary data, allowing font creators to include whatever information they wish. The content of this data MUST NOT affect font usage or load behavior of user agents. User agents should make no assumptions about the content of a private block; it may (for example) contain ASCII or Unicode text, or some vendor-defined binary data, and it may be compressed or encrypted, but it has no publicly defined format. Conformant user agents will not assume anything about the structure of this data. Only the font developer or vendor responsible for the private block is expected to understand its contents.
The private data block, if present, MUST be the last block in the WOFF file, following all the font tables and any extended metadata block. The private data block MUST begin on a 4-byte boundary in the WOFF file, with up to three null bytes inserted as padding after any preceding metadata block if needed to ensure this. The end of the private data block MUST correspond to the end of the WOFF file.
Appendix A: Extended Metadata Examples
This appendix is purely informative, not a normative part of the WOFF specification.
This "dummy" metadata block illustrates the use of the metadata elements described in section 7, including the use of multiple text child elements to provide localized versions of certain elements.
A real-life example of a simple metadata block (reproduced by permission of FSI FontShop International GmbH).
Another example of a metadata block (reproduced by permission of Ascender Corporation). This is dynamically generated, with the uniqueid and licensee elements modified to be unique for each customer.
Here is an example of how the div element could be used, modified from a portion of the XML file for Gentium Plus which, when viewed as plain text, has paragraph formatting.
The original metadata file contained:
Using the div element, this could become:
Appendix B: Media Type registration
This appendix registers a new MIME media type, in conformance with BCP 13 and W3CRegMedia.
- Type name:
-
application
- Subtype name:
-
font-woff
- Required parameters:
-
None.
- Optional parameters:
-
None.
- Encoding considerations:
-
binary.
- Security considerations:
-
Fonts are interpreted data structures that represent collections of glyph outlines, metrics and layout information for various languages and writing systems. Currently, there are many standardized font data tables that allow an unspecified number of entries, and where existing, predefined data fields allow storage of binary data with variable length. There is a significant risk that the flexibility of font data structures may be exploited to hide malicious binary content disguised as a font data component.
WOFF is based on the table-based SFNT (scalable font) format which is highly extensible and offers an opportunity to introduce additional data structures when needed. However, this same extensibility may present specific security concerns – the flexibility and ease of defining new data structures makes it easy for any arbitrary data to be added and hidden inside a font file.
WOFF fonts may contain 'hints' for the alignment of graphical elements of the glyphs with the target display pixel grid, and depending on the font technology utilized in the creation of a font these hints may represent active code interpreted and executed by the font rasterizer. Even though they operate within the confines of the glyph outline conversion system and have no access outside the font rendering machinery, hint instructions can be, however, quite complex, and a maliciously designed complex font could cause undue resource consumption (e.g. memory or CPU cycles) on a machine interpreting it. Indeed, fonts are sufficiently complex that most if not all interpreters cannot be completely protected from malicious fonts without undue performance penalties.
Widespread use of fonts as necessary component of visual content presentation warrants that a careful attention should be given to security considerations whenever a font is either embedded into an electronic document or transmitted alongside media content as a linked resource.
WOFF uses gzip compression. The WOFF header contains the uncompressed length of each compressed table. Applications may therefore constrain the size of memory buffer allocated for decompression and may stop writing if a maliciously crafted WOFF file in fact contains more data than is indicated.
WOFF does not provide privacy protections internally; if needed, these should be provided externally.
WOFF has a private data block facility, which may contain arbitrary binary data. WOFF does not provide a means to access this, or to execute any code contained therein. WOFF requires that the content of this block not affect font rendering in any way.
- Interoperability considerations:
- Published specification:
This media type registration is extracted from the WOFF specification at W3C.
- Applications that use this media type:
WOFF is used by Web browsers, often in conjunction with HTML and CSS.
- Additional information:
- Magic number(s):
- The signature field in the WOFF header MUST contain the "magic number" 0x774F4646
- File extension(s):
- woff
- Macintosh file type code(s):
- (no code specified)
- Macintosh Universal Type Identifier code:
- org.w3c.woff
- Fragment Identifiers
- none.
- Person & email address to contact for further information:
-
Chris Lilley (www-font@w3.org).
- Intended usage:
-
COMMON
- Restrictions on usage:
-
None
- Author:
-
The WOFF specification is a work product of the World Wide Web Consortium's WebFonts Working Group.
- Change controller:
-
The W3C has change control over this specification.
Appendix C: Changes
The following changes have been made, relative to the 27 July 2010 First Public Working Draft. No new features have been added, except for optional enhancements to the metadata format; the remaining changes are clarifications and corrections to existing features.
- Clarified that WOFF is a font packaging or wrapper format, not a new font format as such.
- Clarified padding and byte-alignment requirements throughout
- Preferred the term 'input font' rather than 'original file' to describe the font which is converted to WOFF
- Clarified that any subsetting, checksum-correction, or DSIG invalidating changes prior to WOFF conversion are out of scope for the WOFF specification.
- Clarified meaning of totalSfntSize.
- Defined what is meant by a well formed input font.
- Clarified meaning of 'invalid metadata' - must be well-formed, compressed, and conform to the schema.
- Clarified which elements and attributes in the XML are required; for elements, clarified their required parents.
- Clarified that the id attribute is not of type ID in the XML sense
- Added link to a RelaxNG grammar, which tries to express the same constraints as the prose in a machine-readable manner. The prose is normative in case of any difference.
- Added reminder to check for overflow when decompressing.
- Added a Media Type registration template as required by W3C Media Type registration policies.
- Separated normative and informative references.
- Switched to upper-case for RFC-2119 keywords.
- Added id and class attributes to all testable assertions.
- Added some non-normative explanatory notes.
- Minor clarifications to wording throughout.
- Some re-ordering of text to group related assertions or to improve readability; in particular, the best practices were previously an appendix and are now integrated into the main body of the specification.
- Added this Changes appendix.
The following changes were made as a result of Last Call:
- Language attributes now reference BCP47, and use xml:lang.
- Added optional div and span elements that can be used to provide structure within metadata text.
- Added dir and class attributes to metadata elements.
- Removed summary of conformance requirements (duplicated material from the main body of the specification).
- Somewhat rearranged and clarified description of the metadata format.
- Noted that same-origin requirements are at risk, in the expectation that CSS3 Fonts will handle this instead.
- Mention the need to compute the binary search fields when reconstructing an sfnt header.
- Require that metadata be encoded in UTF-8, rather than allowing either UTF-8 or UTF-16.
A color-coded diff between the editors draft used to prepare the Last Call Working Draft, and the editors draft used to prepare the Candidate Recommendation, is available.
The following changes were made after publication of the Candidate Recommendation:
- Removed (previously at-risk) text specifying same-origin requirements for loading WOFF fonts, and CORS mechanism to relax the restriction, as the CSS WG agreed to include this in CSS3 Fonts as part of the specification of the @font-face rule.
- Moved CSS3-Fonts from normative to informative section, due to removal of at-risk items.
- Corrected erroneous use of MUST in a general introductory statement
A color-coded diff between the editors draft used to prepare the Candidate Recommendation, and the editors draft used to prepare the Proposed Recommendation, is available.
The following changes were made after publication of the Proposed Recommendation:
- The security considerations section of the Media Type Registration appendix was updated to point into the body of the specification, alerting the reader to the private data block and indicating that WOFF does not provide a mechanism to execute any binary code that might be contained therein. This change was made at the request of the IANA Expert Reviewer.
References
Normative References
- [BCP47]
- BCP 47 Tags for Identifying Languages and Matching of Language Tags
- [OFF]
- Open Font Format specification (ISO/IEC 14496-22:2009).
- [RFC-2119]
- RFC 2119: Key words for use in RFCs to Indicate Requirement Levels. S. Bradner, Editor. Internet Engineering Task Force, March 1997.
- [ZLIB]
- RFC 1950 ZLIB Compressed Data Format Specification. P. Deutsch, J-L. Gailly, Editors. Internet Engineeering Task Force, May 1996.
Informative References
- [Compress2]
- zlib compress2() function
- [CSS3-Fonts]
- CSS Fonts Module Level 3. J. Daggett, Editor. World Wide Web Consortium, 4 October 2011. The latest version of CSS3 Fonts is available at http://www.w3.org/TR/css3-fonts/. (Work in Progress).
- [OpenType]
- Microsoft OpenType specification, version 1.6. Microsoft, 2009. OpenType is a registered trademark of Microsoft Corporation.
- [TrueType]
- Apple TrueType Reference manual. Apple, 2002. TrueType is a registered trademark of Apple Computer, Inc.
- [Uncompress]
- zlib uncompress() function
- [XML]
- Extensible Markup Language


BANJITZU
Username
Password
Email
Register
Username
Password
Login
Hello {{ currentUser.attributes.username }}
Logout
Sequences
{{ sequence.attributes.name }}
{{ currentSequence.name }}
Start
Stop
Save As New
Draw
Doh!


Raiden is a technology that leverages off-chain state networks to extend Ethereum with some nice properties for asset transfers:
It scales linearly with the number of participants (1,000,000+ transfers per second possible)
Transfers are confirmed and final within the fraction of a second
Single transfers don’t show up in the global shared ledger
Works with any token that follows Ethereum’s standardized token API.
Transaction fees can be 7 orders of magnitude lower than on the blockchain
Low transaction fees allow to efficiently transfer tiny values.
Click here to visit the Raiden Network documentation.


I HAVE, alas! Philosophy,
Medicine, Jurisprudence too,
And to my cost Theology,
With ardent labour, studied through.

Magister, doctor styled, indeed,
Already these ten years I lead,
Up, down, across, and to and fro,
My pupils by the nose,—and learn,
That we in truth can nothing know!
That in my heart like fire doth burn.
’Tis true I’ve more cunning than all your dull tribe,
Magister and doctor, priest, parson, and scribe;
Scruple or doubt comes not to enthrall me,
Neither can devil nor hell now appal me—
Hence also my heart must all pleasure forego!
I may not pretend, aught rightly to know,
I may not pretend, through teaching, to find
A means to improve or convert mankind.
Then I have neither goods nor treasure,
No worldly honour, rank, or pleasure;
No dog in such fashion would longer live!
Therefore myself to magic I give,
In hope, through spirit-voice and might,
Secrets now veiled to bring to light,
That I no more, with aching brow,
Need speak of what I nothing know;
That I the force may recognise
That binds creation’s inmost energies;
Her vital powers, her embryo seeds survey,
And fling the trade in empty words away.
O full-orb’d moon, did but thy rays
Their last upon mine anguish gaze!
Beside this desk, at dead of night,
Oft have I watched to hail thy light:
Then, pensive friend! o’er book and scroll,
With soothing power, thy radiance stole!
In thy dear light, ah, might I climb,
Freely, some mountain height sublime,
Round mountain caves with spirits ride,
In thy mild haze o’er meadows glide,
And, purged from knowledge-fumes, renew
My spirit, in thy healing dew!
Woe’s me! still prison’d in the gloom
Of this abhorr’d and musty room!
Where heaven’s dear light itself doth pass,
But dimly through the painted glass!
Hemmed in by volumes thick with dust,
Worm-eaten, hid ’neath rust and mould,
And to the high vault’s topmost bound,
A smoke-stained paper compassed round;
With boxes round thee piled, and glass,
And many a useless instrument,
With old ancestral lumber blent—
This is thy world! a world! alas!
And dost thou ask why heaves thy heart,
With tighten’d pressure in thy breast?
Why the dull ache will not depart,
By which thy life-pulse is oppress’d?
Instead of nature’s living sphere,
Created for mankind of old,
Brute skeletons surround thee here,
And dead men’s bones in smoke and mould.
Up! Forth into the distant land!
Is not this book of mystery
By Nostradamus’ proper hand,
An all-sufficient guide? Thou’lt see
The courses of the stars unroll’d;
When nature doth her thoughts unfold
To thee, thy soul shall rise, and seek
Communion high with her to hold,
As spirit doth with spirit speak!
Vain by dull poring to divine
The meaning of each hallow’d sign.
Spirits! I feel you hov’ring near;
Make answer, if my voice ye hear!
Ah! at this spectacle through every sense,
What sudden ecstasy of joy is flowing!
I feel new rapture, hallow’d and intense,
Through every nerve and vein with ardour glowing.
Was it a god who character’d this scroll,
The tumult in my spirit healing,
O’er my sad heart with rapture stealing,
And by a mystic impulse, to my soul,
The powers of nature all around revealing.
Am I a God? What light intense!
In these pure symbols do I see,
Nature exert her vital energy.
Now of the wise man’s words I learn the sense;
“Unlock’d the spirit-world doth lie,How all things live and work, and ever blending,
Thy sense is shut, thy heart is dead!
Up scholar, lave, with courage high,
Thine earthly breast in the morning-red!” (He contemplates the sign.)
A wondrous show! but ah! a show alone!
Where shall I grasp thee, infinite nature, where?
Ye breasts, ye fountains of all life, whereon
Hang heaven and earth, from which the withered heart
For solace yearns, ye still impart
Your sweet and fostering tides—where are ye—where?
Ye gush, and must I languish in despair? (He turns over the leaves of the book impatiently, and perceives the sigh of the Earth-spirit.)
How all unlike the influence of this sign!
Earth-spirit, thou to me art nigher,
E’en now my strength is rising higher,
E’en now I glow as with new wine;
Courage I feel, abroad the world to dare,
The woe of earth, the bliss of earth to bear,
With storms to wrestle, brave the lightning’s glare,
And mid the crashing shipwreck not despair.
Clouds gather over me—
The moon conceals her light—
The lamp is quench’d—
Vapours are rising—Quiv’ring round my head
Flash the red beams—Down from the vaulted roof
A shuddering horror floats,
And seizes me!
I feel it, spirit, prayer-compell’d, ’tis thou
Art hovering near!
Unveil thyself!
Ha! How my heart is riven now!
Each sense, with eager palpitation,
Is strain’d to catch some new sensation!
I feel my heart surrender’d unto thee!
Thou must! Thou must! Though life should be the fee! (He seizes the book, and pronounces mysteriously the sign of the spirit. A ruddy flame flashes up; the spirit appears in the flame.)
Who calls me?
Dreadful shape!
 I cannot bear thy sight!
To see me thou dost breathe thine invocation,
My voice to hear, to gaze upon my brow;
Me doth thy strong entreaty bow—
Lo! I am here!—What cowering agitation
Grasps thee, the demigod! Where’s now the soul’s deep cry?
Where is the breast, which in its depths a world conceiv’d
And bore and cherished? which, with ecstacy,
To rank itself with us, the spirits, heaved?
Where art thou, Faust? whose voice I heard resound,
Who towards me press’d with energy profound?
Art thou he? Thou,—who by my breath art blighted,
Who, in his spirit’s depths affrighted,
Trembles, a crush’d and writhing worm!
Shall I yield, thing of flame, to thee?
Faust, and thine equal, I am he!
In the currents of life, in action’s storm,
I float and I waveThus time’s whirring loom unceasing I ply,
With billowy motion!
Birth and the grave
A limitless ocean,
A constant weaving
With change still rife,
A restless heaving,
A glowing life—
Thou, restless spirit, dost from end to end
O’ersweep the world; how near I feel to thee!
Thou’rt like the spirit, thou dost comprehend,
Not me! (Vanishes.)
Not thee?
Whom then?
I, Gods own image!
And not rank with thee! (A knock.)
Oh death! I know it—’tis my famulus—
My fairest fortune now escapes!
That all these visionary shapes
A soulless groveller should banish thus! (WAGNER in his dressing gown and night-cap, a lamp in his hand. FAUST turns round reluctantly.)
Pardon!
Improvement in this art is now my aim,
For now-a-days it much avails. Indeed
An actor, oft I’ve heard it said, as teacher,
May give instruction to a preacher.
Ay, if your priest should be an actor too,
As not improbably may come to pass.
When in his study pent the whole year through,
Man views the world, as through an optic glass,
On a chance holiday, and scarcely then,
How by persuasion can he govern men?
If feeling prompt not, if it doth not flow
Fresh from the spirit’s depths, with strong control
Swaying to rapture every listener’s soul,
Idle your toil; the chase you may forego!
Brood o’er your task! Together glue,
Cook from another’s feast your own ragout,
Still prosecute your paltry game,
And fan your ash-heaps into flame!
Thus children’s wonder you’ll excite,
And apes’, if such your appetite;
But that which issues from the heart alone,
Will bend the hearts of others to your own.
The speaker in delivery will find
Success alone; I still am far behind.
A worthy object still pursue!
Be not a hollow tinkling fool!
Sound understanding, judgment true,
Find utterance without art or rule;
And when in earnest you are moved to speak,
Then is it needful cunning words to seek?
Your fine harangues, so polish’d in their kind,
Wherein the shreds of human thought ye twist,
Are unrefreshing as the empty wind,
Whistling through wither’d leaves and autumn mist!
Oh God! How long is art,
Our life how short! With earnest zeal
Still as I ply the critic’s task, I feel
A strange oppression both of head and heart.
The very means how hardly are they won,
By which we to the fountains rise!
And haply, ere one half the course is run,
Check’d in his progress, the poor devil dies.
Parchment, is that the sacred fount whence roll
Waters, he thirsteth not who once hath quaffed?
Oh, if it gush not from thine inmost soul,
Thou has not won the life-restoring draught.
Your pardon! ’tis delightful to transport
Oneself into the spirit of the past,
To see in times before us how a wise man thought,
And what a glorious height we have achieved at last.
Ay truly! even to the loftiest star!
To us, my friend, the ages that are pass’d
A book with seven seals, close-fasten’d, are;
And what the spirit of the times men call,
Is merely their own spirit after all,
Wherein, distorted oft, the times are glass’d.
Then truly, ’tis a sight to grieve the soul!
At the first glance we fly it in dismay;
A very lumber-room, a rubbish-hole;
At best a sort of mock-heroic play,
With saws pragmatical, and maxims sage,
To suit the puppets and their mimic stage.
But then the world and man, his heart and brain!
Touching these things all men would something know.
Ay! what ’mong men as knowledge doth obtain!
Who on the child its true name dares bestow?
The few who somewhat of these things have known,
Who their full hearts unguardedly reveal’d,
Nor thoughts, nor feelings, from the mob conceal’d,
Have died on crosses, or in flames been thrown.—
Excuse me, friend, far now the night is spent,
For this time we must say adieu.
Still to watch on I had been well content,
Thus to converse so learnedly with you.
But as to-morrow will be Easter-day,
Some further questions grant, I pray;
With diligence to study still I fondly cling;
Already I know much, but would know everything. (Exit.)
How him alone all hope abandons never,
To empty trash who clings, with zeal untired,
With greed for treasure gropes, and, joy-inspir’d,
Exults if earth-worms second his endeavour.
And dare a voice of merely human birth,
E’en here, where shapes immortal throng’d intrude?
Yet ah! thou poorest of the sons of earth,
For once, I e’en to thee feel gratitude.
Despair the power of sense did well-nigh blast,
And thou didst save me ere I sank dismay’d,
So giant-like the vision seem’d, so vast,
I felt myself shrink dwarf’d as I survey’d!
I, God’s own image, from this toil of clay
Already freed, with eager joy who hail’d
The mirror of eternal truth unveil’d,
Mid light effulgent and celestial day:—
I, more than cherub, whose unfetter’d soul
With penetrative glance aspir’d to flow
Through nature’s veins, and, still creating, know
The life of gods,—how am I punish’d now!
One thunder-word hath hurl’d me from the goal!
Spirit! I dare not lift me to thy sphere.
What though my power compell’d thee to appear,
My art was powerless to detain thee here.
In that great moment, rapture-fraught,
I felt myself so small, so great;
Fiercely didst thrust me from the realm of thought
Back on humanity’s uncertain fate!
Who’ll teach me now? What ought I to forego?
Ought I that impulse to obey?
Alas! our every deed, as well as every woe,
Impedes the tenor of life’s onward way!
E’en to the noblest by the soul conceiv’d,
Some feelings cling of baser quality;
And when the goods of this world are achiev’d,
Each nobler aim is termed a cheat, a lie.
Our aspirations, our soul’s genuine life,
Grow torpid in the din of earthly strife.
Though youthful phantasy, while hope inspires,
Stretch o’er the infinite her wing sublime,
A narrow compass limits her desires,
When wreck’d our fortunes in the gulf of time.
In the deep heart of man care builds her nest,
O’er secret woes she broodeth there,
Sleepless she rocks herself and scareth joy and rest;
Still is she wont some new disguise to wear,
She may as house and court, as wife and child appear,
As dagger, poison, fire and flood;
Imagined evils chill thy blood,
And what thou ne’er shall lose, o’er that dost shed the tear.
I am not like the gods! Feel it I must;
I’m like the earth-worm, writhing in the dust,
Which, as on dust it feeds, its native fare,
Crushed ’neath the passer’s tread, lies buried there.
Is it not dust, wherewith this lofty wall,
With hundred shelves, confines me round;
Rubbish, in thousand shapes, may I not call
What in this moth-world doth my being bound?
Here, what doth fail me, shall I find?
Read in a thousand tomes that, everywhere,
Self-torture is the lot of human-kind,
With but one mortal happy, here and there?
Thou hollow skull, that grin, what should it say,
But that thy brain, like mine, of old perplexed,
Still yearning for the truth, hath sought the light of day.
And in the twilight wandered, sorely vexed?
Ye instruments, forsooth, ye mock at me,—
With wheel, and cog, and ring, and cylinder;
To nature’s portals ye should be the key;
Cunning your wards, and yet the bolts ye fail to stir.
Inscrutable in broadest light,
To be unveil’d by force she doth refuse,
What she reveals not to thy mental sight,
Thou wilt not wrest me from her with levers and with screws.

Old scroll, the smoke of years dost wear,
So long as o’er this desk the sorry lamp hath shone.

Wouldst thou possess thy heritage, essay,
By use to render it thine own!
What we employ not, but impedes our way,
That which the hour creates, that can it use alone!
But wherefore to yon spot is riveted my gaze?
Is yonder flasket there a magnet to my sight?
Whence this mild radiance that around me plays,
As when, ’mid forest gloom, reigneth the moon’s soft light?
Hail precious phial! Thee, with reverent awe,
Down from thine old receptacle I draw!
Science in thee I hail and human art.
Essence of deadliest powers, refin’d and sure,
Of soothing anodynes abstraction pure,
Now in thy master’s need thy grace impart!
I gaze on thee, my pain is lull’d to rest;
I grasp thee, calm’d the tumult in my breast;
The flood-tide of my spirit ebbs away;
Onward I’m summon’d o’er a boundless main,
Calm at my feet expands the glassy plain,
To shores unknown allures a brighter day.
Lo, where a car of fire, on airy pinion,
Comes floating towards me! I’m prepar’d to fly
By a new track through ether’s wide dominion,
To distant spheres of pure activity.
This life intense, this godlike ecstasy—
Worm that thou art such rapture canst thou earn?
Only resolve with courage stern and high,
Thy visage from the radiant sun to turn!
Dare with determin’d will to burst the portals
Past which in terror others fain would steal!
Now is the time, through deeds, to show that mortals
The calm sublimity of gods can feel;
To shudder not at yonder dark abyss,
Where phantasy creates her own self-torturing brood,
Right onward to the yawning gulf to press,
Around whose narrow jaws rolleth hell’s fiery flood;
With glad resolve to take the fatal leap,
Though danger threaten thee, to sink in endless sleep!
Pure crystal goblet! forth I draw thee now,
From out thine antiquated case, where thou
Forgotten hast reposed for many a year!
Oft at my father’s revels thou didst shine,
To glad the earnest guests was thine,
As each to other passed the generous cheer.
The gorgeous brede of figures, quaintly wrought,
Which he who quaff’d must first in rhyme expound,
Then drain the goblet at one draught profound,
Hath nights of boyhood to fond memory brought.
I to my neighbour shall not reach thee now,
Nor on thy rich device shall I my cunning show.
Here is a juice, makes drunk without delay;
Its dark brown flood thy crystal round doth fill;
Let this last draught, the product of my skill,
My own free choice, be quaff’d with resolute will,
A solemn festive greeting, to the coming day!


This was an academic exercise because I wanted to play with a trie structure. It uses a list of known words to solve the puzzle, currently this uses a limited dictionary but can be changed to use all the words in the Princeton University's WordNet dictionary. Understandably searching through the whole dictionary takes a little longer, and since the algorithm is only returning the first result it may not return a solution that the WordBrain game accepts. If you want to try it against the whole dictionary, clone the repo and run 'node lib/makedict' to replace the dictionary with the wordnet one.
PS: It's not pretty, but it does get the job done :)


SchemaOrg Style
Generate documentation based on SchemaOrg tool.
Widoco Style
Generate documentation based on Widoco tool.
WebHook info
Uncheck this option only if previous domain name is same as current given domain name.
Home
General Info
Vocabulary Name:
Domain name:
Web Hook
Repository info
Repository:
Branch Name:
User:
Password:
Syntax Validation
Rapper
Jena Riot
Documentation Generation
SchemaOrg
Widoco
Additional Services
Visualization
Sparql EndPoint
Syntax Validation Report
Schema Evolution Report
Other Branches
Client Side Hooks
Turtle Editor
Use Predefined Queries
Serializations Format
RdfXML
NTriples
Homepage Description


| One or Many | collector | Only One | Standard Heading Set |
| Only One | collector | One or Many | Standard Heading |
| Zero, One or Many | responsible for devising | Only One | Agent |
| Only One | actual user | Zero, One or Many | Resource For Started Activity |
| Zero, One or Many | start location for | Only One | Location |
| Zero, One or Many | start location for | Zero or One | Location |
| Zero, One or Many | completion timepoint | Only One | Timepoint |
| Zero, One or Many | responsible for performance of | Only One | Agent |
| Zero, One or Many | activity state type from | Zero or One | Activity State Type |
| Zero, One or Many | activity state type to | Only One | Activity State Type |


'Long way' - Here's how Ahmed Hegazi played on his West Brom comeback
Jaquob Crooke reports on the Egyptian defender's first start of the season in Albion's win over Sheffield Wednesday
by Jaquob CrookeWest Bromwich Albion’s 2-1 victory over Sheffield Wednesday seen Ahmed Hegazi make his much-anticipated return to the starting eleven.
Albion’s accomplishments this season are made all the greater when you consider they have been without their stalwart defender, and it had been hoped that the return of Hegazi would help to aid Slaven Bilic’s side pursuit of clean sheets.
However, it was evident that there is still a long way to go before the Egyptian’s back at his resilient best, with the defender looking fairly rusty upon his return to first-team action.
And Hegazi didn’t exactly make a composed start to proceedings.
His centre-back partner Kyle Bartley presented a difficult situation for Hegazi to contend with as he allowed a high ball to go over his head to where Hegazi was positioned, but the Egyptian was flat footed in his approach and poor judgement enabled Jacob Murphy to nick the ball off him.
Hegazi was fortunate that Murphy’s pull-back was overhit as Steven Fletcher stretched out a leg at the back post, but the Baggies were able to recover and Hegazi’s blushes were spared.
As the game progressed Hegazi soon settled, providing a composed outlet in possession for West Brom when playing out from the back.
West Brom latest
This is your round up of all things West Brom; the one-stop shop that will keep you updated on the latest goings on at the club and beyond.
Transfers, injuries, match-days and managers, we’ve got you covered.
We’ll be bringing the very latest on the Baggies throughout the week and around the clock.
Make sure you keep yourself updated with our handy daily catch up...
Must reads...
- Garry Monk can't believe Sheffield Wednesday lost to West Brom
- 'I spoke to him' - Every word from Bilic after Baggies stay above Leeds
- Here's how Ahmed Hegazi played on his West Brom comeback
- Things you might have missed as West Brom marched on
- Player ratings as Baggies keep title push rolling
For all your latest WBA news, opinion, analysis and transfer gossip, click here
You can follow our West Brom reporter Joseph Chapman on Twitter, and his email address is<EMAIL_ADDRESS>Hegazi was present in the penalty area for all of Albion’s set-pieces, although the defender’s aerial threat wasn’t utilised in the opening period with a string of poor deliveries.
With that being said, Hegazi had lost his marker Julian Borner on several occasions, with his opposite number providing a hands-on test for Hegazi to negotiate.
However, Hegazi’s lack of match sharpness crept into the fore once again when a breakdown in communication between himself and Filip Krovinovic let the ball slip through for Fletcher, however Bartley was there to thwart a Wednesday counter.
Hegazi was once again found in no man’s land as half-time approached, being pulled out of position by Fletcher before failing to make his tackle stick and that enabled Kieran Lee to work some space before Conor Townsend cleared.
West Bromwich Albion on social media
If you want to follow all things Albion via social media then this is the place to find out how.
Transfers, injuries, match-day videos and photos and the thoughts of the manager and his players, we’ve got you covered.
We’ll be bringing the very latest throughout the week and around the clock.
Make sure you keep yourself updated with our social media accounts...
The Baggies on social media...
Facebook: News, debate and nostalgia
Twitter: All the latest news as it happens
For all your latest WBA news, opinion, analysis and transfer gossip, click here
You can follow our reporter Joseph Chapman on Twitter, and his email address is<EMAIL_ADDRESS>The 28-year-old returned for the second-half offering a more reassured performance than at the end of the first-half.
The visitors started the second period strongly and Hegazi’s positioning was vital to breaking down Sheffield’s attack, and the centre-back was confident in neutralising the threat of Lee when Wednesday countered down Albion’s left.
Then the most hair-raising moment of the game occurred in the 63rd minute, and it was all of Hegazi’s own doing.
The Egyptian was hapless in possession and gifted the ball to Sheffield substitute Adam Reach in a dangerous area, and just as the midfielder looked to play in Fletcher who was free in the box, Hegazi got a vital toe to deflect the ball away before racing across to block Reach’s low strike.
The presence of Wednesday striker Fletcher had given Hegazi a constant headache and his battle with the forward was summarised when Fletcher drifted off his shoulder before being picked out by Bannan, and then lifted the ball over Hegazi and rifling a volley over the crossbar.
Hegazi was left in a tangle but the referee’s whistle had spared the Egyptian’s blushes, adjudging Fletcher to have handled the ball in the build-up.
And in the 74th minute, Hegazi’s afternoon came to a premature conclusion as he was substituted, with Bilic opting to bring on Gareth Barry and drop Semi Ajayi into the centre-half role.
A mixed afternoon for Hegazi, who gained some vital minutes under his belt.
However, it’s clear to see he is still some way off the pace and with Romaine Sawyers and Jake Livermore returning to the fold for midweek, it seems unlikely that he will retain his place in the starting XI.


{% include 'snipets/sidebar.html' %}
Toggle navigation
ORGAN DONATION IN THE US - DATA TABLE
Github / Code
Dropdown
Pie Chart
Bar Chart
Maps
{% include 'snipets/footer.html' %}


{% extends "account/_base.html" %} {% load i18n %} {% load account %} {% block head_title %}{% trans "Confirm E-mail Address" %}{% endblock %} {% block body %}
{% blocktrans with confirmation.email_address.email as email %} Please confirm that {{ email }} is an e-mail address for user {{ user_display }}. {% endblocktrans %}
{% else %} {% url 'account_email' as email_url %}{% blocktrans %} This e-mail confirmation link has expired or is invalid. Please generate a new e-mail confirmation request. {% endblocktrans %}
{% endif %}


Total Time:1hr 30min
Prep:1 hr
Cook:30 min
Difficulty:Easy
Course:Desert
Ingredients
*3 cups self-rising flour *1/2 teaspoon salt *1 cup unsalted butter, at room temperature *2 cups white sugar
*4 eggs, at room temperature *1 teaspoon vanilla extract *2 tablespoons lemon zest
*1 cup whole milk, divided *2 1/2 tablespoons fresh lemon juice, divided Lemon Cream Icing *2 cups chilled heavy cream *3/4 cup confectioners' sugar *1 1/2 tablespoons fresh lemon juice
Instruction
Preheat oven to 375 degrees F (190 degrees C). Line 30 cupcake pan cups with paper liners.
Sift the self-rising flour and salt together in a bowl. In another bowl, beat the unsalted butter and sugar with an electric mixer until light and fluffy. Beat in the eggs one at a time, beating each egg until incorporated before adding the next. Mix in the vanilla extract and lemon zest.
Gently beat the flour mixture into the butter mixture, one third at a time, alternating with half the milk and half the lemon juice after each of the first 2 additions of flour. Beat until just combined; do not over mix.
Fill the prepared cupcake liners with batter 3/4 full, and bake in the preheated oven until a toothpick inserted in the center comes out clean, about 17 minutes. Let the cupcakes cool in the pans for about 10 minutes before removing them to finish cooling on a rack.
To make the icing, beat the cream in a chilled bowl with an electric mixer set on Low until the cream begins to thicken. Add the confectioners' sugar and lemon juice, a little at a time, beating after each addition, until fully incorporated. Increase the mixer speed to High, and beat until the icing forms soft peaks, about 5 minutes. Spread on the cooled cupcakes. Refrigerate leftovers.


|
Pip-Services-Components-Dotnet
|
Abstract lock that implements default lock acquisition routine. More...
Public Member Functions | |
| virtual void | Configure (ConfigParams config) |
| Configures component by passing configuration parameters. More... | |
| abstract bool | TryAcquireLock (string correlationId, string key, long ttl) |
| Makes a single attempt to acquire a lock by its key. It returns immediately a positive or negative result. More... | |
| abstract void | ReleaseLock (string correlationId, string key) |
| Releases prevously acquired lock by its key. More... | |
| void | AcquireLock (string correlationId, string key, long ttl, long timeout) |
| Makes multiple attempts to acquire a lock by its key within give time interval. More... | |
Private Attributes | |
| int | _retryTimeout = 100 |
Abstract lock that implements default lock acquisition routine.
options:
See ILock
| void PipServices3.Components.Lock.Lock.AcquireLock | ( | string | correlationId, |
| string | key, | ||
| long | ttl, | ||
| long | timeout | ||
| ) |
Makes multiple attempts to acquire a lock by its key within give time interval.
| correlationId | (optional) transaction id to trace execution through call chain. |
| key | a unique lock key to acquire. |
| ttl | a lock timeout (time to live) in milliseconds. |
| timeout | a lock acquisition timeout. |
Implements PipServices3.Components.Lock.ILock.
|
virtual |
Configures component by passing configuration parameters.
| config | configuration parameters to be set. |
|
pure virtual |
Releases prevously acquired lock by its key.
| correlationId | (optional) transaction id to trace execution through call chain. |
| key | a unique lock key to acquire. |
Implements PipServices3.Components.Lock.ILock.
Implemented in PipServices3.Components.Lock.MemoryLock.
|
pure virtual |
Makes a single attempt to acquire a lock by its key. It returns immediately a positive or negative result.
| correlationId | (optional) transaction id to trace execution through call chain. |
| key | a unique lock key to acquire. |
| ttl | a lock timeout (time to live) in milliseconds. |
Implements PipServices3.Components.Lock.ILock.
Implemented in PipServices3.Components.Lock.MemoryLock.


{% extends "predictions/_base.html" %} {% block main %} {% if event_list %}
Hmmm, no events are available. Check back later.


+++ title = "San Salvador" lat = 13.706699 lon = -89.208984 +++
San Salvador is the capital city, and the only really sizeable city, in the tiny Central American nation of El Salvador. I didn't go into the city, or explore the country at all, on this trip — I just passed through San Salvador airport, and changed flights, on my way from Brazil to the USA.


About Me
I have been developing software for + years and my expertise lies in building mobile applications and websites with scalable backend APIs.
I have worked at large software consulting organisations and small startups. I enjoy learning new things, and I am always looking for new challenges.
Skills
React, Angular, JavaScript, TypeScript, tailwindcss, Bootstrap,
React Native, Ionic Framework(with Cordova/Capacitor),
.NET(core), C#, ASP.NET,
Microsoft Azure, Microsoft SQL Server, Identity Server, Entity Framework, Git
Agile/Scrum
Work Experience
NSW eHealth
Senior Developer
2022 - ...
- Working on a new web app built using Angular, ASP.NET, and Azure Cognitive Search.
- Responsibilities include building UI and supporting APIs
- Setting up the TDD process for the frontend application
CBHS Health Fund Limited
Mobile App / Web Developer
2016 - 2021
- Building mobile apps CBHS Health, CBHS Corp and CBHS International. Includes architecting backend APIs and Authentication framework(using Identity Server).
- Maintaining CBHS Health Fund, CBHS Corporate Health and CBHS International Health websites build on React, .NET and Sitefinity.
- Training developers on ionic, angular, .NET Core and Clean Code principles
EFFISION
Solutions Developer
2015 - 2016
- Worked on developing and maintaining insurance underwriting portal, build on ASP.NET
- Built POSFLO a Point of Sale and media distribution mobile app using AngularJS and ionic
Capgemini
Manager, Technical Lead, Sr. Consultant
2008 - 2014
- Worked as Microsoft Azure and MS.NET Technology Lead / Technical Architect
- Worked on building scalable backend APIs for hangout and social events app on MS Azure
- Led teams for Level 2 and Level 3 support, which was responsible for handling direct customer queries and helping them to complete business processes
- Couple of assignment is Switzerland and France.
3 Global Services (now Tech Mahindra Business Services)
Project Lead, Sr. Developer
2005 - 2008
- Helped to setup the SDLC process, which included minimum documentation for new application development, set code review guidelines and other quality processes
- Led projects through various stages of requirement gathering, project planning, writing technical specifications, development, testing and support
- Worked as a trainer to conduct ASP.NET (new features) training for the team, which helped developers to quickly learn and implement new features in upcoming projects


--- layout: documentation title: StreamObjectType ---
The StreamObjectType type is intended to characterize NTFS alternate data streams.
| Field Name | Type | Description |
|---|---|---|
| Hash1..n | HashType |
The Hash field specifies a single calculated hash value. |
| Name0..1 | StringObjectPropertyType |
The Name field specifies the name of the alternate data stream. |
| Size_In_Bytes0..1 | UnsignedLongObjectPropertyType |
The Size_In_Bytes field specifies the size of the alternate data stream, in bytes. |


Reset
Dietitian Assessment
Patient Details
URN:
[[PMI.URN]]
Family Name:
[[PMI.LASTNAME]]
Given Name:
[[PMI.FIRSTNAME]]
DOB:
[[PMI.DOB]]
Sex:
[[PMI.SEX]]
P/S:
[[PMI.STATUS]]
Option 1
Testing Dropdown:
1
2
3
4
Assessment Date:
Interview Location
Inpatient
Outpatient
Other
Ward:
Clinic:
Other:
Diet Details
Normal Diet
Bland Diet
Nil Orally
Special Notes:
Measure
BMI:
Height:
cm
Weight:
kg
Comments
Dietitian:
Report Date:


MOONLIGHT AND VALENTINO A film review by Edwin Jahiel Copyright 1995 Edwin Jahiel
(1995) 1/2 * Directed by David Anspaugh. Written by Ellen Simon, from her stage-play. Photography, Julio Macat. Music : Howard Shore. Cast: Elizabeth Perkins (Rebecca), Whoopi Goldberg (Sylvie), Gwyneth Paltrow (Lucy), Kathleen Turner (Alberta), Jon Bon Jovi (no name). A Grammercy picture. 103 minutes. Rated R (language)
A combination of coincidence and trend has just brought us at least three new American movies either directed by women and/or with a nearly all-female cast: Diane Keaton's UNSTRUNG HEROES, David Anspaugh's (HOOSIERS) MOONLIGHT AND VALENTINO, and, by Australian Jocelyn Moorhouse (PROOF), HOW TO MAKE AN AMERICAN QUILT.

MOONLIGHT AND VALENTINO is a would-be tearjerker. The problem is that the tears are on the screen and not in the audience, unless you count tears caused by boredom.
The script, from a play by Neil Simon's daughter, suffers from uninteresting everything: characters, acts, facts and dialogue. A lot of useless yakety-yak here makes the sluggish pace even slower. The talk is of time-killing trivia. The death-in-the-family treatment is far inferior to that in UNSTRUNG HEROES. The roles are dull and artificially constructed--much less attention-getting than those in HOW TO MAKE AN AMERICAN QUILT.
The consolers are themselves in need of drastic straightening out too. The ladies bond, de-bond, re-bond. A hefty Whoopi Goldberg, a pottery maker, is unstable, with pathological fears about her husband leaving her. Gwyneth Paltrow, still mixed up from the long-ago death of her mother, spots a kooky, perpetually hat-wearing student of her sister Perkins. The movie telegraphs with hammer-blows that a new twosome is in the making. And as Paltrow has troubles with her virginity, she first shows her body to Big Sis who decrees "You're a knockout. You should never wear clothes." Then she asks Sis for advice on how to moan during sex. Perkins obliges. ( I am not making any of this up). And to think that they now blame the Internet.
Kathleen Turner--whose best role by far was in SERIAL MOM--is photographed in terribly unflattering ways, with the focus on her oddly soft nose, while she has an un-dimensional, vague part as a self-centered, hard-nosed business exec.
It takes 29 minutes into the film (during which time you waste your energy deciphering matters) to establish relationships or unscramble who's who and what's what. Even then things are not always clear.
The neighborhood seems to be bucolic suburbia--with too many pretty landscape shots--of the "On Golden Pond" school. For some reason, sentimental family gatherings in movies are located in the East of the United States, unlike the enormous majority of other subjects that all take place in California. (Ph.D. thesis, anyone?)
Perkins teaches a three-minute class (sic). She also injects Francois Truffaut in her lectures, for no discernible reason. Distraught Perkins (the very actress who was recently quoted as deriding Demi Moore's nudity in movies) takes a bath. The mixing of pathos and nipples is counterproductive, distracting indeed, as it is known from statistics that 94.67 percent of men are voyeurs to some degree.
Turner turns out to be the former stepmother of Perkins and Paltrow, whose father, at the funeral reception, is coyly told by his ex that she needs a hug and kisses.  That's the movie's best line.
Except for Paltrow's new boyfriend, the main male presence is Bon Jovi's. He is a house painter, an Italian who speaks no English, and whose buns inflame the women's libido. They discuss them openly, until the man turns out to be a real Yankee. (Score one for sitcom humor). His name is wrongly believed to be Valentino, hence the awkward title. The other part of the title comes from Bon Jovi showing up at night to paint the Perkins home. Why night? He's a romantic, which leads of course to intercourse that speeds up Perkins' healing process. (He also relaxes Perkins by teaching her how to eat pizza with her fingers).How exciting. There is a mystery however: is why change the house color from a perfectly nice gray to the color of regurgitation?
The bottom line in this film is that everyone, but everyone, is uninteresting. Not only is everyone unconvincing, but everything stultifies us with boredom, down to the heavy, lachrymose musical score.
Capping all this, the "good-bye to Ben" (Perkins' defunct spouse) finale has all the women, with painted faces, coming to terms with the past by doing a kind of witchcrafty ritual at night, in the cemetery, with loud music and song plus up and down dancing. Then a magic rain falls. Ugh!
The review above was posted to the
rec.arts.movies.reviews newsgroup (de.rec.film.kritiken for German reviews).
The Internet Movie Database accepts no responsibility for the contents of the
review and has no editorial control. Unless stated otherwise, the copyright
belongs to the author.
Please direct comments/criticisms of the review to relevant newsgroups.
Broken URLs inthe reviews are the responsibility of the author.
The formatting of the review is likely to differ from the original due
to ASCII to HTML conversion.
Related links: index of all rec.arts.movies.reviews reviews


JCEF - Java Chromium Embedded Framework
JCEF is a Java port of CEF framework for embedding Chromium-based browsers in applications using Swing.
Embedding of the browser component inside the IDE allows amongst others:
- rendering HTML content
- previewing generated HTML (e.g., from Markdown)
Enabling JCEF
Using JCEF requires using a dedicated JetBrains Runtime, please follow these installation instructions on how to obtain and activate it in your IDE.
Enable ide.browser.jcef.enabled
in Registry dialog (invoke Help | Find Action and type “Registry”) and restart the IDE for changes to take effect.
Debugging
The Chrome DevTools, embedded into JCEF, can be used as a debugging and profiling tool. It’s active by default, so that a Chrome DevTools client can attach to it via the default port number - 9222
.
The port number can be configured with the following registry key:
ide.browser.jcef.debug.port=9222
JavaScript debugger in IntelliJ IDEA Ultimate can thus be used to debug JavaScript code running in the IDE via the Chrome DevTools. Use the Attach to Node.js/Chrome configurations with a proper port number.
Also, JCEF provides a default Chrome DevTools front-end (similar to the one in the Chrome browser) that can be opened from the JCEF’s browser component context menu via Open DevTools (the menu item is available in internal mode only).
To access the Chrome DevTools in plugin code, use the following API:
JBCefBrowser myBrowser = new JBCefBrowser(myUrl);
CefBrowser myDevTools = myBrowser.getCefBrowser().getDevTools();
JBCefBrowser myDevToolsBrowser = new JBCefBrowser(myDevTools, myBrowser.getJBCefClient());
Or in order to just open it in a separate window:
JBCefBrowser myBrowser = new JBCefBrowser(myUrl);
myBrowser.openDevTools();
API
com.intellij.ui.jcef.JBCefApp
Performs JCEF auto-initialization, manages its lifecycle, and provides JBCefClient
instances.
com.intellij.ui.jcef.JBCefClient
Is tied to every browser component explicitly or implicitly. Used for adding handlers to the associated browser. The same instance can be shared among multiple browsers. It is up to the developer to use a shared or per-browser instance, depending on the handlers’ logic. If a client was created explicitly, it should be disposed by the developer; otherwise, it is disposed automatically following the associated browser instance disposal.
com.intellij.ui.jcef.JBCefBrowser
Provides the browser UI component:
JComponent getComponent();
Provides the load methods (callable from non-EDT thread as well):
void loadURL(String);
void loadHTML(String);
For executing JS code and callbacks (see below), use the wrapped CefBrowser
instance directly:
getCefBrowser().executeJavaScript(String code, String url, int line);
By default, JBCefBrowser
is created with implicit JBCefClient
(disposed automatically). It is possible to pass your own JBCefClient
(disposed by the developer).
For accessing:
JBCefClient getJBCefClient();
The simplest way to add a browser component to your UI:
JPanel myPanel = ...
myPanel.add(new JBCefBrowser(“https://www.jetbrains.com”).getComponent());
com.intellij.ui.jcef.JBCefJSQuery
Provides JS query callback mechanism.
There’s no direct access to JS DOM from Java (like in JavaFX WebView, see also this issue). Still, JCEF provides an asynchronous way to communicate to JS.
It’s simpler to illustrate it by an example. Say, we want to open a link in an external browser (see it in MarkdownJCEFHtmlPanel
):
// Create a JS query instance
final JBCefJSQuery myJSQueryOpenInBrowser =
JBCefJSQuery.create(myJBCefBrowser);
// Add a query handler
myJSQueryOpenInBrowser.addHandler((link) -> {
MarkdownAccessor.getSafeOpenerAccessor().openLink(link);
return null; // can respond back to JS with JBCefJSQuery.Response
});
// Inject the query callback into JS
myCefBrowser.executeJavaScript(
"window.JavaPanelBridge = {" +
"openInExternalBrowser : function(link) {" +
myJSQueryOpenInBrowser.inject("link") +
"}" +
"};",
getCefBrowser().getURL(), 0);
// Dispose the query when necessary
Disposer.dispose(myJSQueryOpenInBrowser);


Email sent successfully
to_email: {{to_email}}
from_email: {{from_email}}
subject: {{subject}}
message: {{message}}


If you want to authenticate your user in your app with Github use omniauth-github strategy for that. Here I am describing how you can do that very quickly. OmniAuth provides list of strategies to use many OAuth for your application. Here is the List of Strategies.
Github uses the OAuth2 flow. First of all you have to register your app with Github GitHub Applications Page. Create a new application here and get Client ID and Secret. Here is how can you obtain Client ID and Secret from Github.
Steps to use these in your app.
1
rails new GithubAuthApp
omniauth-github
1
gem "omniauth-github"
1
2
3
4
use OmniAuth::Builder do
provider :github, XXXX, YYYY
end
All done start you server
1
|
|
Just open your app in browser with URL
1
|
|
You will be redirecting to Github for authentication.
After success your app will redirect to your given callback URL with information and token!
At OmniAuth.org you can try out different -2 Strategies.
Useful links :
- OmniAuth.org One page for all you need.
- omniauth-github gem.


{% load zenaida %}{% td_to_dict event.check_postmark_cutoff|td_timeuntil as time_until_check_cutoff %} {% if time_until_check_cutoff.days >= 0 %}
Checks should be made out to {{ event.organization.check_payable_to }} and include your order code ({{ order.code }}) in the memo line. Mail them to:
{{ event.organization.check_recipient }}
{{ event.organization.check_address }}{% if event.organization.check_address_2 %}
{{ event.organization.check_address_2 }}
{% endif %}
{{ event.organization.check_city }}, {{ event.organization.check_state_or_province }} {{ event.organization.check_zip }} {{ event.organization.check_country }}
Checks must be postmarked no later than {% if time_until_check_cutoff.days == 0%}today{% else %}{{ event.check_postmark_cutoff|date:"F jS, Y" }}{% endif %}. If your payment is not postmarked by {% if time_until_check_cutoff.days == 0%}today{% else %}that date{% endif %}, the event organizer reserves the right to revoke your passes.
{% else %}Payment was due to be postmarked no later than {{ event.check_postmark_cutoff|date:"F jS, Y" }}. The event organizer reserves the right to revoke your passes if you have not sent in your payment.
{% endif %}


Package io.ciera.runtime.summit.util
Interface TIM
-
- All Known Implementing Classes:
TIMImpl
public interface TIM
Time manipulaiton utilities and utilites for setting and modifiying timers.
-
-
Method Summary
All Methods Instance Methods Abstract Methods Modifier and Type Method Description long
advance_time(long microseconds)
Advance the system clock by the specified number of microseconds.Date
create_date(int year, int month, int day, int hour, int minute, int second)
Create a newDate
object from the input parameters.long
current_clock()
Get the current system time in microseconds since the epoch.Date
current_date()
Get the current date.int
current_seconds()
Get the current time in seconds since the epoch.int
get_day(Date date)
Get the day of the month from a date object.int
get_hour(Date date)
Get hour of the day from a date object.int
get_minute(Date date)
Get minute of the hour from a date object.int
get_month(Date date)
Get the month of the year from a date object.int
get_second(Date date)
Get second of the minute from a date object.int
get_year(Date date)
Get year from a date object.void
set_epoch(int day, int month, int year)
Set the instant in time from which the system clock counts.long
set_time(int year, int month, int day, int hour, int minute, int second, int microsecond)
Set the system clock time.long
time_of_day(long timeval)
Get the number of microseconds since the beginning of the current day.boolean
timer_add_time(int microseconds, TimerHandle timer_inst_ref)
Add time to a running timer.boolean
timer_cancel(TimerHandle timer_inst_ref)
Cancel a running timer.int
timer_remaining_time(TimerHandle timer_inst_ref)
Get the remaining time of a running timer in microseconds.boolean
timer_reset_time(int microseconds, TimerHandle timer_inst_ref)
Reset the timer and set a new duration from the current system time.TimerHandle
timer_start(EventHandle event_inst, int microseconds)
Start a new timer to wake inmicroseconds
microseconds from the current system time.TimerHandle
timer_start_recurring(EventHandle event_inst, int microseconds)
Start a new recurring timer to wake inmicroseconds
microseconds from the current system time.String
timestamp_format(long timestamp, String format)
Format a timestamp according to a format string.String
timestamp_to_string(long timestamp)
Format a timestamp as a string representing the number of microseconds since the current epoch.
-
-
-
Method Detail
-
advance_time
long advance_time(long microseconds)
Advance the system clock by the specified number of microseconds. All timers that have expiration times earlier than the resulting time will immediately be fired.- Parameters:
microseconds
- number of microseconds to advance the clock- Returns:
- the system clock time after it has been advanced
-
create_date
Date create_date(int year, int month, int day, int hour, int minute, int second)
Create a newDate
object from the input parameters.- Parameters:
year
- the year A.D.month
- the month of the yearday
- the day of the monthhour
- the hour of the dayminute
- the minute of the hoursecond
- the second of the minute- Returns:
- a new
Date
object from the input parameters
-
current_clock
long current_clock()
Get the current system time in microseconds since the epoch.- Returns:
- the current time
-
current_date
Date current_date()
Get the current date.- Returns:
- the current date
-
current_seconds
int current_seconds()
Get the current time in seconds since the epoch.- Returns:
- the current seconds
-
get_day
int get_day(Date date)
Get the day of the month from a date object.- Parameters:
date
- the input date- Returns:
- the day of the month for the input date
-
get_month
int get_month(Date date)
Get the month of the year from a date object.- Parameters:
date
- the input date- Returns:
- the month of the year for the input date
-
get_year
int get_year(Date date)
Get year from a date object.- Parameters:
date
- the input date- Returns:
- the year for the input date
-
get_hour
int get_hour(Date date)
Get hour of the day from a date object.- Parameters:
date
- the input date- Returns:
- the hour of the day for the input date
-
get_minute
int get_minute(Date date)
Get minute of the hour from a date object.- Parameters:
date
- the input date- Returns:
- the minute of the hour for the input date
-
get_second
int get_second(Date date)
Get second of the minute from a date object.- Parameters:
date
- the input date- Returns:
- the second of the minute for the input date
-
set_epoch
void set_epoch(int day, int month, int year)
Set the instant in time from which the system clock counts. Ifset_epoch
is not called, the system clock will initialize at the current number of microseconds from the January 1, 1970 00:00:00 UTC and count up. Setting the epoch will change this reference instant tomonth
,day
,year
00:00:00 UTC. Note: this call may result in unexpected timer behavior as the expiration times will shift by the difference in epoch.- Parameters:
day
- the day of the month of the new epochmonth
- the month of the year of the new epochyear
- the year of the new epoch
-
set_time
long set_time(int year, int month, int day, int hour, int minute, int second, int microsecond)
Set the system clock time. All timers that have expiration times earlier than the resulting time will immediately be fired.- Parameters:
year
- the new system time yearmonth
- the new system time month of the yearday
- the new system time day of the monthhour
- the new system time hour of the dayminute
- the new system time minute of the hoursecond
- the new system time second of the minutemicrosecond
- the new system time microsecond of the second- Returns:
- the new system time in microseconds since the current epoch
-
time_of_day
long time_of_day(long timeval)
Get the number of microseconds since the beginning of the current day.- Parameters:
timeval
- timestamp value- Returns:
- the number of microseconds since 00:00:00 UTC of the current day
-
timer_add_time
boolean timer_add_time(int microseconds, TimerHandle timer_inst_ref)
Add time to a running timer.- Parameters:
microseconds
- the time to add in microsecondstimer_inst_ref
- the timer handle to add time to- Returns:
- true if successful, false otherwise
-
timer_cancel
boolean timer_cancel(TimerHandle timer_inst_ref)
Cancel a running timer.- Parameters:
timer_inst_ref
- the timer handle to cancel- Returns:
- true if successful, false otherwise
-
timer_remaining_time
int timer_remaining_time(TimerHandle timer_inst_ref)
Get the remaining time of a running timer in microseconds.- Parameters:
timer_inst_ref
- the timer handle to inspect- Returns:
- the remaining time of the timer in microseconds
-
timer_reset_time
boolean timer_reset_time(int microseconds, TimerHandle timer_inst_ref)
Reset the timer and set a new duration from the current system time.- Parameters:
microseconds
- the new duration from the current system time to set in microsecondstimer_inst_ref
- the timer handle to reset- Returns:
- true if successful, false otherwise
-
timer_start
TimerHandle timer_start(EventHandle event_inst, int microseconds)
Start a new timer to wake inmicroseconds
microseconds from the current system time. The architecture does not guarantee the timer will wake in exactlymicroseconds
microseconds, however it does guarantee that it will be at least that long. When the timer wakes, theevent_inst
will be added to the system event queue.- Parameters:
event_inst
- the event to generate when the timer wakesmicroseconds
- the duration from the current system time to set in microseconds- Returns:
- a handle to the newly created timer
-
timer_start_recurring
TimerHandle timer_start_recurring(EventHandle event_inst, int microseconds)
Start a new recurring timer to wake inmicroseconds
microseconds from the current system time. The architecture does not guarantee the timer will wake in exactlymicroseconds
microseconds, however it does guarantee that it will be at least that long. When the timer wakes, theevent_inst
will be added to the system event queue. The timer will then be reset to wake again atmicroseconds
after the system time when the timer event was last generated.- Parameters:
event_inst
- the event to generate when the timer wakesmicroseconds
- the duration from the current system time to set in microseconds- Returns:
- a handle to the newly created timer
-
timestamp_format
String timestamp_format(long timestamp, String format)
Format a timestamp according to a format string. This implementation follows the format documented inDateTimeFormatter
.- Parameters:
timestamp
- the timestamp to formatformat
- the format string- Returns:
- a formatted string representing the timestamp
-
timestamp_to_string
String timestamp_to_string(long timestamp)
Format a timestamp as a string representing the number of microseconds since the current epoch.- Parameters:
timestamp
- the timestamp to format- Returns:
- the string representation of microseconds
-
-


<model-viewer>
Easily display interactive 3D models on the web & in AR
Quick Start
Getting Started
Documentation
-
Examples: Advanced usage
-
API Reference
Addons
-
Examples
-
API Reference
<model-viewer-effects>
Browser Support
<model-viewer>
is supported on the last two major versions of all evergreen
desktop and mobile browsers, plus the last two versions of Safari (on MacOS and iOS).
These browser features are only needed if you wish to use webxr in ar-modes:
| Feature | ||||||
|---|---|---|---|---|---|---|
| WebXR Device API | ||||||
| WebXR HitTest API | ||||||
| WebXR DOM Overlay API |
Natively supported
Available with polyfill
Behind a flag, unstable
Not available


{{businessModelName}} of {{featureModel.name}}
Legend:
Modification:
Add Business Model Decision
Delete Business Model Decision
Conformance:
Conformance Error (see below)
Missing Mandatory Decision
Conformance Check
- {{error}}