It's a SAP Smart Form / Smart Style problem.
A Character style "N 12P" was defined in the Smart Style as a normal font and not a bold. This Smart Style was used in the from.
Inside the form settings, for a Label field, N 12P was selected as its "Character Format" from the drop down list. The "paragraph format" is standard "left aligned".
However, this label field, in place of "normal" display, is becoming "bold"!
Therefore, even if in the smartstyle, the format N 12P, was defined as a normal character, somehow its attributes are getting changed (turning it into a bold character).
Further digging down the character attributes window for that label (General Attributes window → Edit → Formats (glass icon) → double-click format N P12 → opens the Character attributes window), the Bold field was found marked with a *. On clicking the *, the "Font attribute bold Type" window displays "inherited".
So, somewhere the Smart Style's character attribute is changing from "normal" to "bold", and this change is somehow being inherited. What possibly could have gone wrong? Is it possible to override the Smart Style's format attribute from within a smartform?
Please note that changing the Smart Style sheet is not possible. But anyways the format defined there is OK i.e. as normal. Therefore, no change is required in the Smart Style.
The assumption had worked. The text editor at the field level was overriding paragraph and character style settings. It worked after resetting these from within the editor. Thanks
Related
I use icomoon.io to create and manage my icon fonts. It's excellent and you can set "ligatures" for the text you want to display the icon.
However, I cannot find a sane way to handle missing ligatures to display a default or "missing" icon.
One insane way was I created an icon component and check the text against an array of ligatures. But this would mean that I must maintain the array to match the icons in my font.
everyDangLigature = ['star', 'arrow-up', ...]
iconText = everyDangLigature.includes(str) ? str : 'missing';
IcoMoon wrote me back with
...if you parse the CMAP table of the font, you could check if a glyph
exists by its code point.
Also asked the opentypejs group.
How does one go about parsing the CMAP table of the font?
Is there another way to elegantly handle missing ligatures in our icon fonts?
I was looking at the font-awesome source to quickly get an idea of how importing fonts and graphics works. I found the line:
.fa-spinner:before {
content: "\f110";
}
How does this refer to the spinner icon?
Where can I read about creating my own fonts and icons and using them?
That is a CSS declaration to enable you to use a shortcut like <span class="fa-spinner"> to produce a spinner icon. The content: CSS property means "place this content in this element, and the :before pseudoclass is used to place it before any content you might actually place in such a <span> in your markup.
\f110 is an escape sequence used to produce a character by its hexadecimal representation. It refers to the Unicode character at codepoint U+F110. This is in the "private use range", a range of character codes you're allowed to use for your own arbitrary symbols that don't necessarily correspond to any other character, such as a spinner icon. You can produce the same character in your markup without the assistance of CSS by simply using the equivalent HTML numeric character reference,
When I write CSS in Notepad++, the color coding sometimes seems inconsistent. Normally, selectors are shown in light purple but sometimes they are black for 1 or more lines consecutively. I don't see anything wrong with such lines. Why are they black? What am I missing here?
i'm not sure why that happened to you!?
but you can add keywords to notepad++ :
Setting => Style Configurator ..
Select your language and Style.
Add your keyword like color and etc , separated by space :
Usually, that sort of coloring indicates that the CSS rule immediately preceding the affected one hasn't been closed. Here's an example where I remove the closing brace from a rule in normalize.css, which affects the one that immediately follows in exactly the same way (ignoring the comment and the lack of bold type, of course):
Presumably then, the reason why the "first" declaration after that selector is affected but the subsequent ones are not is because the semicolon from the first declaration tells the syntax coloring parser to terminate the nonsensical statement which is formed by the selector. But I'm just blindly guessing.
If you're sure that the preceding rule has been closed properly, then the syntax coloring parser may have been confused. Try simply highlighting the rule, deleting it, and undoing; that usually works for me.
Since Notepad++ recognizes color of codes based on the language type, you can't able to view multiple languages with color codes in a same file. Even though CSS is a part of web designing, it is still a unique language. If you want to display the CSS codings inside the HTML to color, just change the language type to CSS (only for temporarily purpose). But, don't forget to revert the language conversion back to HTML before saving the file.
Steps: Language -> C -> CSS
My app does the following:
enumerate fonts installed on the clients machine, and populate a dropdown list with them
present a s:TextArea with special characters (like äöü)
update the TextArea's font family to the one selected in the dropdown
After it updates, there seems to be three possible results: the correct glyph, a blank space, or a fallback glyph in a device font (seems to be _serif, though the CSS style is _typewriter). My goal is to programmatically detect whether a device font supports all the glyphs in a chosen user font.
I have tried getBounds on various children (to detect 0 width, etc.), getting info about atoms, and comparing fontFamily for a correct glyph against fontFamily for a blank or fallback glyph. For formatting changes that dispatch a UpdateCompleteEvent or CompositionCompleteEvent, i am always doing my checks after it completes.
Is there another way to approach this, or am I missing something?
thanks.
enumerateFonts
hasGlyphs
According to the w3 XHTML specification, the label attribute specifies a shorter label for the option. However (using the try-it tool with FF3.5), I can't see any effect. Hence my question: what does this attribute really do?
EDIT
It seems that it overrides the label used in the dropdown list. The contents of the option are (as far as I know) only used as the default for the value. Does this (in IE7+) make the following two declarations equivalent?
<option label="Volvo">Volvo (Latin for 'I roll')</option>
and
<option label="Volvo" value="Volvo (Latin for 'I roll')">Whatever....</option>
Note: The label attribute is only supported by IE 7+. Try in IE and you will see the difference.
The label attribute defines a shorter version of the text which will appear for its option in the drop-down list of the select menu.
label is defined as an optional attribute of the option tag, meaning implementation of and support for the attribute is not required to be compliant with the W3C standard. More information can be found here about the option tag:
http://www.w3schools.com/tags/att_option_label.asp
And, here is the link to the W3C specification:
http://www.w3.org/TR/html4/interact/forms.html#edef-OPTION
(Edit):
#Martijn the only usefulness I see is that it allows the developer to define an option tag and the label sets the "viewable text", and close it shorthand, rather than having to also specify a separate closing option tag. This would result in less code/data sent to the browser/device, which might have implications in mobile applications.