issue-#64 Wingdings dependency in StdLinks
- Josef Templ
- Posts: 2047
- Joined: Tue Sep 17, 2013 6:50 am
Re: issue-#64 Wingdings dependency in StdLinks
"Segoe UI Symbol" is not available on my Windows Vista.
It is possible that some of these (exotic) fonts are installed together with other
software, for example with Microsoft Office or Internet Explorer or a particular
version of that.
I would not use one of them as it will always causes troubles on some
platform or in the future. As long as nobody can point us to a reliable documentation
about the availability and contents of those fonts we should not use one of them.
- Josef
It is possible that some of these (exotic) fonts are installed together with other
software, for example with Microsoft Office or Internet Explorer or a particular
version of that.
I would not use one of them as it will always causes troubles on some
platform or in the future. As long as nobody can point us to a reliable documentation
about the availability and contents of those fonts we should not use one of them.
- Josef
-
- Posts: 1700
- Joined: Tue Sep 17, 2013 12:21 am
- Location: Russia
Re: issue-#64 Wingdings dependency in StdLinks
IMHO, better to do the same as we made with StdFolds...
- Josef Templ
- Posts: 2047
- Joined: Tue Sep 17, 2013 6:50 am
Re: issue-#64 Wingdings dependency in StdLinks
I also considered this variant but rejected it becauseIvan Denisov wrote:IMHO, better to do the same as we made with StdFolds...
- it is too much effort
- it complicates the module significantly which may create more future maintenance work
- we know from StdFolds that it is not possible to get a good rendering result without filling the glyphs
- StdLinks are for developers only, not for end-users; the look is more or less irrelevant.
- Josef
Re: issue-#64 Wingdings dependency in StdLinks
I prefer following the StdFolds's implementation.
much work has be done when working on StdFolds. StdLinks will be easy to do than it;
and I think Ivan can give us a good implementation base his work on StdFolds, if we would.
a good rendering result is not important,the link views are invisible for most of time .
I use BB as my favorite text editor, StdLinks used everywhere,most for external linking.
much work has be done when working on StdFolds. StdLinks will be easy to do than it;
and I think Ivan can give us a good implementation base his work on StdFolds, if we would.
a good rendering result is not important,the link views are invisible for most of time .
I use BB as my favorite text editor, StdLinks used everywhere,most for external linking.
Re: issue-#64 Wingdings dependency in StdLinks
See Wikipedia https://en.wikipedia.org/wiki/Help:Special_charactersJosef Templ wrote:"Segoe UI Symbol" is not available on my Windows Vista.
The font "Segoe UI Symbol" is available on my Windows 8.1 and works on my Ubuntu 14.04 with Wine 1.6.Wikipedia wrote: Windows 7
Unicode support is extended through installing the optional standalone Windows Update package KB2729094,[1] available for both 32-bit and 64-bit versions of Windows 7 SP1 from the Microsoft Download Center. This backport from Windows 8 updates the Segoe UI font by adding browser support for Emoji and other symbols to Windows 7.
On both operating systems the BlackBox documents have the same look an feel for links, target and folds.
The font "Wingdings" doesn't work on my Ubuntu system. Wingdings is an ASCII font and not a Unicode font.
- Josef Templ
- Posts: 2047
- Joined: Tue Sep 17, 2013 6:50 am
Re: issue-#64 Wingdings dependency in StdLinks
I have created topic branch issue-#64 in Github.
The currently committed changes are mainly based on CPC 1.7 rc5, i.e. with
non changes in the look on most platforms. It still uses Wingdings
but adds a high byte F0 for Russian Windows compatibility.
We can keep this until somebody reports a problem with it.
The new DefaultAppearance uses the icon texts =>, <=, >>, << as has been discussed before.
This form of DefaultAppearance has the important property of being language independent.
Personally I prefer the DefaultAppearance over the Wingdings glyphs because of better
visibility in the text and complete platform independence. But when in doubt, don't
make a change. We can change it later if new problems arise.
The main technical problem has not been addressed so far:
The size (w, h) is not adapted to the platform upon internalizing.
May be some BB framework expert has an idea how to do it.
For the changes see http://redmine.blackboxframework.org/pr ... 3d1bc6e0a6.
- Josef
The currently committed changes are mainly based on CPC 1.7 rc5, i.e. with
non changes in the look on most platforms. It still uses Wingdings
but adds a high byte F0 for Russian Windows compatibility.
We can keep this until somebody reports a problem with it.
The new DefaultAppearance uses the icon texts =>, <=, >>, << as has been discussed before.
This form of DefaultAppearance has the important property of being language independent.
Personally I prefer the DefaultAppearance over the Wingdings glyphs because of better
visibility in the text and complete platform independence. But when in doubt, don't
make a change. We can change it later if new problems arise.
The main technical problem has not been addressed so far:
The size (w, h) is not adapted to the platform upon internalizing.
May be some BB framework expert has an idea how to do it.
For the changes see http://redmine.blackboxframework.org/pr ... 3d1bc6e0a6.
- Josef
-
- Posts: 1700
- Joined: Tue Sep 17, 2013 12:21 am
- Location: Russia
Re: issue-#64 Wingdings dependency in StdLinks
In Wine this code does not resolving the problem, however in Windows it does.
I have tested version: http://blackboxframework.org/unstable/i ... a1.209.zip in Russian windows.
Left as it was, right as it became.
I have tested version: http://blackboxframework.org/unstable/i ... a1.209.zip in Russian windows.
Left as it was, right as it became.
- Josef Templ
- Posts: 2047
- Joined: Tue Sep 17, 2013 6:50 am
Re: issue-#64 Wingdings dependency in StdLinks
What happens in Wine? Isn't the DefaultAppearance used?
That is at least the intention if WingDings is not available.
The DefaultAppearance does not depend in Wingdings.
- Josef
That is at least the intention if WingDings is not available.
The DefaultAppearance does not depend in Wingdings.
- Josef
-
- Posts: 1700
- Joined: Tue Sep 17, 2013 12:21 am
- Location: Russia
Re: issue-#64 Wingdings dependency in StdLinks
No, in Wine the Windows appearance is used. Lets change the Init code like this:Josef Templ wrote:What happens in Wine? Isn't the DefaultAppearance used?
That is at least the intention if WingDings is not available.
The DefaultAppearance does not depend in Wingdings.
Code: Select all
PROCEDURE Init;
VAR font: Fonts.Font; d: StdDirectory;
PROCEDURE DefaultAppearance;
BEGIN font := Fonts.dir.Default(); iconFont := font.typeface;
linkLeft := "=>"; linkRight := "<=";
targetLeft := ">>"; targetRight := "<<";
coloredBackg := TRUE
END DefaultAppearance;
BEGIN
NEW(d); dir := d; stdDir := d;
IF Dialog.IsWindows() & ~ Dialog.IsWine() THEN
iconFont := "Wingdings";
...
END Init;
Re: issue-#64 Wingdings dependency in StdLinks
About Wine:
The font "Wingdings" exist in Wine. Not all "Wingdings" symbols displays correctly in Wine. That is the reason why default is not used.
A similar situation we have with Windows 7:
The font "Segoe UI Symbol" exist in Windows 7. Not all "Segoe UI Symbol" symbols displays correctly in Windows 7. That is the reason why default is not used.
Who will test all those bloody combinations?
How can I find out inside my program without looking on the monitor:
When the font exist, is the symbol (which I use) displayed correctly?
The font "Wingdings" exist in Wine. Not all "Wingdings" symbols displays correctly in Wine. That is the reason why default is not used.
A similar situation we have with Windows 7:
The font "Segoe UI Symbol" exist in Windows 7. Not all "Segoe UI Symbol" symbols displays correctly in Windows 7. That is the reason why default is not used.
Who will test all those bloody combinations?
How can I find out inside my program without looking on the monitor:
When the font exist, is the symbol (which I use) displayed correctly?