Font naming schemes (mrxvt)

I'm trying to switch to mrxvt from XFCE-terminal. The big problem I have is setting the font. I have very little experience with fonts, basically they've just always been something to mess with until I found something that didn't hurt my eyes.
I'm lost as I'm trying to set a font in mrxvt. xlsfonts provides a great many fonts, few with any of the names I'm looking for, in an unfamiliar naming pattern, like (to pick at random) "-sony-fixed-medium-r-normal--16-120-100-100-c-80-jisx0201.1976-0"
- What is the format of the naming, and to what do all the numbers refer?
- I presume the size of the font is specified as part of the name?
- How do I access other fonts, like terminus, that don't appear in the output of xlsfonts?
- What are freetype fonts, and how can I view available ones?
While I'm not font-savvy, in XFCE-terminal I found Monospace size 8 appealing, at least the way gnome-settings-daemon made it look (partially because it wasn't very wide, I tend to dislike wide fonts). Likely, I'm looking for something as near to it as possible. (See below for screenshot example.)
Correct me if I'm wrong, but isn't "Monospace" actually just an alias/pointer for/to the default system monospace font? If so, how can I reference it in mrxvt?
Sorry for the plethora of questions, I'm just trying to figure everything out.
[edit]
Already 4th on Google for "terminus mrxvt" (without the quotes) after just 2.5 hours -- found this while doing some searching on the topic.
Last edited by B-Con (2008-11-09 02:33:06)

Similar Messages

Changing Time Stamp in Receiver Adapter's File Naming Schema.

Hi All,
I am working on a ABAP Proxy to File(FTP with FCC) scenario.
I have a requirement to place the file at FTP with naming schema XSP_SUPPLIER_CC_DD_MM_YYYY.csv.
I have checked many blogs which talks about Dynamic Configuration, but here the naming schema we fetch is from sender file adapter's ASMA(Adapeter Specific Message Attributes).
But in my case sender side is ABAP proxy.
How can I achieve this??
Please suggest.
Regards,
Sachi

Hi,
>> but here the naming schema we fetch is from sender file adapter's ASMA(Adapeter Specific Message Attributes).But in my case sender side is ABAP proxy.
You can use dynamic configuration to not only fetch values from message header you can use it to put values to message heade also.....you can write UDF (code will look like below) and in the UDF you can create string with required filename and concatinate it with the timestamp...
try {
String filename    = "";
String timestamp = "";
DynamicConfiguration conf1 = (DynamicConfiguration) container
    .getTransformationParameters()
    .get(StreamTransformationConstants.DYNAMIC_CONFIGURATION);
DynamicConfigurationKey key1 = DynamicConfigurationKey.create( "http:/"+"/sap.com/xi/XI/System/File","FileName");
filename = "XSP_SUPPLIER_CC_"sourceFiledValue(Supplier)addtimestamphere+".csv";
conf1.put(key1,filename);
return filename;
catch(Exception e)
     String exception = e.toString();
      return exception;
Supplier>UDF>TargetMessage
In the file receiver communication channel check the ASMA property target filename.
Regards,
Priyanka

What naming scheme is the best?

I've imported photos from a hard drive into Aperture. The folders were listed as years. Then with folders of events within each.
On import to Aperture I have ie: 1999 as project. Within this I have many folders such as Fishing, XX birthday, XX birthday, Fun Park, Christmas, etc...
Then another Project 2000 and same as above.
Is there a better naming scheme I should use? In each year Project folder I have Christmas photos. Paintball tournaments. Family get togethers etc..
Some events the same just different years.
Is there a more efficient use of Apeture? Such as making a Christmas Project and then putting all Christmas photos in here? Should I then make year folders of the tournaments or for Christmas?
Not sure of the best use of Aperture to control photos?

For me the best thing is a unique name for every image. I had considered a date naming convention and did not go forward for a few reasons, first off the name was getting too long and I could always look for the date by metadata, so no need.
I figured naming by content presented problems such as what content if an image of a dog also has a cat in it? Skiing in Alta? Skiing or Alta.... Then there is the problem of remembering or finding the last numbered image in the group.
So I ended up with a simple sequence number. I was originally going to go with using letters for the beginning to coincide with a year. A=2001, B=2002 etc. I again threw this out as being redundant because of Metadata. I ended up just going with a letter first with 5 digits following. I edit down to keepers and then simply go back and see the last number I used and then use the following number.
In Aperture I place the images in projects of the shoot in folders of the client then in projects within those folders. I then put alias's in a sequentially numbered folder in groups of 1000.

PSE7: Naming scheme for import without spaces?

Hi all,
just upgraded to photoshop elements 7 (from 2 :-) ) and have a question on the naming schemes available to put imported photos into subfolders named by date: The offered options in the drop down (Photo downloader - Create Subfolders by date) all include spaces between year month and day values. Up to now my format was yyyymmdd (all without spaces) and the newly created folders would not sort properly anymore.
So is there a way to have PSE7 create subfolders based on the date WITHOUT the spaces. I had a trial version of Lightroom 2 and there it is possible, however Lightroom is much to "big" for my needs.
Thanks for any hints,
Peter

Unfortunately, the options you get are the ones you see in the drop-down.

Package naming scheme (ruby-X or X-ruby)

I have a couple of packages that I want to build and both of them follow the scheme X-ruby (mysql-ruby and ncurses-ruby). Should I leave them like this or should I call them ruby-X instead?
The reason I ask is that I thought there might be a standard but actually after looking at "pacman -Ss mysql" I am not sure since there is mysql-python and perl-dbd-mysql.

The naming scheme that Eric is pushing for is <language name>-<package>.
It's just that mysql-python hasn't been renamed to python-mysql yet.

Bypass scenario with a specific file naming schema

Hi,
I am working on a bypass scenario where I pick a file from FTP location with naming conventions SCOS2UVMS_.TXT and place the file at other location with the name USED_Car.TXT.
Now I have to place this file with the Date and Time Stamp as DYYMMDD.THHMMSS.
How can I achieve this?
Thanks & Regards,
Sachi

Hi,
U can bypass the Integration repository steps and pass a file from 1 locatio to other.
U need to configure only the Integration Directory. In all the objects (sender agreement,Receiver determination,Interface determination,Receiver agreement) just give the interface name as dummy and name space also dummy.
Means u just give a arbitary interface name and namespace,which doesn't exist.
Then run the sender communication channel and check in target directory.
This will work fine....
But i think its nt a good idea to use SAP PI, for the just sake of transferring the files from 1 location to other.
U can schedule a batch file,and move the files b/w two locations.
I hope this will solve ur problem..
Babu

What is the naming scheme for Versions

V1_ON_JONAHS VISIT
I get that "V1" is the version number
and that "Jonah's Visit" is the title of my script, but what does the "ON" stand for?

Thanks! That makes sense, now that I know what it means.
Perhaps this would be good information to include on your Help page at https://helpx.adobe.com/story/help/save-versions-document.html or one of the others that talks about saving versions.

New network naming schema in systemd 197

The liveCD was able to use eth0 just fine. I installed the system and configured it but after rebooting, I have not connection and 'ip addr' only shows "1: lo", no eth0.
I have an intel chipset which apparently used e1000e. Which appears to be loaded, but you tell me:
[root@Strongarm ~]# dmesg | grep e1000e
e1000e: Intel (R)_ PRO/1000 Network Driver - 2.0.0-k
e1000e: Copyright(c) 1999 - 2012 Intel Corporation.
e1000e: 0000:00:19.0: setting latency timer to 64
e1000e: 0000:00:19.0: Interrupt Throttling Rate (ints/sec) set to dynamic conservative mode
e1000e: 0000:00:19.0: irq 45 for MSI/MSI-X
e1000e: 0000:00:19.0: eth0 (PCI Express: 2.5GT/s:Width x1) 00:16:76:c8:76:6e
e1000e: 0000:00:19.0: eth0 Intel(R) PRO/1000 Network Connection
e1000e: 0000:00:19.0: eth0: MAC: 6, PHY: 6, PBA No: FFFFFF-OFF
I'm not too sure where to go from here. Please let me know what you need.
# Mod edit: stickying this until is passes through
Last edited by jasonwryan (2013-01-17 23:08:34)

Hey,
I just picked up a new laptop and set up arch on it. I'm having what I consider to be a very strange issue: My network interface names are not always the same on boot. sometimes I get the typical wlan0/eth0/lo set, but just as often I get the following:
enp0s25 no wireless extensions.
wlp3s0 IEEE 802.11abgn ESSID:"censored"
Mode:Managed Frequency:2.432 GHz Access Point: 00:CE:41:50:17:ED
Bit Rate=54 Mb/s Tx-Power=15 dBm
Retry long limit:7 RTS thr:off Fragment thr:off
Power Management:off
Link Quality=51/70 Signal level=-59 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:115 Missed beacon:0
lo no wireless extensions.
Sometimes just one of them has an atypical name.
This is mostly just weird, but it does cause some configuration headaches, so I'd like to fix it. In particular, when the above happens, connman thinks that wlp3s0 isn't wireless, and so I can't use it to choose an ssid (using connmanctl as a frontend).
I found the following in my dmesg:
[ 3.316821] systemd-udevd[133]: renamed network interface wlan0 to wlp3s0
There's a similar line for the other interface. This is probably the culprit, but I have no idea *why* it's happening, or exactly what to do about it.
Here's my lscpi output, in case it is useful:
00:00.0 Host bridge: Intel Corporation Mobile 4 Series Chipset Memory Controller Hub (rev 07)
00:02.0 VGA compatible controller: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller (rev 07)
00:02.1 Display controller: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller (rev 07)
00:03.0 Communication controller: Intel Corporation Mobile 4 Series Chipset MEI Controller (rev 07)
00:03.2 IDE interface: Intel Corporation Mobile 4 Series Chipset PT IDER Controller (rev 07)
00:03.3 Serial controller: Intel Corporation Mobile 4 Series Chipset AMT SOL Redirection (rev 07)
00:19.0 Ethernet controller: Intel Corporation 82567LM Gigabit Network Connection (rev 03)
00:1a.0 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #4 (rev 03)
00:1a.1 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #5 (rev 03)
00:1a.2 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #6 (rev 03)
00:1a.7 USB controller: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #2 (rev 03)
00:1b.0 Audio device: Intel Corporation 82801I (ICH9 Family) HD Audio Controller (rev 03)
00:1c.0 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 1 (rev 03)
00:1c.1 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 2 (rev 03)
00:1d.0 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #1 (rev 03)
00:1d.1 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #2 (rev 03)
00:1d.2 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #3 (rev 03)
00:1d.7 USB controller: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #1 (rev 03)
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev 93)
00:1f.0 ISA bridge: Intel Corporation ICH9M-E LPC Interface Controller (rev 03)
00:1f.2 SATA controller: Intel Corporation 82801IBM/IEM (ICH9M/ICH9M-E) 4 port SATA Controller [AHCI mode] (rev 03)
00:1f.3 SMBus: Intel Corporation 82801I (ICH9 Family) SMBus Controller (rev 03)
03:00.0 Network controller: Intel Corporation PRO/Wireless 5100 AGN [Shiloh] Network Connection
Some advice would be appreciated, thank in advance.

Type1 Postscript fonts

PowerMac G5 Version 10.4.11
MacBook Pro 17' version 10.5.4
Is there any way I can converted my collections of 2,000 fonts to OpenType?
Will the fonts be exactly 100% the same if I converted to OpenType? Please advise me.

A conversion can never be fully transparent for such a complex entity as fonts.
For example, in OpenType, there are two kinds of kerning information (GPOS and kern table). Depending on the conversion method, you may convert the Type 1 kerning into one or both types, but for PostScript-flavored OpenType fonts, kern table-based kerning is not supported. So you will have to use GPOS kerning but there are some applications that don't support it, and with some other applications, only the Western subset of the kerning table will be exposed even if the Type 1 font contained more pairs.
Another example: OpenType fonts contain three different set of linespacing values, one used in most Windows applications, one used in most Mac applications and one used in the typographically sophisticated applications such as Adobe's. There are important technical limitations regarding each of those sets of values. Type 1 fonts only have one set of values and the font driver computes certain aspects of it (i.e. line gap) automatically. When converting, you'd need to make sure that the original Type 1 linespacing values are converted appropriately into each of the sets, but in some cases there may be insolvable conflicts between the values that "should be" there as a result of the conversion and the values that "should be" there due to the technical limitations.
Yet another example: Mac Type 1 fonts typically contain one family name for an arbitrary number of styles, plus a set of style-linking associations. Windows Type 1 fonts typically contain one family name for no more than four styles, and the style-linking associations mimic those styles. OpenType fonts contain both a naming scheme that allows one family name for an arbitrary number of styles (for use in Mac and Adobe applications) and a scheme that allows one family name for no more than four styles (for Windows applications), and also allow style linking. But there are, again, some technical limitations around it, and it is often not possible to automatically map the Type 1 naming schemes into OpenType naming schemes.
These are just three examples, there are more.
In my experience, a fully automated successful conversion from Type 1 to OpenType is quite difficult and requires technical knowledge of the OpenType specification beyond an average user's skills.
Regards,
Adam Twardoch

[SOLVED] Help: My fonts probably got messed up

Hi,
I'm on a fully updated Arch-X86_64/KDE system.
After working flawlessly in the past, I can't use Efax-gtk anymore as I get errors similar to this one:
Warning: Cannot convert string "-*-Helvetica-Medium-R-Normal--*-140-*-*-P-*-ISO8859-1"
to type FontStruct
Warning: Cannot convert string "-*-Helvetica-Medium-R-Normal--*-120-*-*-P-*-ISO8859-1"
to type FontStruct
Warning: Cannot convert string "-*-Helvetica-Medium-R-Normal--*-100-*-*-P-*-ISO8859-1"
to type FontStruct
Warning: Cannot convert string "-*-Helvetica-Bold-R-Normal--*-120-*-*-P-*-ISO8859-1"
to type FontStruct
Warning: Cannot convert string "-*-Helvetica
Since the last time I've successfully used Efax-gtk I've installed several fonts (mainly TTF) from AUR, and I guess, something got wrong.
Below please find several respective terminal outputs.
Please advise.
Thanks
Regards,
Michael Badt
$ fc-list : file
/usr/share/fonts/TTF/DejaVuSerif-BoldItalic.ttf:
/usr/share/fonts/Type1/a010015l.pfb:
/usr/share/fonts/TTF/LiberationMono-BoldItalic.ttf:
/usr/share/fonts/Type1/n019043l.pfb:
/usr/share/fonts/misc/7x13-ISO8859-1.pcf.gz:
/home/miki/.fonts/s/SimpleCLM_Medium.ttf:
/usr/share/fonts/TTF/DejaVuSans-ExtraLight.ttf:
/usr/share/fonts/misc/9x18-ISO8859-1.pcf.gz:
/usr/share/fonts/misc/12x13ja.pcf.gz:
/usr/share/fonts/misc/6x13-ISO8859-1.pcf.gz:
/usr/share/fonts/Type1/n019044l.pfb:
/usr/share/fonts/TTF/DroidSansArmenian.ttf:
/home/miki/.fonts/f/FrankRuehlCLM_MediumOblique.ttf:
/usr/share/fonts/TTF/LiberationSerif-Regular.ttf:
/usr/share/fonts/TTF/DroidSansEthiopic-Regular.ttf:
/home/miki/.fonts/a/AharoniCLM_Bold.pfa:
/usr/share/fonts/misc/6x12-ISO8859-1.pcf.gz:
/usr/share/fonts/TTF/DejaVuSerif-Bold.ttf:
/home/miki/.fonts/m/MiriamMonoCLM_BookOblique.ttf:
/usr/share/fonts/misc/10x20-ISO8859-1.pcf.gz:
/usr/share/fonts/misc/8x13-ISO8859-1.pcf.gz:
/usr/share/fonts/misc/7x13.pcf.gz:
/home/miki/.fonts/a/AharoniCLM_Book.pfa:
/usr/share/fonts/Type1/n022003l.pfb:
/usr/share/fonts/misc/9x18B-ISO8859-1.pcf.gz:
/usr/share/fonts/Type1/n022004l.pfb:
/usr/share/fonts/misc/7x14-ISO8859-1.pcf.gz:
/usr/share/fonts/TTF/DroidSansHebrew-Regular.ttf:
/usr/share/fonts/misc/6x10-ISO8859-1.pcf.gz:
/usr/share/fonts/Type1/n021023l.pfb:
/home/miki/.fonts/e/ElliniaCLM_Light.pfa:
/usr/share/fonts/misc/9x18B.pcf.gz:
/usr/share/fonts/misc/9x15-ISO8859-1.pcf.gz:
/usr/share/fonts/Type1/n021024l.pfb:
/usr/share/fonts/Type1/n019023l.pfb:
/usr/share/fonts/misc/9x15.pcf.gz:
/usr/share/fonts/TTF/DroidSansFallbackLegacy.ttf:
/usr/share/fonts/misc/5x7.pcf.gz:
/usr/share/fonts/Type1/n022023l.pfb:
/usr/share/fonts/Type1/n022024l.pfb:
/home/miki/.fonts/k/KeterYG_Bold.ttf:
/home/miki/.fonts/d/DrugulinCLM_BoldItalic.pfa:
/usr/share/fonts/Type1/n019024l.pfb:
/home/miki/.fonts/d/DavidCLM_Bold.ttf:
/home/miki/.fonts/f/FrankRuehlCLM_BoldOblique.ttf:
/usr/share/fonts/TTF/DejaVuSansCondensed.ttf:
/usr/share/fonts/TTF/DroidKufi-Bold.ttf:
/usr/share/fonts/TTF/LiberationSans-BoldItalic.ttf:
/usr/share/fonts/misc/8x13.pcf.gz:
/usr/share/fonts/misc/cu-pua12.pcf.gz:
/usr/share/fonts/misc/8x13B-ISO8859-1.pcf.gz:
/usr/share/fonts/misc/9x18.pcf.gz:
/usr/share/fonts/TTF/FreeMonoBoldOblique.ttf:
/usr/share/fonts/TTF/DejaVuSansMono-BoldOblique.ttf:
/home/miki/.fonts/n/NachlieliCLM_Bold.pfa:
/usr/share/fonts/TTF/DroidKufi-Regular.ttf:
/usr/share/fonts/TTF/FreeSansOblique.ttf:
/usr/share/fonts/Type1/n021003l.pfb:
/home/miki/.fonts/h/HadasimCLM_Regular.ttf:
/usr/share/fonts/misc/clR6x12-ISO8859-1.pcf.gz:
/usr/share/fonts/misc/9x15B.pcf.gz:
/usr/share/fonts/Type1/n021004l.pfb:
/usr/share/fonts/TTF/FreeSerif.ttf:
/usr/share/fonts/TTF/FreeMonoOblique.ttf:
/usr/share/fonts/TTF/DroidSansHebrew-Bold.ttf:
/usr/share/fonts/TTF/Ubuntu-B.ttf:
/home/miki/.fonts/k/KeterYG_BoldOblique.ttf:
/usr/share/fonts/TTF/Ubuntu-R.ttf:
/usr/share/fonts/Type1/n019003l.pfb:
/usr/share/fonts/TTF/Ubuntu-C.ttf:
/home/miki/.fonts/y/YehudaCLM_Bold.pfa:
/usr/share/fonts/misc/8x13B.pcf.gz:
/home/miki/.fonts/d/DavidCLM_MediumItalic.ttf:
/usr/share/fonts/kanjistrokeorders/KanjiStrokeOrders.ttf:
/usr/share/fonts/misc/9x15B-ISO8859-1.pcf.gz:
/usr/share/fonts/TTF/LiberationSerif-Bold.ttf:
/usr/share/fonts/misc/decsess.pcf.gz:
/usr/share/fonts/misc/6x9-ISO8859-1.pcf.gz:
/usr/share/fonts/TTF/DejaVuSerifCondensed-BoldItalic.ttf:
/home/miki/.fonts/n/NachlieliCLM_BoldOblique.pfa:
/home/miki/.fonts/h/HadasimCLM_Bold.ttf:
/usr/share/fonts/misc/micro.pcf.gz:
/usr/share/fonts/TTF/DejaVuSerif-Italic.ttf:
/usr/share/fonts/Type1/n019004l.pfb:
/home/miki/.fonts/h/HadasimCLM_RegularOblique.ttf:
/usr/share/fonts/TTF/DejaVuSansMono.ttf:
/usr/share/fonts/TTF/DroidSansGeorgian.ttf:
/usr/share/fonts/TTF/DroidSansEthiopic-Bold.ttf:
/home/miki/.fonts/s/SimpleCLM_Bold.ttf:
/usr/share/fonts/misc/6x13B-ISO8859-1.pcf.gz:
/usr/share/fonts/misc/8x16.pcf.gz:
/usr/share/fonts/misc/7x13B-ISO8859-1.pcf.gz:
/usr/share/fonts/TTF/Ubuntu-L.ttf:
/usr/share/fonts/TTF/DroidSansJapanese.ttf:
/usr/share/fonts/misc/6x9.pcf.gz:
/home/miki/.fonts/s/StamSefaradCLM.ttf:
/usr/share/fonts/TTF/LiberationMono-Bold.ttf:
/home/miki/.fonts/s/SimpleCLM_BoldOblique.ttf:
/usr/share/fonts/misc/cursor.pcf.gz:
/home/miki/.fonts/e/ElliniaCLM_BoldItalic.pfa:
/usr/share/fonts/TTF/DejaVuSans-BoldOblique.ttf:
/usr/share/fonts/TTF/DejaVuSansCondensed-Oblique.ttf:
/usr/share/fonts/TTF/DroidNaskh-Regular.ttf:
/home/miki/.fonts/y/YehudaCLM_Light.pfa:
/usr/share/fonts/TTF/DejaVuSans.ttf:
/usr/share/fonts/TTF/FreeSerifBold.ttf:
/usr/share/fonts/misc/clR6x12.pcf.gz:
/home/miki/.fonts/e/ElliniaCLM_Bold.pfa:
/usr/share/fonts/misc/8x13O-ISO8859-1.pcf.gz:
/usr/share/fonts/TTF/DejaVuSansCondensed-Bold.ttf:
/usr/share/fonts/misc/8x13O.pcf.gz:
/usr/share/fonts/misc/7x13O-ISO8859-1.pcf.gz:
/usr/share/fonts/misc/deccurs.pcf.gz:
/usr/share/fonts/misc/7x13B.pcf.gz:
/home/miki/.fonts/n/NachlieliCLM_LightOblique.pfa:
/usr/share/fonts/misc/6x13O-ISO8859-1.pcf.gz:
/usr/share/fonts/TTF/UbuntuMono-BI.ttf:
/usr/share/fonts/TTF/LiberationMono-Italic.ttf:
/home/miki/.fonts/c/CaladingsCLM.pfa:
/usr/share/fonts/TTF/DroidSerif-BoldItalic.ttf:
/usr/share/fonts/misc/7x14.pcf.gz:
/usr/share/fonts/Type1/c059036l.pfb:
/home/miki/.fonts/h/HadasimCLM_BoldOblique.ttf:
/home/miki/.fonts/s/StamAshkenazCLM.ttf:
/usr/share/fonts/TTF/DroidSans-Bold.ttf:
/usr/share/fonts/misc/7x14B-ISO8859-1.pcf.gz:
/usr/share/fonts/Type1/c059033l.pfb:
/usr/share/fonts/TTF/Ubuntu-RI.ttf:
/usr/share/fonts/TTF/DejaVuSansMono-Oblique.ttf:
/usr/share/fonts/misc/10x20.pcf.gz:
/home/miki/.fonts/m/MiriamMonoCLM_Bold.ttf:
/usr/share/fonts/misc/4x6.pcf.gz:
/usr/share/fonts/TTF/FreeSansBoldOblique.ttf:
/usr/share/fonts/TTF/DroidSansTamil-Regular.ttf:
/usr/share/fonts/misc/6x12.pcf.gz:
/usr/share/fonts/TTF/DroidSerif-Regular.ttf:
/home/miki/.fonts/m/MiriamMonoCLM_Book.ttf:
/usr/share/fonts/TTF/FreeMono.ttf:
/home/miki/.fonts/a/AharoniCLM_BookOblique.pfa:
/home/miki/.fonts/m/MiriamMonoCLM_BoldOblique.ttf:
/usr/share/fonts/TTF/FreeSans.ttf:
/usr/share/fonts/TTF/DroidNaskh-Regular-SystemUI.ttf:
/usr/share/fonts/Type1/d050000l.pfb:
/home/miki/.fonts/a/AharoniCLM_BoldOblique.pfa:
/usr/share/fonts/misc/18x18ko.pcf.gz:
/usr/share/fonts/misc/6x13B.pcf.gz:
/usr/share/fonts/TTF/DroidSans.ttf:
/usr/share/fonts/TTF/UbuntuMono-RI.ttf:
/usr/share/fonts/TTF/LiberationSans-Bold.ttf:
/usr/share/fonts/Type1/c059016l.pfb:
/usr/share/fonts/Type1/s050000l.pfb:
/usr/share/fonts/misc/7x14B.pcf.gz:
/usr/share/fonts/TTF/LiberationSerif-Italic.ttf:
/usr/share/fonts/TTF/LiberationSerif-BoldItalic.ttf:
/home/miki/.fonts/d/DavidCLM_BoldItalic.ttf:
/usr/share/fonts/Type1/c059013l.pfb:
/usr/share/fonts/TTF/Ubuntu-BI.ttf:
/usr/share/fonts/misc/7x13O.pcf.gz:
/usr/share/fonts/TTF/DejaVuSerifCondensed-Italic.ttf:
/usr/share/fonts/TTF/FreeSansBold.ttf:
/usr/share/fonts/TTF/Ubuntu-LI.ttf:
/usr/share/fonts/TTF/FreeMonoBold.ttf:
/usr/share/fonts/TTF/DejaVuSans-Bold.ttf:
/home/miki/.fonts/k/KeterYG_MediumOblique.ttf:
/usr/share/fonts/TTF/DejaVuSerif.ttf:
/home/miki/.fonts/s/SimpleCLM_MediumOblique.ttf:
/usr/share/fonts/TTF/FreeSerifItalic.ttf:
/usr/share/fonts/TTF/DejaVuSansMono-Bold.ttf:
/usr/share/fonts/TTF/DroidSansThai.ttf:
/home/miki/.fonts/d/DavidCLM_Medium.ttf:
/usr/share/fonts/TTF/DejaVuSerifCondensed.ttf:
/usr/share/fonts/TTF/LiberationMono-Regular.ttf:
/usr/share/fonts/Type1/b018032l.pfb:
/usr/share/fonts/TTF/DroidNaskh-Bold.ttf:
/usr/share/fonts/misc/5x8.pcf.gz:
/usr/share/fonts/Type1/b018035l.pfb:
/usr/share/fonts/TTF/UbuntuMono-B.ttf:
/usr/share/fonts/misc/5x7-ISO8859-1.pcf.gz:
/usr/share/fonts/misc/6x13O.pcf.gz:
/usr/share/fonts/TTF/UbuntuMono-R.ttf:
/home/miki/.fonts/e/ElliniaCLM_LightItalic.pfa:
/usr/share/fonts/TTF/DroidSansArabic.ttf:
/usr/share/fonts/misc/6x10.pcf.gz:
/usr/share/fonts/TTF/DroidSerif-Bold.ttf:
/usr/share/fonts/TTF/DroidSansDevanagari-Regular.ttf:
/usr/share/fonts/TTF/DejaVuSansCondensed-BoldOblique.ttf:
/usr/share/fonts/Type1/z003034l.pfb:
/usr/share/fonts/misc/12x24.pcf.gz:
/usr/share/fonts/TTF/DroidSansFallback.ttf:
/usr/share/fonts/misc/18x18ja.pcf.gz:
/home/miki/.fonts/f/FrankRuehlCLM_Bold.ttf:
/usr/share/fonts/TTF/LiberationSans-Italic.ttf:
/home/miki/.fonts/m/MiriamCLM_Book.ttf:
/usr/share/fonts/Type1/b018012l.pfb:
/usr/share/fonts/Type1/p052004l.pfb:
/usr/share/fonts/misc/cu12.pcf.gz:
/home/miki/.fonts/m/MiriamCLM_Bold.ttf:
/usr/share/fonts/TTF/DroidSerif-Italic.ttf:
/usr/share/fonts/Type1/b018015l.pfb:
/usr/share/fonts/misc/4x6-ISO8859-1.pcf.gz:
/usr/share/fonts/Type1/a010033l.pfb:
/usr/share/fonts/TTF/DroidSansTamil-Bold.ttf:
/usr/share/fonts/Type1/p052003l.pfb:
/usr/share/fonts/Type1/a010035l.pfb:
/usr/share/fonts/TTF/LiberationSans-Regular.ttf:
/home/miki/.fonts/n/NachlieliCLM_Light.pfa:
/usr/share/fonts/TTF/DejaVuSerifCondensed-Bold.ttf:
/usr/share/fonts/Type1/n019063l.pfb:
/usr/share/fonts/misc/5x8-ISO8859-1.pcf.gz:
/usr/share/fonts/misc/6x13.pcf.gz:
/home/miki/.fonts/d/DrugulinCLM_Bold.pfa:
/usr/share/fonts/misc/arabic24.pcf.gz:
/usr/share/fonts/Type1/n019064l.pfb:
/usr/share/fonts/misc/cu-alt12.pcf.gz:
/home/miki/.fonts/f/FrankRuehlCLM_Medium.ttf:
/usr/share/fonts/TTF/DroidSansMono.ttf:
/usr/share/fonts/Type1/p052024l.pfb:
/usr/share/fonts/TTF/FreeSerifBoldItalic.ttf:
/usr/share/fonts/TTF/DejaVuSans-Oblique.ttf:
/usr/share/fonts/Type1/a010013l.pfb:
/usr/share/fonts/TTF/DroidSansFallbackFull.ttf:
/home/miki/.fonts/k/KeterYG_Medium.ttf:
/usr/share/fonts/Type1/p052023l.pfb:
And here is probably the problem (that's AFTER I've ran mkfontdir, as root, in both directories, as suggested)
are/fonts/Type1/p052023l.pfb:
miki ~ $ grep /fonts /var/log/Xorg.0.log
[ 16.143] (WW) The directory "/usr/share/fonts/OTF/" does not exist.
[ 16.153] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/100dpi/".
[ 16.153] (Run 'mkfontdir' on "/usr/share/fonts/100dpi/").
[ 16.154] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/75dpi/".
[ 16.154] (Run 'mkfontdir' on "/usr/share/fonts/75dpi/").
/usr/share/fonts/misc/,
/usr/share/fonts/TTF/,
/usr/share/fonts/Type1/
$ xset q
Keyboard Control:
auto repeat: on key click percent: 0 LED mask: 00000000
XKB indicators:
00: Caps Lock: off 01: Num Lock: off 02: Scroll Lock: off
03: Compose: off 04: Kana: off 05: Sleep: off
06: Suspend: off 07: Mute: off 08: Misc: off
09: Mail: off 10: Charging: off 11: Shift Lock: off
12: Group 2: off 13: Mouse Keys: off
auto repeat delay: 660 repeat rate: 25
auto repeating keys: 00ffffffdffffbbf
fadfffefffedffff
9fffffffffffffff
fff7ffffffffffff
bell percent: 50 bell pitch: 400 bell duration: 100
Pointer Control:
acceleration: 20/10 threshold: 4
Screen Saver:
prefer blanking: yes allow exposures: yes
timeout: 0 cycle: 600
Colors:
default colormap: 0x20 BlackPixel: 0x0 WhitePixel: 0xffffff
Font Path:
/usr/share/fonts/misc/,/usr/share/fonts/TTF/,/usr/share/fonts/Type1/,built-ins,/home/miki/.fonts
DPMS (Energy Star):
Standby: 600 Suspend: 900 Off: 1200
DPMS is Enabled
Monitor is On
and my full fonts tree
miki /usr/share/fonts $ tree
├── 100dpi
│   └── fonts.alias
├── 75dpi
│   └── fonts.alias
├── TTF
│   ├── DejaVuSans-Bold.ttf
│   ├── DejaVuSans-BoldOblique.ttf
│   ├── DejaVuSans-ExtraLight.ttf
│   ├── DejaVuSans-Oblique.ttf
│   ├── DejaVuSans.ttf
│   ├── DejaVuSansCondensed-Bold.ttf
│   ├── DejaVuSansCondensed-BoldOblique.ttf
│   ├── DejaVuSansCondensed-Oblique.ttf
│   ├── DejaVuSansCondensed.ttf
│   ├── DejaVuSansMono-Bold.ttf
│   ├── DejaVuSansMono-BoldOblique.ttf
│   ├── DejaVuSansMono-Oblique.ttf
│   ├── DejaVuSansMono.ttf
│   ├── DejaVuSerif-Bold.ttf
│   ├── DejaVuSerif-BoldItalic.ttf
│   ├── DejaVuSerif-Italic.ttf
│   ├── DejaVuSerif.ttf
│   ├── DejaVuSerifCondensed-Bold.ttf
│   ├── DejaVuSerifCondensed-BoldItalic.ttf
│   ├── DejaVuSerifCondensed-Italic.ttf
│   ├── DejaVuSerifCondensed.ttf
│   ├── DroidKufi-Bold.ttf
│   ├── DroidKufi-Regular.ttf
│   ├── DroidNaskh-Bold.ttf
│   ├── DroidNaskh-Regular-SystemUI.ttf
│   ├── DroidNaskh-Regular.ttf
│   ├── DroidSans-Bold.ttf
│   ├── DroidSans.ttf
│   ├── DroidSansArabic.ttf
│   ├── DroidSansArmenian.ttf
│   ├── DroidSansDevanagari-Regular.ttf
│   ├── DroidSansEthiopic-Bold.ttf
│   ├── DroidSansEthiopic-Regular.ttf
│   ├── DroidSansFallback.ttf
│   ├── DroidSansFallbackFull.ttf
│   ├── DroidSansFallbackLegacy.ttf
│   ├── DroidSansGeorgian.ttf
│   ├── DroidSansHebrew-Bold.ttf
│   ├── DroidSansHebrew-Regular.ttf
│   ├── DroidSansJapanese.ttf
│   ├── DroidSansMono.ttf
│   ├── DroidSansTamil-Bold.ttf
│   ├── DroidSansTamil-Regular.ttf
│   ├── DroidSansThai.ttf
│   ├── DroidSerif-Bold.ttf
│   ├── DroidSerif-BoldItalic.ttf
│   ├── DroidSerif-Italic.ttf
│   ├── DroidSerif-Regular.ttf
│   ├── FreeMono.ttf
│   ├── FreeMonoBold.ttf
│   ├── FreeMonoBoldOblique.ttf
│   ├── FreeMonoOblique.ttf
│   ├── FreeSans.ttf
│   ├── FreeSansBold.ttf
│   ├── FreeSansBoldOblique.ttf
│   ├── FreeSansOblique.ttf
│   ├── FreeSerif.ttf
│   ├── FreeSerifBold.ttf
│   ├── FreeSerifBoldItalic.ttf
│   ├── FreeSerifItalic.ttf
│   ├── LiberationMono-Bold.ttf
│   ├── LiberationMono-BoldItalic.ttf
│   ├── LiberationMono-Italic.ttf
│   ├── LiberationMono-Regular.ttf
│   ├── LiberationSans-Bold.ttf
│   ├── LiberationSans-BoldItalic.ttf
│   ├── LiberationSans-Italic.ttf
│   ├── LiberationSans-Regular.ttf
│   ├── LiberationSerif-Bold.ttf
│   ├── LiberationSerif-BoldItalic.ttf
│   ├── LiberationSerif-Italic.ttf
│   ├── LiberationSerif-Regular.ttf
│   ├── Ubuntu-B.ttf
│   ├── Ubuntu-BI.ttf
│   ├── Ubuntu-C.ttf
│   ├── Ubuntu-L.ttf
│   ├── Ubuntu-LI.ttf
│   ├── Ubuntu-R.ttf
│   ├── Ubuntu-RI.ttf
│   ├── UbuntuMono-B.ttf
│   ├── UbuntuMono-BI.ttf
│   ├── UbuntuMono-R.ttf
│   ├── UbuntuMono-RI.ttf
│   ├── fonts.dir
│   └── fonts.scale
├── Type1
│   ├── a010013l.afm
│   ├── a010013l.pfb
│   ├── a010013l.pfm
│   ├── a010015l.afm
│   ├── a010015l.pfb
│   ├── a010015l.pfm
│   ├── a010033l.afm
│   ├── a010033l.pfb
│   ├── a010033l.pfm
│   ├── a010035l.afm
│   ├── a010035l.pfb
│   ├── a010035l.pfm
│   ├── b018012l.afm
│   ├── b018012l.pfb
│   ├── b018012l.pfm
│   ├── b018015l.afm
│   ├── b018015l.pfb
│   ├── b018015l.pfm
│   ├── b018032l.afm
│   ├── b018032l.pfb
│   ├── b018032l.pfm
│   ├── b018035l.afm
│   ├── b018035l.pfb
│   ├── b018035l.pfm
│   ├── c059013l.afm
│   ├── c059013l.pfb
│   ├── c059013l.pfm
│   ├── c059016l.afm
│   ├── c059016l.pfb
│   ├── c059016l.pfm
│   ├── c059033l.afm
│   ├── c059033l.pfb
│   ├── c059033l.pfm
│   ├── c059036l.afm
│   ├── c059036l.pfb
│   ├── c059036l.pfm
│   ├── d050000l.afm
│   ├── d050000l.pfb
│   ├── d050000l.pfm
│   ├── fonts.dir
│   ├── fonts.scale
│   ├── n019003l.afm
│   ├── n019003l.pfb
│   ├── n019003l.pfm
│   ├── n019004l.afm
│   ├── n019004l.pfb
│   ├── n019004l.pfm
│   ├── n019023l.afm
│   ├── n019023l.pfb
│   ├── n019023l.pfm
│   ├── n019024l.afm
│   ├── n019024l.pfb
│   ├── n019024l.pfm
│   ├── n019043l.afm
│   ├── n019043l.pfb
│   ├── n019043l.pfm
│   ├── n019044l.afm
│   ├── n019044l.pfb
│   ├── n019044l.pfm
│   ├── n019063l.afm
│   ├── n019063l.pfb
│   ├── n019063l.pfm
│   ├── n019064l.afm
│   ├── n019064l.pfb
│   ├── n019064l.pfm
│   ├── n021003l.afm
│   ├── n021003l.pfb
│   ├── n021003l.pfm
│   ├── n021004l.afm
│   ├── n021004l.pfb
│   ├── n021004l.pfm
│   ├── n021023l.afm
│   ├── n021023l.pfb
│   ├── n021023l.pfm
│   ├── n021024l.afm
│   ├── n021024l.pfb
│   ├── n021024l.pfm
│   ├── n022003l.afm
│   ├── n022003l.pfb
│   ├── n022003l.pfm
│   ├── n022004l.afm
│   ├── n022004l.pfb
│   ├── n022004l.pfm
│   ├── n022023l.afm
│   ├── n022023l.pfb
│   ├── n022023l.pfm
│   ├── n022024l.afm
│   ├── n022024l.pfb
│   ├── n022024l.pfm
│   ├── p052003l.afm
│   ├── p052003l.pfb
│   ├── p052003l.pfm
│   ├── p052004l.afm
│   ├── p052004l.pfb
│   ├── p052004l.pfm
│   ├── p052023l.afm
│   ├── p052023l.pfb
│   ├── p052023l.pfm
│   ├── p052024l.afm
│   ├── p052024l.pfb
│   ├── p052024l.pfm
│   ├── s050000l.afm
│   ├── s050000l.pfb
│   ├── s050000l.pfm
│   ├── z003034l.afm
│   ├── z003034l.pfb
│   └── z003034l.pfm
├── cyrillic
│   └── fonts.alias
├── encodings
│   ├── adobe-dingbats.enc.gz
│   ├── adobe-standard.enc.gz
│   ├── adobe-symbol.enc.gz
│   ├── armscii-8.enc.gz
│   ├── ascii-0.enc.gz
│   ├── dec-special.enc.gz
│   ├── encodings.dir
│   ├── ibm-cp437.enc.gz
│   ├── ibm-cp850.enc.gz
│   ├── ibm-cp852.enc.gz
│   ├── ibm-cp866.enc.gz
│   ├── iso8859-11.enc.gz
│   ├── iso8859-13.enc.gz
│   ├── iso8859-16.enc.gz
│   ├── iso8859-6.16.enc.gz
│   ├── iso8859-6.8x.enc.gz
│   ├── large
│   │   ├── big5.eten-0.enc.gz
│   │   ├── big5hkscs-0.enc.gz
│   │   ├── cns11643-1.enc.gz
│   │   ├── cns11643-2.enc.gz
│   │   ├── cns11643-3.enc.gz
│   │   ├── encodings.dir
│   │   ├── gb18030-0.enc.gz
│   │   ├── gb18030.2000-0.enc.gz
│   │   ├── gb18030.2000-1.enc.gz
│   │   ├── gb2312.1980-0.enc.gz
│   │   ├── gbk-0.enc.gz
│   │   ├── jisx0201.1976-0.enc.gz
│   │   ├── jisx0208.1990-0.enc.gz
│   │   ├── jisx0212.1990-0.enc.gz
│   │   ├── ksc5601.1987-0.enc.gz
│   │   ├── ksc5601.1992-3.enc.gz
│   │   └── sun.unicode.india-0.enc.gz
│   ├── microsoft-cp1250.enc.gz
│   ├── microsoft-cp1251.enc.gz
│   ├── microsoft-cp1252.enc.gz
│   ├── microsoft-cp1253.enc.gz
│   ├── microsoft-cp1254.enc.gz
│   ├── microsoft-cp1255.enc.gz
│   ├── microsoft-cp1256.enc.gz
│   ├── microsoft-cp1257.enc.gz
│   ├── microsoft-cp1258.enc.gz
│   ├── microsoft-win3.1.enc.gz
│   ├── mulearabic-0.enc.gz
│   ├── mulearabic-1.enc.gz
│   ├── mulearabic-2.enc.gz
│   ├── mulelao-1.enc.gz
│   ├── suneu-greek.enc.gz
│   ├── tcvn-0.enc.gz
│   ├── tis620-2.enc.gz
│   └── viscii1.1-1.enc.gz
├── kanjistrokeorders
│   └── KanjiStrokeOrders.ttf
├── misc
│   ├── 10x20-ISO8859-1.pcf.gz
│   ├── 10x20-ISO8859-10.pcf.gz
│   ├── 10x20-ISO8859-11.pcf.gz
│   ├── 10x20-ISO8859-13.pcf.gz
│   ├── 10x20-ISO8859-14.pcf.gz
│   ├── 10x20-ISO8859-15.pcf.gz
│   ├── 10x20-ISO8859-16.pcf.gz
│   ├── 10x20-ISO8859-2.pcf.gz
│   ├── 10x20-ISO8859-3.pcf.gz
│   ├── 10x20-ISO8859-4.pcf.gz
│   ├── 10x20-ISO8859-5.pcf.gz
│   ├── 10x20-ISO8859-7.pcf.gz
│   ├── 10x20-ISO8859-8.pcf.gz
│   ├── 10x20-ISO8859-9.pcf.gz
│   ├── 10x20-KOI8-R.pcf.gz
│   ├── 10x20.pcf.gz
│   ├── 12x13ja.pcf.gz
│   ├── 12x24.pcf.gz
│   ├── 12x24rk.pcf.gz
│   ├── 18x18ja.pcf.gz
│   ├── 18x18ko.pcf.gz
│   ├── 4x6-ISO8859-1.pcf.gz
│   ├── 4x6-ISO8859-10.pcf.gz
│   ├── 4x6-ISO8859-13.pcf.gz
│   ├── 4x6-ISO8859-14.pcf.gz
│   ├── 4x6-ISO8859-15.pcf.gz
│   ├── 4x6-ISO8859-16.pcf.gz
│   ├── 4x6-ISO8859-2.pcf.gz
│   ├── 4x6-ISO8859-3.pcf.gz
│   ├── 4x6-ISO8859-4.pcf.gz
│   ├── 4x6-ISO8859-5.pcf.gz
│   ├── 4x6-ISO8859-7.pcf.gz
│   ├── 4x6-ISO8859-8.pcf.gz
│   ├── 4x6-ISO8859-9.pcf.gz
│   ├── 4x6-KOI8-R.pcf.gz
│   ├── 4x6.pcf.gz
│   ├── 5x7-ISO8859-1.pcf.gz
│   ├── 5x7-ISO8859-10.pcf.gz
│   ├── 5x7-ISO8859-13.pcf.gz
│   ├── 5x7-ISO8859-14.pcf.gz
│   ├── 5x7-ISO8859-15.pcf.gz
│   ├── 5x7-ISO8859-16.pcf.gz
│   ├── 5x7-ISO8859-2.pcf.gz
│   ├── 5x7-ISO8859-3.pcf.gz
│   ├── 5x7-ISO8859-4.pcf.gz
│   ├── 5x7-ISO8859-5.pcf.gz
│   ├── 5x7-ISO8859-7.pcf.gz
│   ├── 5x7-ISO8859-8.pcf.gz
│   ├── 5x7-ISO8859-9.pcf.gz
│   ├── 5x7-KOI8-R.pcf.gz
│   ├── 5x7.pcf.gz
│   ├── 5x8-ISO8859-1.pcf.gz
│   ├── 5x8-ISO8859-10.pcf.gz
│   ├── 5x8-ISO8859-13.pcf.gz
│   ├── 5x8-ISO8859-14.pcf.gz
│   ├── 5x8-ISO8859-15.pcf.gz
│   ├── 5x8-ISO8859-16.pcf.gz
│   ├── 5x8-ISO8859-2.pcf.gz
│   ├── 5x8-ISO8859-3.pcf.gz
│   ├── 5x8-ISO8859-4.pcf.gz
│   ├── 5x8-ISO8859-5.pcf.gz
│   ├── 5x8-ISO8859-7.pcf.gz
│   ├── 5x8-ISO8859-8.pcf.gz
│   ├── 5x8-ISO8859-9.pcf.gz
│   ├── 5x8-KOI8-R.pcf.gz
│   ├── 5x8.pcf.gz
│   ├── 6x10-ISO8859-1.pcf.gz
│   ├── 6x10-ISO8859-10.pcf.gz
│   ├── 6x10-ISO8859-13.pcf.gz
│   ├── 6x10-ISO8859-14.pcf.gz
│   ├── 6x10-ISO8859-15.pcf.gz
│   ├── 6x10-ISO8859-16.pcf.gz
│   ├── 6x10-ISO8859-2.pcf.gz
│   ├── 6x10-ISO8859-3.pcf.gz
│   ├── 6x10-ISO8859-4.pcf.gz
│   ├── 6x10-ISO8859-5.pcf.gz
│   ├── 6x10-ISO8859-7.pcf.gz
│   ├── 6x10-ISO8859-8.pcf.gz
│   ├── 6x10-ISO8859-9.pcf.gz
│   ├── 6x10-KOI8-R.pcf.gz
│   ├── 6x10.pcf.gz
│   ├── 6x12-ISO8859-1.pcf.gz
│   ├── 6x12-ISO8859-10.pcf.gz
│   ├── 6x12-ISO8859-13.pcf.gz
│   ├── 6x12-ISO8859-14.pcf.gz
│   ├── 6x12-ISO8859-15.pcf.gz
│   ├── 6x12-ISO8859-16.pcf.gz
│   ├── 6x12-ISO8859-2.pcf.gz
│   ├── 6x12-ISO8859-3.pcf.gz
│   ├── 6x12-ISO8859-4.pcf.gz
│   ├── 6x12-ISO8859-5.pcf.gz
│   ├── 6x12-ISO8859-7.pcf.gz
│   ├── 6x12-ISO8859-8.pcf.gz
│   ├── 6x12-ISO8859-9.pcf.gz
│   ├── 6x12-KOI8-R.pcf.gz
│   ├── 6x12.pcf.gz
│   ├── 6x13-ISO8859-1.pcf.gz
│   ├── 6x13-ISO8859-10.pcf.gz
│   ├── 6x13-ISO8859-11.pcf.gz
│   ├── 6x13-ISO8859-13.pcf.gz
│   ├── 6x13-ISO8859-14.pcf.gz
│   ├── 6x13-ISO8859-15.pcf.gz
│   ├── 6x13-ISO8859-16.pcf.gz
│   ├── 6x13-ISO8859-2.pcf.gz
│   ├── 6x13-ISO8859-3.pcf.gz
│   ├── 6x13-ISO8859-4.pcf.gz
│   ├── 6x13-ISO8859-5.pcf.gz
│   ├── 6x13-ISO8859-7.pcf.gz
│   ├── 6x13-ISO8859-8.pcf.gz
│   ├── 6x13-ISO8859-9.pcf.gz
│   ├── 6x13-KOI8-R.pcf.gz
│   ├── 6x13.pcf.gz
│   ├── 6x13B-ISO8859-1.pcf.gz
│   ├── 6x13B-ISO8859-10.pcf.gz
│   ├── 6x13B-ISO8859-13.pcf.gz
│   ├── 6x13B-ISO8859-14.pcf.gz
│   ├── 6x13B-ISO8859-15.pcf.gz
│   ├── 6x13B-ISO8859-16.pcf.gz
│   ├── 6x13B-ISO8859-2.pcf.gz
│   ├── 6x13B-ISO8859-3.pcf.gz
│   ├── 6x13B-ISO8859-4.pcf.gz
│   ├── 6x13B-ISO8859-5.pcf.gz
│   ├── 6x13B-ISO8859-7.pcf.gz
│   ├── 6x13B-ISO8859-8.pcf.gz
│   ├── 6x13B-ISO8859-9.pcf.gz
│   ├── 6x13B.pcf.gz
│   ├── 6x13O-ISO8859-1.pcf.gz
│   ├── 6x13O-ISO8859-10.pcf.gz
│   ├── 6x13O-ISO8859-13.pcf.gz
│   ├── 6x13O-ISO8859-14.pcf.gz
│   ├── 6x13O-ISO8859-15.pcf.gz
│   ├── 6x13O-ISO8859-16.pcf.gz
│   ├── 6x13O-ISO8859-2.pcf.gz
│   ├── 6x13O-ISO8859-3.pcf.gz
│   ├── 6x13O-ISO8859-4.pcf.gz
│   ├── 6x13O-ISO8859-5.pcf.gz
│   ├── 6x13O-ISO8859-7.pcf.gz
│   ├── 6x13O-ISO8859-9.pcf.gz
│   ├── 6x13O.pcf.gz
│   ├── 6x9-ISO8859-1.pcf.gz
│   ├── 6x9-ISO8859-10.pcf.gz
│   ├── 6x9-ISO8859-13.pcf.gz
│   ├── 6x9-ISO8859-14.pcf.gz
│   ├── 6x9-ISO8859-15.pcf.gz
│   ├── 6x9-ISO8859-16.pcf.gz
│   ├── 6x9-ISO8859-2.pcf.gz
│   ├── 6x9-ISO8859-3.pcf.gz
│   ├── 6x9-ISO8859-4.pcf.gz
│   ├── 6x9-ISO8859-5.pcf.gz
│   ├── 6x9-ISO8859-7.pcf.gz
│   ├── 6x9-ISO8859-8.pcf.gz
│   ├── 6x9-ISO8859-9.pcf.gz
│   ├── 6x9-KOI8-R.pcf.gz
│   ├── 6x9.pcf.gz
│   ├── 7x13-ISO8859-1.pcf.gz
│   ├── 7x13-ISO8859-10.pcf.gz
│   ├── 7x13-ISO8859-11.pcf.gz
│   ├── 7x13-ISO8859-13.pcf.gz
│   ├── 7x13-ISO8859-14.pcf.gz
│   ├── 7x13-ISO8859-15.pcf.gz
│   ├── 7x13-ISO8859-16.pcf.gz
│   ├── 7x13-ISO8859-2.pcf.gz
│   ├── 7x13-ISO8859-3.pcf.gz
│   ├── 7x13-ISO8859-4.pcf.gz
│   ├── 7x13-ISO8859-5.pcf.gz
│   ├── 7x13-ISO8859-7.pcf.gz
│   ├── 7x13-ISO8859-8.pcf.gz
│   ├── 7x13-ISO8859-9.pcf.gz
│   ├── 7x13-KOI8-R.pcf.gz
│   ├── 7x13.pcf.gz
│   ├── 7x13B-ISO8859-1.pcf.gz
│   ├── 7x13B-ISO8859-10.pcf.gz
│   ├── 7x13B-ISO8859-11.pcf.gz
│   ├── 7x13B-ISO8859-13.pcf.gz
│   ├── 7x13B-ISO8859-14.pcf.gz
│   ├── 7x13B-ISO8859-15.pcf.gz
│   ├── 7x13B-ISO8859-16.pcf.gz
│   ├── 7x13B-ISO8859-2.pcf.gz
│   ├── 7x13B-ISO8859-3.pcf.gz
│   ├── 7x13B-ISO8859-4.pcf.gz
│   ├── 7x13B-ISO8859-5.pcf.gz
│   ├── 7x13B-ISO8859-7.pcf.gz
│   ├── 7x13B-ISO8859-8.pcf.gz
│   ├── 7x13B-ISO8859-9.pcf.gz
│   ├── 7x13B.pcf.gz
│   ├── 7x13O-ISO8859-1.pcf.gz
│   ├── 7x13O-ISO8859-10.pcf.gz
│   ├── 7x13O-ISO8859-11.pcf.gz
│   ├── 7x13O-ISO8859-13.pcf.gz
│   ├── 7x13O-ISO8859-14.pcf.gz
│   ├── 7x13O-ISO8859-15.pcf.gz
│   ├── 7x13O-ISO8859-16.pcf.gz
│   ├── 7x13O-ISO8859-2.pcf.gz
│   ├── 7x13O-ISO8859-3.pcf.gz
│   ├── 7x13O-ISO8859-4.pcf.gz
│   ├── 7x13O-ISO8859-5.pcf.gz
│   ├── 7x13O-ISO8859-7.pcf.gz
│   ├── 7x13O-ISO8859-9.pcf.gz
│   ├── 7x13O.pcf.gz
│   ├── 7x14-ISO8859-1.pcf.gz
│   ├── 7x14-ISO8859-10.pcf.gz
│   ├── 7x14-ISO8859-11.pcf.gz
│   ├── 7x14-ISO8859-13.pcf.gz
│   ├── 7x14-ISO8859-14.pcf.gz
│   ├── 7x14-ISO8859-15.pcf.gz
│   ├── 7x14-ISO8859-16.pcf.gz
│   ├── 7x14-ISO8859-2.pcf.gz
│   ├── 7x14-ISO8859-3.pcf.gz
│   ├── 7x14-ISO8859-4.pcf.gz
│   ├── 7x14-ISO8859-5.pcf.gz
│   ├── 7x14-ISO8859-7.pcf.gz
│   ├── 7x14-ISO8859-8.pcf.gz
│   ├── 7x14-ISO8859-9.pcf.gz
│   ├── 7x14-JISX0201.1976-0.pcf.gz
│   ├── 7x14-KOI8-R.pcf.gz
│   ├── 7x14.pcf.gz
│   ├── 7x14B-ISO8859-1.pcf.gz
│   ├── 7x14B-ISO8859-10.pcf.gz
│   ├── 7x14B-ISO8859-11.pcf.gz
│   ├── 7x14B-ISO8859-13.pcf.gz
│   ├── 7x14B-ISO8859-14.pcf.gz
│   ├── 7x14B-ISO8859-15.pcf.gz
│   ├── 7x14B-ISO8859-16.pcf.gz
│   ├── 7x14B-ISO8859-2.pcf.gz
│   ├── 7x14B-ISO8859-3.pcf.gz
│   ├── 7x14B-ISO8859-4.pcf.gz
│   ├── 7x14B-ISO8859-5.pcf.gz
│   ├── 7x14B-ISO8859-7.pcf.gz
│   ├── 7x14B-ISO8859-8.pcf.gz
│   ├── 7x14B-ISO8859-9.pcf.gz
│   ├── 7x14B.pcf.gz
│   ├── 8x13-ISO8859-1.pcf.gz
│   ├── 8x13-ISO8859-10.pcf.gz
│   ├── 8x13-ISO8859-13.pcf.gz
│   ├── 8x13-ISO8859-14.pcf.gz
│   ├── 8x13-ISO8859-15.pcf.gz
│   ├── 8x13-ISO8859-16.pcf.gz
│   ├── 8x13-ISO8859-2.pcf.gz
│   ├── 8x13-ISO8859-3.pcf.gz
│   ├── 8x13-ISO8859-4.pcf.gz
│   ├── 8x13-ISO8859-5.pcf.gz
│   ├── 8x13-ISO8859-7.pcf.gz
│   ├── 8x13-ISO8859-8.pcf.gz
│   ├── 8x13-ISO8859-9.pcf.gz
│   ├── 8x13-KOI8-R.pcf.gz
│   ├── 8x13.pcf.gz
│   ├── 8x13B-ISO8859-1.pcf.gz
│   ├── 8x13B-ISO8859-10.pcf.gz
│   ├── 8x13B-ISO8859-13.pcf.gz
│   ├── 8x13B-ISO8859-14.pcf.gz
│   ├── 8x13B-ISO8859-15.pcf.gz
│   ├── 8x13B-ISO8859-16.pcf.gz
│   ├── 8x13B-ISO8859-2.pcf.gz
│   ├── 8x13B-ISO8859-3.pcf.gz
│   ├── 8x13B-ISO8859-4.pcf.gz
│   ├── 8x13B-ISO8859-5.pcf.gz
│   ├── 8x13B-ISO8859-7.pcf.gz
│   ├── 8x13B-ISO8859-8.pcf.gz
│   ├── 8x13B-ISO8859-9.pcf.gz
│   ├── 8x13B.pcf.gz
│   ├── 8x13O-ISO8859-1.pcf.gz
│   ├── 8x13O-ISO8859-10.pcf.gz
│   ├── 8x13O-ISO8859-13.pcf.gz
│   ├── 8x13O-ISO8859-14.pcf.gz
│   ├── 8x13O-ISO8859-15.pcf.gz
│   ├── 8x13O-ISO8859-16.pcf.gz
│   ├── 8x13O-ISO8859-2.pcf.gz
│   ├── 8x13O-ISO8859-3.pcf.gz
│   ├── 8x13O-ISO8859-4.pcf.gz
│   ├── 8x13O-ISO8859-5.pcf.gz
│   ├── 8x13O-ISO8859-7.pcf.gz
│   ├── 8x13O-ISO8859-9.pcf.gz
│   ├── 8x13O.pcf.gz
│   ├── 8x16.pcf.gz
│   ├── 8x16rk.pcf.gz
│   ├── 9x15-ISO8859-1.pcf.gz
│   ├── 9x15-ISO8859-10.pcf.gz
│   ├── 9x15-ISO8859-11.pcf.gz
│   ├── 9x15-ISO8859-13.pcf.gz
│   ├── 9x15-ISO8859-14.pcf.gz
│   ├── 9x15-ISO8859-15.pcf.gz
│   ├── 9x15-ISO8859-16.pcf.gz
│   ├── 9x15-ISO8859-2.pcf.gz
│   ├── 9x15-ISO8859-3.pcf.gz
│   ├── 9x15-ISO8859-4.pcf.gz
│   ├── 9x15-ISO8859-5.pcf.gz
│   ├── 9x15-ISO8859-7.pcf.gz
│   ├── 9x15-ISO8859-8.pcf.gz
│   ├── 9x15-ISO8859-9.pcf.gz
│   ├── 9x15-KOI8-R.pcf.gz
│   ├── 9x15.pcf.gz
│   ├── 9x15B-ISO8859-1.pcf.gz
│   ├── 9x15B-ISO8859-10.pcf.gz
│   ├── 9x15B-ISO8859-11.pcf.gz
│   ├── 9x15B-ISO8859-13.pcf.gz
│   ├── 9x15B-ISO8859-14.pcf.gz
│   ├── 9x15B-ISO8859-15.pcf.gz
│   ├── 9x15B-ISO8859-16.pcf.gz
│   ├── 9x15B-ISO8859-2.pcf.gz
│   ├── 9x15B-ISO8859-3.pcf.gz
│   ├── 9x15B-ISO8859-4.pcf.gz
│   ├── 9x15B-ISO8859-5.pcf.gz
│   ├── 9x15B-ISO8859-7.pcf.gz
│   ├── 9x15B-ISO8859-8.pcf.gz
│   ├── 9x15B-ISO8859-9.pcf.gz
│   ├── 9x15B.pcf.gz
│   ├── 9x18-ISO8859-1.pcf.gz
│   ├── 9x18-ISO8859-10.pcf.gz
│   ├── 9x18-ISO8859-11.pcf.gz
│   ├── 9x18-ISO8859-13.pcf.gz
│   ├── 9x18-ISO8859-14.pcf.gz
│   ├── 9x18-ISO8859-15.pcf.gz
│   ├── 9x18-ISO8859-16.pcf.gz
│   ├── 9x18-ISO8859-2.pcf.gz
│   ├── 9x18-ISO8859-3.pcf.gz
│   ├── 9x18-ISO8859-4.pcf.gz
│   ├── 9x18-ISO8859-5.pcf.gz
│   ├── 9x18-ISO8859-7.pcf.gz
│   ├── 9x18-ISO8859-8.pcf.gz
│   ├── 9x18-ISO8859-9.pcf.gz
│   ├── 9x18-KOI8-R.pcf.gz
│   ├── 9x18.pcf.gz
│   ├── 9x18B-ISO8859-1.pcf.gz
│   ├── 9x18B-ISO8859-10.pcf.gz
│   ├── 9x18B-ISO8859-13.pcf.gz
│   ├── 9x18B-ISO8859-14.pcf.gz
│   ├── 9x18B-ISO8859-15.pcf.gz
│   ├── 9x18B-ISO8859-16.pcf.gz
│   ├── 9x18B-ISO8859-2.pcf.gz
│   ├── 9x18B-ISO8859-3.pcf.gz
│   ├── 9x18B-ISO8859-4.pcf.gz
│   ├── 9x18B-ISO8859-5.pcf.gz
│   ├── 9x18B-ISO8859-7.pcf.gz
│   ├── 9x18B-ISO8859-8.pcf.gz
│   ├── 9x18B-ISO8859-9.pcf.gz
│   ├── 9x18B.pcf.gz
│   ├── arabic24.pcf.gz
│   ├── clB6x10.pcf.gz
│   ├── clB6x12.pcf.gz
│   ├── clB8x10.pcf.gz
│   ├── clB8x12.pcf.gz
│   ├── clB8x13.pcf.gz
│   ├── clB8x14.pcf.gz
│   ├── clB8x16.pcf.gz
│   ├── clB8x8.pcf.gz
│   ├── clB9x15.pcf.gz
│   ├── clI6x12.pcf.gz
│   ├── clI8x8.pcf.gz
│   ├── clR4x6.pcf.gz
│   ├── clR5x10.pcf.gz
│   ├── clR5x6.pcf.gz
│   ├── clR5x8.pcf.gz
│   ├── clR6x10.pcf.gz
│   ├── clR6x12-ISO8859-1.pcf.gz
│   ├── clR6x12-ISO8859-10.pcf.gz
│   ├── clR6x12-ISO8859-13.pcf.gz
│   ├── clR6x12-ISO8859-14.pcf.gz
│   ├── clR6x12-ISO8859-15.pcf.gz
│   ├── clR6x12-ISO8859-16.pcf.gz
│   ├── clR6x12-ISO8859-2.pcf.gz
│   ├── clR6x12-ISO8859-3.pcf.gz
│   ├── clR6x12-ISO8859-4.pcf.gz
│   ├── clR6x12-ISO8859-5.pcf.gz
│   ├── clR6x12-ISO8859-7.pcf.gz
│   ├── clR6x12-ISO8859-8.pcf.gz
│   ├── clR6x12-ISO8859-9.pcf.gz
│   ├── clR6x12-KOI8-R.pcf.gz
│   ├── clR6x12.pcf.gz
│   ├── clR6x13.pcf.gz
│   ├── clR6x6.pcf.gz
│   ├── clR6x8.pcf.gz
│   ├── clR7x10.pcf.gz
│   ├── clR7x12.pcf.gz
│   ├── clR7x14.pcf.gz
│   ├── clR7x8.pcf.gz
│   ├── clR8x10.pcf.gz
│   ├── clR8x12.pcf.gz
│   ├── clR8x13.pcf.gz
│   ├── clR8x14.pcf.gz
│   ├── clR8x16.pcf.gz
│   ├── clR8x8.pcf.gz
│   ├── clR9x15.pcf.gz
│   ├── cu-alt12.pcf.gz
│   ├── cu-arabic12.pcf.gz
│   ├── cu-devnag12.pcf.gz
│   ├── cu-lig12.pcf.gz
│   ├── cu-pua12.pcf.gz
│   ├── cu12.pcf.gz
│   ├── cuarabic12.pcf.gz
│   ├── cudevnag12.pcf.gz
│   ├── cursor.pcf.gz
│   ├── deccurs.pcf.gz
│   ├── decsess.pcf.gz
│   ├── fonts.alias
│   ├── fonts.dir
│   ├── fonts.scale
│   ├── gb16fs.pcf.gz
│   ├── gb16st.pcf.gz
│   ├── gb24st.pcf.gz
│   ├── hanglg16.pcf.gz
│   ├── hanglm16.pcf.gz
│   ├── hanglm24.pcf.gz
│   ├── jiskan16.pcf.gz
│   ├── jiskan24.pcf.gz
│   ├── k14.pcf.gz
│   ├── micro.pcf.gz
│   ├── nil2.pcf.gz
│   ├── olcursor.pcf.gz
│   ├── olgl10.pcf.gz
│   ├── olgl12.pcf.gz
│   ├── olgl14.pcf.gz
│   └── olgl19.pcf.gz
└── util
├── map-ISO8859-1
├── map-ISO8859-10
├── map-ISO8859-11
├── map-ISO8859-13
├── map-ISO8859-14
├── map-ISO8859-15
├── map-ISO8859-16
├── map-ISO8859-2
├── map-ISO8859-3
├── map-ISO8859-4
├── map-ISO8859-5
├── map-ISO8859-6
├── map-ISO8859-7
├── map-ISO8859-8
├── map-ISO8859-9
├── map-JISX0201.1976-0
└── map-KOI8-R
10 directories, 676 files
Thanks again
Last edited by mibadt (2014-06-01 09:10:42)

Short answer: Try installing either or both 'extra/xorg-fonts-100dpi' and 'extra/xorg-fonts-75dpi'.
Long answer:
I don't have efax-gtk installed. The efax program is looking for a font using the old XLFD system of font names. The fontconfig methods for checking fonts may not be useful to determine where the problem lies. The program xlsfonts, from 'extra/xorg-xlsfonts', is needed to search for a match to the font name.
I have a Helvetica font installed, your results may be different or you may have no results from xlsfonts.
$ # Find the font names that match.
$ xlsfonts -fn "-*-Helvetica-Medium-R-Normal--*-140-*-*-P-*-ISO8859-1"
-adobe-helvetica-medium-r-normal--14-140-75-75-p-77-iso8859-1
-adobe-helvetica-medium-r-normal--19-140-100-100-p-0-iso8859-1
-adobe-helvetica-medium-r-normal--19-140-100-100-p-0-iso8859-1
-adobe-helvetica-medium-r-normal--20-140-100-100-p-100-iso8859-1
$ # Find the directories and one of the files for the fonts named above.
$ grep -r -m1 '\-adobe-helvetica-medium-r-normal' /usr/share/fonts/**/fonts.dir
/usr/share/fonts/100dpi/fonts.dir:helvR08-ISO8859-1.pcf.gz -adobe-helvetica-medium-r-normal--11-80-100-100-p-56-iso8859-1
/usr/share/fonts/75dpi/fonts.dir:helvR08-ISO8859-1.pcf.gz -adobe-helvetica-medium-r-normal--8-80-75-75-p-46-iso8859-1
$ # Find the packages containing the files.
$ pkgfile helvR08-ISO8859-1.pcf.gz
extra/xorg-fonts-100dpi
extra/xorg-fonts-75dpi

Power of File Naming during import

Can you append the HH (Hour) MM (Minute) SS (Second) that the photo was shot to the name while importing?
I have read that Aperture will not allow files to be renamed after in the Library to follow along with being non destructive. However I do not see renaming files or appending Meta Data in IPTC as being destructive and should not be ignored if the Photographer desires that to be part of his/her workflow.
I am sure that some third party programmers will write Automator scripts to accomplish many of the things that Aperture will be lacking in.
I am curious as to the power and functionality of Naming digital files as they are imported. I know that they can be tagged with YYMMDD. I have Read the Getting Started but want to know if HHMMSS can be appended also. I have searched the Internet for a naming convention that is very flexible and unique. When files are imported you do not know and can not say what is in each file, so better renaming and IPTC editing should be support post import. I do not consider preImport or during the best place to do this in Post Production. I think this can best be accomplished after using Aperture's Great Meta tagging tools.
I have accepted for for the majority of my workflow that Files should only be named once, and only tagged with a different name on an export. (Like appendning some Keywords).
I used to use a Random, Sequentually generated SN, but think now that the Date is nearly Unique (execpt Multiple Shots a second, or from other cameras at the same time.) I think that this SN to be tagged on the photo is more helpful.
Does any body recommend a powerful naming convention for digital image files?
Here is the naming Scheme that I am thinking of.
YYMMDD-HHMMSSx.CR2
X - is 0 through 9 to account for multiple shots a second.
I was planning on using the sequential numbering. This will allow me to easily speak out differenced between multiple files in a stack by speaking the last number which will usually be unique.
I have also thought about YYMMDD-ABC-HHMMSSx.cr2 (ABC would identify the roll) which is similar to what I have used, but I am do not like ABC now because it might mislead me or not mean anything at all.
What is everybody using, and what is working for you???
(and again)
Can you append the HH (Hour) MM (Minute) SS (Second) that the photo was shot to the name while importing?
PowerMac G5 Mac OS X (10.4.3)

Yes, after playing with it at home, I confirm the same things. All of the - (dashes) and .(dots) and 'PM' is wasteful, and aperture will not even show that full name.
Naming is a Huge deal. The photos will not be in Aperture forever, and when they come back out during an export or whatever, they should be how you want them. Not having control makes using aperture as a Library for your photos and projects weak.
If Aperture starts at the import from digital media, then naming happens only after that point. If I have to rename files before importing them into aperture then, I have to skip Aperture's first Steps.
When I name photos I have in the past tagged some keywords to the file name. Stacks and smart albums would do great to help, but after I put all of the work into naming and organizing, the filenames can not be set to what I want them to be.
This means that I would still have to use a 3rd party app to organize sort and name all photos then import to aperture.
Now the Stacks functionality, and keyword tagging can be skipped in Aperture. What is left are versions, working with RAW and smart albums. And Spotlight would do just as good of a job searching for photos this way.
I do not want to knock Aperture, but I have to accept that it is a learning curve. I need to learn what it can do for me to save time. And I need to learn what it will not do so that I can stay away from it. I was really looking forword to it being my post production SW.
I would like for something like this.
YYMMDD-HHMMSSx-Grouping Keyword(IPTC)-1 of 7(in stack)
This would use the Keyword and IPTC That you work hard to set in aperture, and also the stacking. Then when they are exported to clients, or for backup, web, or use when aperture has reached EOL, then it can be very useful.
I like that iPhoto has 3rd party extensions to use Keywords to Save in photo or extract from photo to add to iPhoto Library. I am a little more afraid of Aperture because it is a closed system. If a 3rd party app sets keywords to a photo or renames it, what info would be lost in Aperture.
Thanks for all of the thougts.

How to load original fonts in a packaged ID file I was sent

How to a load fonts into a packaged document another designer sent me; I don't want to use them in my document, but I'd like them in hers. This InDesign CC14. In other words, I have her fonts in her package, but don't know how to get them showing in her document correctly without using them in mine.

Sorry for the delay in answering. The fonts named as missing are:
Helvetica Neue (T1) 107 Extra Black Cond Oblique
Helvetica Neue (T1) 27 Ultra Light Condensed
Helvetica Neue (T1) 35 Thin
Helvetica Neue (T1) 45 Light
Helvetica Neue (T1) 65 Medium
Helvetica Neue (T1) 66 Medium Italic
Helvetica Neue (T1) 67 Medium Condensed
Helvetica Neue (T1) 75 Bold
Helvetica Neue (T1) 76 Bold Italic
Helvetica Neue (T1) 77 Bold Condensed
Helvetica Neue (T1) 77 Bold Condensed Oblique
Helvetica Neue (T1) 85 Heavy
Helvetica Neue (T1) 86 Heavy Italic
Helvetica Neue (T1) 87 Heavy Condensed
Helvetica Neue (T1) 95 Black
Helvetica Neue (T1) 97 Black Condensed
Helvetica Neue (T1) 97 Black Condensed Oblique
Times (T1)
Helvetica Neue-Heavy
I do not see these in the Fonts Folder, or much else I recognize as a font. I didn’t look before because I just assumed when packaged every font would be collected, but maybe they are just not there.

Temp File Name Schema in Receiver File adapter

Hi,
I have a scenario where i have to write the file in the temperaory location before writing it to the FTP loacation, I have selected the Processing Parameter as "Use Temperory File" but when the file gets created it is padded with the Message Id, is thr any option to get the file name as the temp file name without the Message Id or timestamp.
Please let me know if any one has come across such scenario.
thankx,
shree

Hi,
Under Write Mode, specify whether the target file is to be written directly in the specified directory. If an additional step is to be added using a temporary file, choose Use Temporary File.
You can specify a naming scheme for the temporary file under Temporary File Name Scheme.
This schema is used to determine the prefix and extension of the temporary file; to ensure a unique file name, a time stamp is also added to the name during processing.
The schema xitemp.tmp, for example, results in the file name xitemp<timestamp>.tmp
So you have to customise the file name in schema.
see below link
http://help.sap.com/saphelp_nw2004s/helpdata/en/bc/bb79d6061007419a081e58cbeaaf28/content.htm
Regards
Chilla

Unable to copy/cut/paste from within custom file naming dialogue (in exporting images)

When I go into the export dialogue and select a portion of a file naming scheme, I cannot get it into the clipboard. I had wanted to cut a portion of the specification, export with an amended name, and then paste the original back. I am running the beta in Win7 64-bit.

Advice:
1) Check Copy in sand-boxed app. in 1.6.0_24+.
2) Do not hi-jack the threads of other people. Start a new thread and if you think another thread relates to your problem, link to it.

RE: Named anchored objects

Albert,
In my case I was using a named anchored object to get a handle to an actual
service object. My named object that I registered in the name service was
an intermediary to which I did not maintain a connection. So I have not
explicitly tested what you are asking.
However, I too was not using a hard coded reference to the SO, and fail over
and load balancing worked fine. The functions of fail over and load
balancing are not done by the service object but by the name service, proxy
and router. Since you are getting a proxy back any time you do a lookup in
the name service I would think that fail over should work with any anchored
object that is registered in the name service. When you do a RegisterObject
call you will notice that one of the arguments is the session duration,
which implies to me that fail over will be handled the same as for service
objects.
Load balancing adds another wrinkle. Load balancing is handled by a router.
You must get a proxy to the router and not a proxy to an instance of the
object that the router is doing the load balancing for. In the latter
scenario you will be bypassing the router. If you are creating, anchoring
and registering your objects dynamically you will not have a router so you
will not be able to load balance! This applies even if the objects are
instantiated within partitions that are load balanced because you will still
be getting proxies back to a particular instance of the anchored objects.
There are ways to accomplish load balancing between objects that you
register yourself. However, the best solution will vary depending on the
actual problem trying to be solved. If you would like to discuss this
further, include a little more detail about the scenario you need to
implement and I will give you what I know.
BTY what I have outlined above also applies to getting references via a
system agent.
Sean
Cornice Consulting, Inc.
-----Original Message-----
From: [email protected]
[<a href="mailto:[email protected]">mailto:[email protected]]On</a> Behalf Of Albert Dijk
Sent: Friday, July 03, 1998 11:01 AM
To: [email protected]
Subject:
Alex, David, Jez, Sean,...
My question about both solutions (using Nameservice and agents) is:
If I reach a remote service object using either a BindObject or an agent, do
fail-over and load-balancing work the same way as they normally do when
using a hard coded reference to the SO.
Albert Dijk
From: Sean Brown[SMTP:[email protected]]
Reply To: [email protected]
Sent: Thursday, June 25, 1998 6:55 AM
To: Ananiev, Alex; [email protected]
Subject: RE: multiple named objects with the same name and
interface
Alexander,
I can not comment on the speed difference because I never tested it.
But, I
will say that we looked at the agent solution at a client sight
before. I
will give the same warning I gave them. If you go the agent direction
you
are now using agents for a purpose that they were not intended. Even
though
it technically works, as soon as you start using a piece of
functionality in
a way the developer did not intend it to be used you run the risk of
forward
compatibility problems. By this I mean, since agents were not
originally
intended to be used to look up service / anchored object references,
it may
not work in the future because it is not likely to be given
consideration in
any future design.
As we all know, programmers are always stretching the bounds of the
tools
they use and you may have a good reason (i.e. performance). I just
wanted to
let you know the possible risk.
One final note on a limitation of using system agents to obtain
references
to anchored objects. You can not access agents across environments.
So, if
you have connected environments and need to get references to services
in
another environment for fail-over or whatever, you will not be able to
do it
with agents.
Just some thoughts!
Sean
-----Original Message-----
From: [email protected]
[<a href="mailto:[email protected]]On">mailto:[email protected]]On</a> Behalf Of Ananiev, Alex
Sent: Wednesday, June 24, 1998 12:14 PM
To: '[email protected]'
Subject: RE: multiple named objects with the same name and interface
David,
The problem with dynamic binding is that in this case you have to keep
the reference to the service object somewhere. You don't want to call
"bindObject" every time you need to use this service object, "bind" is
a
time-consuming operation, even on the same partition. Keeping
reference
could be undesirable if your object could be moved across partitions
(e.g. business object).
The alternative solution is to use agents. You can create custom
agent,
make it a subagent of an active partition agent and use it as a
placeholder for whatever service you need. "FindSubAgent" works much
faster than "bindObject", we verified that and agent is "user-visible"
by its nature.
Alexander
From: "Sean Brown" <[email protected]>
Date: Wed, 24 Jun 1998 09:12:55 -0500
Subject: RE: multiple named objects with the same name and interface
David,
I actually determined it through testing. In my case I did not want
this to
happen and was trying to determine why it was happing. It makes sense
if
you think about it. Forte is trying to avoid making a remote method
invocation if it can.
Now, for anything more complex than looking locally first and if none
is
found give me any remote instance you can find, you will need to do
more
work. Using a naming scheme like Jez suggests below works well.
Sean
- -----Original Message-----
From: Jez Sygrove [<a href="mailto:[email protected]">mailto:[email protected]</a>]
Sent: Wednesday, June 24, 1998 4:34 AM
To: [email protected]; 'David Foote'
Cc: [email protected]
Subject: RE: multiple named objects with the same name and interface
David,
there's a mechanism used within SCAFFOLDS that allows the
location of the 'nearest' SO when more than one is available.
It involves registering each duplicated SO under three dynamically
built
names. The names include the partition, the node or the environment
name.
When wishing to locate the nearest SO the BO builds a SO name using
its
own partition and asks the name service for that.
If there is an SO registered under that name then it must be in the
same
partition and all is well. No cross partition calls.
If not, then the BO builds the name using its node and asks the name
service for that.
This means that if there is an SO outside the BO partition but still
on
the same node then this can be used. Again, relatively 'local'.
If neither of these work then the BO has to resort to an environment
wide search.
It may be that this approach could be adapted / adopted; I like it's
ingenuity.
Cheers,
Jez
From: David Foote[SMTP:[email protected]]
Reply To: David Foote
Sent: 24 June 1998 03:17
To: [email protected]
Cc: [email protected]
Subject: RE: multiple named objects with the same name and
interface
Sean,
First, thank you for your response. I have wondered about this fora
long time.
I looked at the documentation for ObjectLocationManager and on page
327
of the Framework Library and AppletSupport Library Guide indescribing
the BindObject method Forte says:
"The name service allows more than one anchored object (from
different
partitions) to be registered in the name service under the same
registration name. When you invoke the BindObject method with a
request
for a name that has duplicate registration entries, the BindObject
method finds an entry corresponding to an active partition, skipping
any
entries that do not. If no such active partition is found, or if the
requested name is not found in the name service registry, a
RemoteAccessException will be raised when the BindObject method is
invoked."
My question is: How did you discover that in the case of duplicate
registrations the naming service will return the local object if one
exists? This is not apparent from the documentation I have quoted.
Is
it documented elsewhere? Or did you determine it empirically?
David N. Foote,
Consultant
----Original Message Follows----
David,
First I will start by saying that this can be done by using named
anchored
objects and registering them yourself in the name service. There is
documentation on how to do this. And by default you will get mostof
the
behavior you desire. When you do a lookup in the name service
(BindObject
method) it will first look in the local partition and see if thereis
a
local copy and give you that copy. By anchoring the object and
manually
registering it in the name service you are programmatically creating
your
own SO without defining it as such in the development environment.
BTW
in
response to your item number 1. This should be the case there as
well.
If
your "mobile" object is in the same partition where the serviceobject
he is
calling resides, you should get a handle to the local instance ofthe
service object.
Here is the catch, if you make a bind object call and there is no
local
copy
you will get a handle to a remote copy but you can not be sure which
one!
It end ups as more or less a random selection. Off the top of myhead
and
without going to the doc, I am pretty sure that when you register an
anchored object you can not limit it's visibility to "User".
Sean
-----Original Message-----
From: [email protected]
[<a href=
"mailto:[email protected]]On">mailto:[email protected]]On</a> Behalf Of David Foote
Sent: Monday, June 22, 1998 4:51 PM
To: [email protected]
Subject: multiple named objects with the same name and interface
All,
More than once, I have wished that Forte allowed you to place named
objects with the same name in more than one partition. There aretwo
situations in which this seems desirable:
1) Objects that are not distributed, but are mobile (passed by value
to
remote objects), cannot safely reference a Service Object unless it
has
environment visibility, but this forces the overhead of a remote
method
call when it might not otherwise be necessary. If it were possibleto
place a copy of the same Service Object (with user visibility) ineach
partition, the overhead of a remote method call could be avoided.
This
would only be useful for a service object whose state could besafely
replicated.
2) My second scenario also involves mobile objects referencing a
Service
Object, but this time I would like the behavior of the calledService
Object to differ with the partition from which it is called.
This could be accomplished by placing Service Objects with the same
name
and the same interface in each partition, but varying the
implementation
with the partition.
Does anyone have any thoughts about why this would be a good thingor
a
bad thing?
David N. Foote
Consultant
Alexander Ananiev
Claremont Technology Group
916-558-4127
To unsubscribe, email '[email protected]' with
'unsubscribe forte-users' as the body of the message.
Searchable thread archive
<URL:<a href="http://pinehurst.sageit.com/listarchive/">http://pinehurst.sageit.com/listarchive/</a>>
>
>
>
Alexander Ananiev
Claremont Technology Group
916-558-4127
To unsubscribe, email '[email protected]' with
'unsubscribe forte-users' as the body of the message.
Searchable thread archive <URL:<a href=
"http://pinehurst.sageit.com/listarchive/">http://pinehurst.sageit.com/listarchive/</a>>
To unsubscribe, email '[email protected]' with
'unsubscribe forte-users' as the body of the message.
Searchable thread archive <URL:<a href=
"http://pinehurst.sageit.com/listarchive/">http://pinehurst.sageit.com/listarchive/</a>>

Albert,
In my case I was using a named anchored object to get a handle to an actual
service object. My named object that I registered in the name service was
an intermediary to which I did not maintain a connection. So I have not
explicitly tested what you are asking.
However, I too was not using a hard coded reference to the SO, and fail over
and load balancing worked fine. The functions of fail over and load
balancing are not done by the service object but by the name service, proxy
and router. Since you are getting a proxy back any time you do a lookup in
the name service I would think that fail over should work with any anchored
object that is registered in the name service. When you do a RegisterObject
call you will notice that one of the arguments is the session duration,
which implies to me that fail over will be handled the same as for service
objects.
Load balancing adds another wrinkle. Load balancing is handled by a router.
You must get a proxy to the router and not a proxy to an instance of the
object that the router is doing the load balancing for. In the latter
scenario you will be bypassing the router. If you are creating, anchoring
and registering your objects dynamically you will not have a router so you
will not be able to load balance! This applies even if the objects are
instantiated within partitions that are load balanced because you will still
be getting proxies back to a particular instance of the anchored objects.
There are ways to accomplish load balancing between objects that you
register yourself. However, the best solution will vary depending on the
actual problem trying to be solved. If you would like to discuss this
further, include a little more detail about the scenario you need to
implement and I will give you what I know.
BTY what I have outlined above also applies to getting references via a
system agent.
Sean
Cornice Consulting, Inc.
-----Original Message-----
From: [email protected]
[<a href="mailto:[email protected]">mailto:[email protected]]On</a> Behalf Of Albert Dijk
Sent: Friday, July 03, 1998 11:01 AM
To: [email protected]
Subject:
Alex, David, Jez, Sean,...
My question about both solutions (using Nameservice and agents) is:
If I reach a remote service object using either a BindObject or an agent, do
fail-over and load-balancing work the same way as they normally do when
using a hard coded reference to the SO.
Albert Dijk
From: Sean Brown[SMTP:[email protected]]
Reply To: [email protected]
Sent: Thursday, June 25, 1998 6:55 AM
To: Ananiev, Alex; [email protected]
Subject: RE: multiple named objects with the same name and
interface
Alexander,
I can not comment on the speed difference because I never tested it.
But, I
will say that we looked at the agent solution at a client sight
before. I
will give the same warning I gave them. If you go the agent direction
you
are now using agents for a purpose that they were not intended. Even
though
it technically works, as soon as you start using a piece of
functionality in
a way the developer did not intend it to be used you run the risk of
forward
compatibility problems. By this I mean, since agents were not
originally
intended to be used to look up service / anchored object references,
it may
not work in the future because it is not likely to be given
consideration in
any future design.
As we all know, programmers are always stretching the bounds of the
tools
they use and you may have a good reason (i.e. performance). I just
wanted to
let you know the possible risk.
One final note on a limitation of using system agents to obtain
references
to anchored objects. You can not access agents across environments.
So, if
you have connected environments and need to get references to services
in
another environment for fail-over or whatever, you will not be able to
do it
with agents.
Just some thoughts!
Sean
-----Original Message-----
From: [email protected]
[<a href="mailto:[email protected]]On">mailto:[email protected]]On</a> Behalf Of Ananiev, Alex
Sent: Wednesday, June 24, 1998 12:14 PM
To: '[email protected]'
Subject: RE: multiple named objects with the same name and interface
David,
The problem with dynamic binding is that in this case you have to keep
the reference to the service object somewhere. You don't want to call
"bindObject" every time you need to use this service object, "bind" is
a
time-consuming operation, even on the same partition. Keeping
reference
could be undesirable if your object could be moved across partitions
(e.g. business object).
The alternative solution is to use agents. You can create custom
agent,
make it a subagent of an active partition agent and use it as a
placeholder for whatever service you need. "FindSubAgent" works much
faster than "bindObject", we verified that and agent is "user-visible"
by its nature.
Alexander
From: "Sean Brown" <[email protected]>
Date: Wed, 24 Jun 1998 09:12:55 -0500
Subject: RE: multiple named objects with the same name and interface
David,
I actually determined it through testing. In my case I did not want
this to
happen and was trying to determine why it was happing. It makes sense
if
you think about it. Forte is trying to avoid making a remote method
invocation if it can.
Now, for anything more complex than looking locally first and if none
is
found give me any remote instance you can find, you will need to do
more
work. Using a naming scheme like Jez suggests below works well.
Sean
- -----Original Message-----
From: Jez Sygrove [<a href="mailto:[email protected]">mailto:[email protected]</a>]
Sent: Wednesday, June 24, 1998 4:34 AM
To: [email protected]; 'David Foote'
Cc: [email protected]
Subject: RE: multiple named objects with the same name and interface
David,
there's a mechanism used within SCAFFOLDS that allows the
location of the 'nearest' SO when more than one is available.
It involves registering each duplicated SO under three dynamically
built
names. The names include the partition, the node or the environment
name.
When wishing to locate the nearest SO the BO builds a SO name using
its
own partition and asks the name service for that.
If there is an SO registered under that name then it must be in the
same
partition and all is well. No cross partition calls.
If not, then the BO builds the name using its node and asks the name
service for that.
This means that if there is an SO outside the BO partition but still
on
the same node then this can be used. Again, relatively 'local'.
If neither of these work then the BO has to resort to an environment
wide search.
It may be that this approach could be adapted / adopted; I like it's
ingenuity.
Cheers,
Jez
From: David Foote[SMTP:[email protected]]
Reply To: David Foote
Sent: 24 June 1998 03:17
To: [email protected]
Cc: [email protected]
Subject: RE: multiple named objects with the same name and
interface
Sean,
First, thank you for your response. I have wondered about this fora
long time.
I looked at the documentation for ObjectLocationManager and on page
327
of the Framework Library and AppletSupport Library Guide indescribing
the BindObject method Forte says:
"The name service allows more than one anchored object (from
different
partitions) to be registered in the name service under the same
registration name. When you invoke the BindObject method with a
request
for a name that has duplicate registration entries, the BindObject
method finds an entry corresponding to an active partition, skipping
any
entries that do not. If no such active partition is found, or if the
requested name is not found in the name service registry, a
RemoteAccessException will be raised when the BindObject method is
invoked."
My question is: How did you discover that in the case of duplicate
registrations the naming service will return the local object if one
exists? This is not apparent from the documentation I have quoted.
Is
it documented elsewhere? Or did you determine it empirically?
David N. Foote,
Consultant
----Original Message Follows----
David,
First I will start by saying that this can be done by using named
anchored
objects and registering them yourself in the name service. There is
documentation on how to do this. And by default you will get mostof
the
behavior you desire. When you do a lookup in the name service
(BindObject
method) it will first look in the local partition and see if thereis
a
local copy and give you that copy. By anchoring the object and
manually
registering it in the name service you are programmatically creating
your
own SO without defining it as such in the development environment.
BTW
in
response to your item number 1. This should be the case there as
well.
If
your "mobile" object is in the same partition where the serviceobject
he is
calling resides, you should get a handle to the local instance ofthe
service object.
Here is the catch, if you make a bind object call and there is no
local
copy
you will get a handle to a remote copy but you can not be sure which
one!
It end ups as more or less a random selection. Off the top of myhead
and
without going to the doc, I am pretty sure that when you register an
anchored object you can not limit it's visibility to "User".
Sean
-----Original Message-----
From: [email protected]
[<a href=
"mailto:[email protected]]On">mailto:[email protected]]On</a> Behalf Of David Foote
Sent: Monday, June 22, 1998 4:51 PM
To: [email protected]
Subject: multiple named objects with the same name and interface
All,
More than once, I have wished that Forte allowed you to place named
objects with the same name in more than one partition. There aretwo
situations in which this seems desirable:
1) Objects that are not distributed, but are mobile (passed by value
to
remote objects), cannot safely reference a Service Object unless it
has
environment visibility, but this forces the overhead of a remote
method
call when it might not otherwise be necessary. If it were possibleto
place a copy of the same Service Object (with user visibility) ineach
partition, the overhead of a remote method call could be avoided.
This
would only be useful for a service object whose state could besafely
replicated.
2) My second scenario also involves mobile objects referencing a
Service
Object, but this time I would like the behavior of the calledService
Object to differ with the partition from which it is called.
This could be accomplished by placing Service Objects with the same
name
and the same interface in each partition, but varying the
implementation
with the partition.
Does anyone have any thoughts about why this would be a good thingor
a
bad thing?
David N. Foote
Consultant
Alexander Ananiev
Claremont Technology Group
916-558-4127
To unsubscribe, email '[email protected]' with
'unsubscribe forte-users' as the body of the message.
Searchable thread archive
<URL:<a href="http://pinehurst.sageit.com/listarchive/">http://pinehurst.sageit.com/listarchive/</a>>
>
>
>
Alexander Ananiev
Claremont Technology Group
916-558-4127
To unsubscribe, email '[email protected]' with
'unsubscribe forte-users' as the body of the message.
Searchable thread archive <URL:<a href=
"http://pinehurst.sageit.com/listarchive/">http://pinehurst.sageit.com/listarchive/</a>>
To unsubscribe, email '[email protected]' with
'unsubscribe forte-users' as the body of the message.
Searchable thread archive <URL:<a href=
"http://pinehurst.sageit.com/listarchive/">http://pinehurst.sageit.com/listarchive/</a>>

Font naming schemes (mrxvt)

Similar Messages

Maybe you are looking for