How do you know the correct name to use for X11 fonts for XTerm*faceName or xterm -fa ?











up vote
9
down vote

favorite
7












I am using Mac OS X 10.8 and XQuartz 2.7.2. I have downloaded and placed several TrueType fonts named *.ttf in my /Users/<name>/.fonts directory. Upon running XQuartz several files including fonts.dir are created. This file has X11 font names of various encodings, etc. for each font I've installed.



My trouble is that I can't always "figure out" the correct name to use in xterm -fa <NAME> or in my .Xresources XTerm*faceName entry. For some fonts the core font name as listed in the detailed X11 font name in the fonts.dir file works whereas for others it doesn't.










share|improve this question


















  • 1




    If it helps: the FreeBSD 10.2 manual page for xterm(1) includes information on -fa and the faceName resource.
    – Graham Perrin
    Feb 25 '16 at 19:38















up vote
9
down vote

favorite
7












I am using Mac OS X 10.8 and XQuartz 2.7.2. I have downloaded and placed several TrueType fonts named *.ttf in my /Users/<name>/.fonts directory. Upon running XQuartz several files including fonts.dir are created. This file has X11 font names of various encodings, etc. for each font I've installed.



My trouble is that I can't always "figure out" the correct name to use in xterm -fa <NAME> or in my .Xresources XTerm*faceName entry. For some fonts the core font name as listed in the detailed X11 font name in the fonts.dir file works whereas for others it doesn't.










share|improve this question


















  • 1




    If it helps: the FreeBSD 10.2 manual page for xterm(1) includes information on -fa and the faceName resource.
    – Graham Perrin
    Feb 25 '16 at 19:38













up vote
9
down vote

favorite
7









up vote
9
down vote

favorite
7






7





I am using Mac OS X 10.8 and XQuartz 2.7.2. I have downloaded and placed several TrueType fonts named *.ttf in my /Users/<name>/.fonts directory. Upon running XQuartz several files including fonts.dir are created. This file has X11 font names of various encodings, etc. for each font I've installed.



My trouble is that I can't always "figure out" the correct name to use in xterm -fa <NAME> or in my .Xresources XTerm*faceName entry. For some fonts the core font name as listed in the detailed X11 font name in the fonts.dir file works whereas for others it doesn't.










share|improve this question













I am using Mac OS X 10.8 and XQuartz 2.7.2. I have downloaded and placed several TrueType fonts named *.ttf in my /Users/<name>/.fonts directory. Upon running XQuartz several files including fonts.dir are created. This file has X11 font names of various encodings, etc. for each font I've installed.



My trouble is that I can't always "figure out" the correct name to use in xterm -fa <NAME> or in my .Xresources XTerm*faceName entry. For some fonts the core font name as listed in the detailed X11 font name in the fonts.dir file works whereas for others it doesn't.







fonts xterm






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Aug 23 '12 at 2:29









Jason Waldrop

213139




213139








  • 1




    If it helps: the FreeBSD 10.2 manual page for xterm(1) includes information on -fa and the faceName resource.
    – Graham Perrin
    Feb 25 '16 at 19:38














  • 1




    If it helps: the FreeBSD 10.2 manual page for xterm(1) includes information on -fa and the faceName resource.
    – Graham Perrin
    Feb 25 '16 at 19:38








1




1




If it helps: the FreeBSD 10.2 manual page for xterm(1) includes information on -fa and the faceName resource.
– Graham Perrin
Feb 25 '16 at 19:38




If it helps: the FreeBSD 10.2 manual page for xterm(1) includes information on -fa and the faceName resource.
– Graham Perrin
Feb 25 '16 at 19:38










4 Answers
4






active

oldest

votes

















up vote
15
down vote













The following one-liner has often helped me a lot to find the correct font name:



$ fc-list | cut -f2 -d: | sort -u


Especially with Japanese fonts like 'IPAX0208Mincho', I would never have been able to guess the correct name.
If you don't mind a little more typing effort, you might even prefer



$ fc-list | cut -f2 -d: | sort -u | less -r


to get a paged output.






share|improve this answer






























    up vote
    3
    down vote













    You can use xfontsel to get the right name:



    $ xfontsel


    enter image description here



    Chose the font you are interested in and then click on the "Select" button. That will copy the font name to the clipboard. Use that name to run xterm. E.g.:



    $ xterm -font -adobe-helvetica-*-r-normal-*-12-120-*-*-*-*-*-*


    Can't get it to work on my system (linux) using "-fa" but "-font" works.






    share|improve this answer

















    • 1




      Yes, I knew to use xfontsel to get the X11 font name and use xterm -font to select it. What's strange is that for some fonts I can use xterm -fa <simple font name> and it works fine on other fonts it doesn't. I think you must have to have a very specific spelling of the <simple font name> because if I take a font where it works and change one letter it doesn't work anymore. So, my basic question is how do you systematically determine the "correct" <simple font name> such that xterm -fa works.
      – Jason Waldrop
      Aug 23 '12 at 14:22










    • @JasonWaldrop Ah. In that case, I'm stumped.
      – terdon
      Aug 23 '12 at 15:35










    • If it helps (from the man page): "… though xfd accepts a "-fa" option to denote FreeType fonts), xfontsel has not been similarly extended …"
      – Graham Perrin
      Feb 25 '16 at 19:40










    • @JasonWaldrop you might be interested in the comment above.
      – terdon
      Feb 25 '16 at 19:43




















    up vote
    0
    down vote













    If you use FontBook to load the font, it will display the correct name to use with xterm -fa.






    share|improve this answer




























      up vote
      0
      down vote













      What's missing are entries in the fonts.alias file:



      /usr/share/X11/fonts/75dpi/fonts.alias


      What this file does is provide short names ("aliases") for X Window fonts that are installed. When you try to use a short name that isn't in the file, you get behavior like this when starting xterm:



      lansdale:~> xterm -xrm *font:courr12
      xterm: cannot load font "courr12"


      (The xterm does come up and runs with a default, different font)



      The fonts.alias file exists because of the long length of X11 font names. For example, courr12 is the short name for:



      -adobe-courier-medium-r-normal--12-120-75-75-m-70-iso10646-1


      [The long names are actually 14 different editable fields stitched together with dashes/hyphens. Run program xfontsel to see them; it will start with all fields showing with an asterisk, meaning not set to something specific.]



      Each line in the file begins with a short name (an alias), a blank, then the long name it points/refers to. This way, you don't have to use the long name all the time, just set up an alias and use that. When putting a new line in the file, you decide what the short name will be, only the full X11 name has to have a font file installed on the system.



      When I first cut my teeth on Unix systems in the 1990s, I ran across courr12 and later came to desire font it (Courier 'Roman' size 12) for my xterms. On HP/UX and Solaris, the fonts.alias file already had courr12, so I could just put "XTerm*font: courr12" in my .Xdefaults file and everything would work fine.






      share|improve this answer























        Your Answer








        StackExchange.ready(function() {
        var channelOptions = {
        tags: "".split(" "),
        id: "3"
        };
        initTagRenderer("".split(" "), "".split(" "), channelOptions);

        StackExchange.using("externalEditor", function() {
        // Have to fire editor after snippets, if snippets enabled
        if (StackExchange.settings.snippets.snippetsEnabled) {
        StackExchange.using("snippets", function() {
        createEditor();
        });
        }
        else {
        createEditor();
        }
        });

        function createEditor() {
        StackExchange.prepareEditor({
        heartbeatType: 'answer',
        convertImagesToLinks: true,
        noModals: true,
        showLowRepImageUploadWarning: true,
        reputationToPostImages: 10,
        bindNavPrevention: true,
        postfix: "",
        imageUploader: {
        brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
        contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
        allowUrls: true
        },
        onDemand: true,
        discardSelector: ".discard-answer"
        ,immediatelyShowMarkdownHelp:true
        });


        }
        });














         

        draft saved


        draft discarded


















        StackExchange.ready(
        function () {
        StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f465142%2fhow-do-you-know-the-correct-name-to-use-for-x11-fonts-for-xtermfacename-or-xter%23new-answer', 'question_page');
        }
        );

        Post as a guest















        Required, but never shown

























        4 Answers
        4






        active

        oldest

        votes








        4 Answers
        4






        active

        oldest

        votes









        active

        oldest

        votes






        active

        oldest

        votes








        up vote
        15
        down vote













        The following one-liner has often helped me a lot to find the correct font name:



        $ fc-list | cut -f2 -d: | sort -u


        Especially with Japanese fonts like 'IPAX0208Mincho', I would never have been able to guess the correct name.
        If you don't mind a little more typing effort, you might even prefer



        $ fc-list | cut -f2 -d: | sort -u | less -r


        to get a paged output.






        share|improve this answer



























          up vote
          15
          down vote













          The following one-liner has often helped me a lot to find the correct font name:



          $ fc-list | cut -f2 -d: | sort -u


          Especially with Japanese fonts like 'IPAX0208Mincho', I would never have been able to guess the correct name.
          If you don't mind a little more typing effort, you might even prefer



          $ fc-list | cut -f2 -d: | sort -u | less -r


          to get a paged output.






          share|improve this answer

























            up vote
            15
            down vote










            up vote
            15
            down vote









            The following one-liner has often helped me a lot to find the correct font name:



            $ fc-list | cut -f2 -d: | sort -u


            Especially with Japanese fonts like 'IPAX0208Mincho', I would never have been able to guess the correct name.
            If you don't mind a little more typing effort, you might even prefer



            $ fc-list | cut -f2 -d: | sort -u | less -r


            to get a paged output.






            share|improve this answer














            The following one-liner has often helped me a lot to find the correct font name:



            $ fc-list | cut -f2 -d: | sort -u


            Especially with Japanese fonts like 'IPAX0208Mincho', I would never have been able to guess the correct name.
            If you don't mind a little more typing effort, you might even prefer



            $ fc-list | cut -f2 -d: | sort -u | less -r


            to get a paged output.







            share|improve this answer














            share|improve this answer



            share|improve this answer








            edited Dec 8 '15 at 10:30

























            answered Apr 25 '14 at 10:39









            syntaxerror

            390313




            390313
























                up vote
                3
                down vote













                You can use xfontsel to get the right name:



                $ xfontsel


                enter image description here



                Chose the font you are interested in and then click on the "Select" button. That will copy the font name to the clipboard. Use that name to run xterm. E.g.:



                $ xterm -font -adobe-helvetica-*-r-normal-*-12-120-*-*-*-*-*-*


                Can't get it to work on my system (linux) using "-fa" but "-font" works.






                share|improve this answer

















                • 1




                  Yes, I knew to use xfontsel to get the X11 font name and use xterm -font to select it. What's strange is that for some fonts I can use xterm -fa <simple font name> and it works fine on other fonts it doesn't. I think you must have to have a very specific spelling of the <simple font name> because if I take a font where it works and change one letter it doesn't work anymore. So, my basic question is how do you systematically determine the "correct" <simple font name> such that xterm -fa works.
                  – Jason Waldrop
                  Aug 23 '12 at 14:22










                • @JasonWaldrop Ah. In that case, I'm stumped.
                  – terdon
                  Aug 23 '12 at 15:35










                • If it helps (from the man page): "… though xfd accepts a "-fa" option to denote FreeType fonts), xfontsel has not been similarly extended …"
                  – Graham Perrin
                  Feb 25 '16 at 19:40










                • @JasonWaldrop you might be interested in the comment above.
                  – terdon
                  Feb 25 '16 at 19:43

















                up vote
                3
                down vote













                You can use xfontsel to get the right name:



                $ xfontsel


                enter image description here



                Chose the font you are interested in and then click on the "Select" button. That will copy the font name to the clipboard. Use that name to run xterm. E.g.:



                $ xterm -font -adobe-helvetica-*-r-normal-*-12-120-*-*-*-*-*-*


                Can't get it to work on my system (linux) using "-fa" but "-font" works.






                share|improve this answer

















                • 1




                  Yes, I knew to use xfontsel to get the X11 font name and use xterm -font to select it. What's strange is that for some fonts I can use xterm -fa <simple font name> and it works fine on other fonts it doesn't. I think you must have to have a very specific spelling of the <simple font name> because if I take a font where it works and change one letter it doesn't work anymore. So, my basic question is how do you systematically determine the "correct" <simple font name> such that xterm -fa works.
                  – Jason Waldrop
                  Aug 23 '12 at 14:22










                • @JasonWaldrop Ah. In that case, I'm stumped.
                  – terdon
                  Aug 23 '12 at 15:35










                • If it helps (from the man page): "… though xfd accepts a "-fa" option to denote FreeType fonts), xfontsel has not been similarly extended …"
                  – Graham Perrin
                  Feb 25 '16 at 19:40










                • @JasonWaldrop you might be interested in the comment above.
                  – terdon
                  Feb 25 '16 at 19:43















                up vote
                3
                down vote










                up vote
                3
                down vote









                You can use xfontsel to get the right name:



                $ xfontsel


                enter image description here



                Chose the font you are interested in and then click on the "Select" button. That will copy the font name to the clipboard. Use that name to run xterm. E.g.:



                $ xterm -font -adobe-helvetica-*-r-normal-*-12-120-*-*-*-*-*-*


                Can't get it to work on my system (linux) using "-fa" but "-font" works.






                share|improve this answer












                You can use xfontsel to get the right name:



                $ xfontsel


                enter image description here



                Chose the font you are interested in and then click on the "Select" button. That will copy the font name to the clipboard. Use that name to run xterm. E.g.:



                $ xterm -font -adobe-helvetica-*-r-normal-*-12-120-*-*-*-*-*-*


                Can't get it to work on my system (linux) using "-fa" but "-font" works.







                share|improve this answer












                share|improve this answer



                share|improve this answer










                answered Aug 23 '12 at 13:09









                terdon

                40.9k885134




                40.9k885134








                • 1




                  Yes, I knew to use xfontsel to get the X11 font name and use xterm -font to select it. What's strange is that for some fonts I can use xterm -fa <simple font name> and it works fine on other fonts it doesn't. I think you must have to have a very specific spelling of the <simple font name> because if I take a font where it works and change one letter it doesn't work anymore. So, my basic question is how do you systematically determine the "correct" <simple font name> such that xterm -fa works.
                  – Jason Waldrop
                  Aug 23 '12 at 14:22










                • @JasonWaldrop Ah. In that case, I'm stumped.
                  – terdon
                  Aug 23 '12 at 15:35










                • If it helps (from the man page): "… though xfd accepts a "-fa" option to denote FreeType fonts), xfontsel has not been similarly extended …"
                  – Graham Perrin
                  Feb 25 '16 at 19:40










                • @JasonWaldrop you might be interested in the comment above.
                  – terdon
                  Feb 25 '16 at 19:43
















                • 1




                  Yes, I knew to use xfontsel to get the X11 font name and use xterm -font to select it. What's strange is that for some fonts I can use xterm -fa <simple font name> and it works fine on other fonts it doesn't. I think you must have to have a very specific spelling of the <simple font name> because if I take a font where it works and change one letter it doesn't work anymore. So, my basic question is how do you systematically determine the "correct" <simple font name> such that xterm -fa works.
                  – Jason Waldrop
                  Aug 23 '12 at 14:22










                • @JasonWaldrop Ah. In that case, I'm stumped.
                  – terdon
                  Aug 23 '12 at 15:35










                • If it helps (from the man page): "… though xfd accepts a "-fa" option to denote FreeType fonts), xfontsel has not been similarly extended …"
                  – Graham Perrin
                  Feb 25 '16 at 19:40










                • @JasonWaldrop you might be interested in the comment above.
                  – terdon
                  Feb 25 '16 at 19:43










                1




                1




                Yes, I knew to use xfontsel to get the X11 font name and use xterm -font to select it. What's strange is that for some fonts I can use xterm -fa <simple font name> and it works fine on other fonts it doesn't. I think you must have to have a very specific spelling of the <simple font name> because if I take a font where it works and change one letter it doesn't work anymore. So, my basic question is how do you systematically determine the "correct" <simple font name> such that xterm -fa works.
                – Jason Waldrop
                Aug 23 '12 at 14:22




                Yes, I knew to use xfontsel to get the X11 font name and use xterm -font to select it. What's strange is that for some fonts I can use xterm -fa <simple font name> and it works fine on other fonts it doesn't. I think you must have to have a very specific spelling of the <simple font name> because if I take a font where it works and change one letter it doesn't work anymore. So, my basic question is how do you systematically determine the "correct" <simple font name> such that xterm -fa works.
                – Jason Waldrop
                Aug 23 '12 at 14:22












                @JasonWaldrop Ah. In that case, I'm stumped.
                – terdon
                Aug 23 '12 at 15:35




                @JasonWaldrop Ah. In that case, I'm stumped.
                – terdon
                Aug 23 '12 at 15:35












                If it helps (from the man page): "… though xfd accepts a "-fa" option to denote FreeType fonts), xfontsel has not been similarly extended …"
                – Graham Perrin
                Feb 25 '16 at 19:40




                If it helps (from the man page): "… though xfd accepts a "-fa" option to denote FreeType fonts), xfontsel has not been similarly extended …"
                – Graham Perrin
                Feb 25 '16 at 19:40












                @JasonWaldrop you might be interested in the comment above.
                – terdon
                Feb 25 '16 at 19:43






                @JasonWaldrop you might be interested in the comment above.
                – terdon
                Feb 25 '16 at 19:43












                up vote
                0
                down vote













                If you use FontBook to load the font, it will display the correct name to use with xterm -fa.






                share|improve this answer

























                  up vote
                  0
                  down vote













                  If you use FontBook to load the font, it will display the correct name to use with xterm -fa.






                  share|improve this answer























                    up vote
                    0
                    down vote










                    up vote
                    0
                    down vote









                    If you use FontBook to load the font, it will display the correct name to use with xterm -fa.






                    share|improve this answer












                    If you use FontBook to load the font, it will display the correct name to use with xterm -fa.







                    share|improve this answer












                    share|improve this answer



                    share|improve this answer










                    answered Aug 29 '12 at 0:19









                    Jason Waldrop

                    213139




                    213139






















                        up vote
                        0
                        down vote













                        What's missing are entries in the fonts.alias file:



                        /usr/share/X11/fonts/75dpi/fonts.alias


                        What this file does is provide short names ("aliases") for X Window fonts that are installed. When you try to use a short name that isn't in the file, you get behavior like this when starting xterm:



                        lansdale:~> xterm -xrm *font:courr12
                        xterm: cannot load font "courr12"


                        (The xterm does come up and runs with a default, different font)



                        The fonts.alias file exists because of the long length of X11 font names. For example, courr12 is the short name for:



                        -adobe-courier-medium-r-normal--12-120-75-75-m-70-iso10646-1


                        [The long names are actually 14 different editable fields stitched together with dashes/hyphens. Run program xfontsel to see them; it will start with all fields showing with an asterisk, meaning not set to something specific.]



                        Each line in the file begins with a short name (an alias), a blank, then the long name it points/refers to. This way, you don't have to use the long name all the time, just set up an alias and use that. When putting a new line in the file, you decide what the short name will be, only the full X11 name has to have a font file installed on the system.



                        When I first cut my teeth on Unix systems in the 1990s, I ran across courr12 and later came to desire font it (Courier 'Roman' size 12) for my xterms. On HP/UX and Solaris, the fonts.alias file already had courr12, so I could just put "XTerm*font: courr12" in my .Xdefaults file and everything would work fine.






                        share|improve this answer



























                          up vote
                          0
                          down vote













                          What's missing are entries in the fonts.alias file:



                          /usr/share/X11/fonts/75dpi/fonts.alias


                          What this file does is provide short names ("aliases") for X Window fonts that are installed. When you try to use a short name that isn't in the file, you get behavior like this when starting xterm:



                          lansdale:~> xterm -xrm *font:courr12
                          xterm: cannot load font "courr12"


                          (The xterm does come up and runs with a default, different font)



                          The fonts.alias file exists because of the long length of X11 font names. For example, courr12 is the short name for:



                          -adobe-courier-medium-r-normal--12-120-75-75-m-70-iso10646-1


                          [The long names are actually 14 different editable fields stitched together with dashes/hyphens. Run program xfontsel to see them; it will start with all fields showing with an asterisk, meaning not set to something specific.]



                          Each line in the file begins with a short name (an alias), a blank, then the long name it points/refers to. This way, you don't have to use the long name all the time, just set up an alias and use that. When putting a new line in the file, you decide what the short name will be, only the full X11 name has to have a font file installed on the system.



                          When I first cut my teeth on Unix systems in the 1990s, I ran across courr12 and later came to desire font it (Courier 'Roman' size 12) for my xterms. On HP/UX and Solaris, the fonts.alias file already had courr12, so I could just put "XTerm*font: courr12" in my .Xdefaults file and everything would work fine.






                          share|improve this answer

























                            up vote
                            0
                            down vote










                            up vote
                            0
                            down vote









                            What's missing are entries in the fonts.alias file:



                            /usr/share/X11/fonts/75dpi/fonts.alias


                            What this file does is provide short names ("aliases") for X Window fonts that are installed. When you try to use a short name that isn't in the file, you get behavior like this when starting xterm:



                            lansdale:~> xterm -xrm *font:courr12
                            xterm: cannot load font "courr12"


                            (The xterm does come up and runs with a default, different font)



                            The fonts.alias file exists because of the long length of X11 font names. For example, courr12 is the short name for:



                            -adobe-courier-medium-r-normal--12-120-75-75-m-70-iso10646-1


                            [The long names are actually 14 different editable fields stitched together with dashes/hyphens. Run program xfontsel to see them; it will start with all fields showing with an asterisk, meaning not set to something specific.]



                            Each line in the file begins with a short name (an alias), a blank, then the long name it points/refers to. This way, you don't have to use the long name all the time, just set up an alias and use that. When putting a new line in the file, you decide what the short name will be, only the full X11 name has to have a font file installed on the system.



                            When I first cut my teeth on Unix systems in the 1990s, I ran across courr12 and later came to desire font it (Courier 'Roman' size 12) for my xterms. On HP/UX and Solaris, the fonts.alias file already had courr12, so I could just put "XTerm*font: courr12" in my .Xdefaults file and everything would work fine.






                            share|improve this answer














                            What's missing are entries in the fonts.alias file:



                            /usr/share/X11/fonts/75dpi/fonts.alias


                            What this file does is provide short names ("aliases") for X Window fonts that are installed. When you try to use a short name that isn't in the file, you get behavior like this when starting xterm:



                            lansdale:~> xterm -xrm *font:courr12
                            xterm: cannot load font "courr12"


                            (The xterm does come up and runs with a default, different font)



                            The fonts.alias file exists because of the long length of X11 font names. For example, courr12 is the short name for:



                            -adobe-courier-medium-r-normal--12-120-75-75-m-70-iso10646-1


                            [The long names are actually 14 different editable fields stitched together with dashes/hyphens. Run program xfontsel to see them; it will start with all fields showing with an asterisk, meaning not set to something specific.]



                            Each line in the file begins with a short name (an alias), a blank, then the long name it points/refers to. This way, you don't have to use the long name all the time, just set up an alias and use that. When putting a new line in the file, you decide what the short name will be, only the full X11 name has to have a font file installed on the system.



                            When I first cut my teeth on Unix systems in the 1990s, I ran across courr12 and later came to desire font it (Courier 'Roman' size 12) for my xterms. On HP/UX and Solaris, the fonts.alias file already had courr12, so I could just put "XTerm*font: courr12" in my .Xdefaults file and everything would work fine.







                            share|improve this answer














                            share|improve this answer



                            share|improve this answer








                            edited Nov 15 at 20:41









                            Tomasz Jakub Rup

                            562313




                            562313










                            answered Nov 15 at 19:30









                            user855923

                            11




                            11






























                                 

                                draft saved


                                draft discarded



















































                                 


                                draft saved


                                draft discarded














                                StackExchange.ready(
                                function () {
                                StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f465142%2fhow-do-you-know-the-correct-name-to-use-for-x11-fonts-for-xtermfacename-or-xter%23new-answer', 'question_page');
                                }
                                );

                                Post as a guest















                                Required, but never shown





















































                                Required, but never shown














                                Required, but never shown












                                Required, but never shown







                                Required, but never shown

































                                Required, but never shown














                                Required, but never shown












                                Required, but never shown







                                Required, but never shown







                                Popular posts from this blog

                                Сан-Квентин

                                Алькесар

                                Josef Freinademetz