What is the least resource intensive way to generate the luatex font cache for a new font?Using MinionPro for the main font and Fontspec for the monospaced fontHow to generate compounded diacritical fonts for Sanskrit with XeTeX and LuaTeX?What is the .ttf font for default LaTeX font?how to set font feature file for a specific font file and not the whole font shapeWhat is the default font for LaTeX?What is the best Math Font for use with Minion Pro font?What is the least invasive way to set the font for listings?LuaLatex setup a different font for numbers and the restMaking a new font family based on the default fontWhat is the correct way to make setmainfont take effect?

How do you respond to a colleague from another team when they're wrongly expecting that you'll help them?

Could the E-bike drivetrain wear down till needing replacement after 400 km?

Is camera lens focus an exact point or a range?

If a character with the Alert feat rolls a crit fail on their Perception check, are they surprised?

What is the difference between "Do you interest" and "...interested in" something?

Why has "pence" been used in this sentence, not "pences"?

Can I use my Chinese passport to enter China after I acquired another citizenship?

Proving a function is onto where f(x)=|x|.

Did arcade monitors have same pixel aspect ratio as TV sets?

Is it improper etiquette to ask your opponent what his/her rating is before the game?

What's the difference between 違法 and 不法?

Is it better practice to read straight from sheet music rather than memorize it?

Diode in opposite direction?

When quoting, must I also copy hyphens used to divide words that continue on the next line?

How do ground effect vehicles perform turns?

Are lightweight LN wallets vulnerable to transaction withholding?

How much character growth crosses the line into breaking the character

Does having a TSA Pre-Check member in your flight reservation increase the chances that everyone gets Pre-Check?

Query about absorption line spectra

Two-sided logarithm inequality

How must one send away the mother bird?

My friend sent me a screenshot of a transaction hash, but when I search for it I find divergent data. What happened?

Open a doc from terminal, but not by its name

Should I install hardwood flooring or cabinets first?



What is the least resource intensive way to generate the luatex font cache for a new font?


Using MinionPro for the main font and Fontspec for the monospaced fontHow to generate compounded diacritical fonts for Sanskrit with XeTeX and LuaTeX?What is the .ttf font for default LaTeX font?how to set font feature file for a specific font file and not the whole font shapeWhat is the default font for LaTeX?What is the best Math Font for use with Minion Pro font?What is the least invasive way to set the font for listings?LuaLatex setup a different font for numbers and the restMaking a new font family based on the default fontWhat is the correct way to make setmainfont take effect?













10















When a font is first used with lualatex, luaotfload does some magic to produce font cache files.



For large fonts (e.g., Noto Sans CJK) this can take a lot of time and a lot of memory.



I have an old computer (5 year old MacBook air with 4GB RAM) running Linux with a 4GB swap partition. The initial cache generation of this font can take more than 15 min and render my computer unusable. Sometimes I just run out of memory and the process is killed.



Let's say I want to use the font as such:



documentclassarticle
usepackagefontspec
setmainfont[Script=CJK,Language=Chinese Simplified]Noto Sans CJK SC
begindocument
中文
enddocument


What is the least resource intensive way and/or fastest way to generate the required cache files?



At the moment, I quit everything (even X11) and run lualatex from the console, but it still takes a long time, and quitting everything is a bit of a pain.










share|improve this question

















  • 1





    That is a very good question, but I don't think you can do any better as you do now. Here is Hans' statement about this: mailman.ntg.nl/pipermail/ntg-context/2018/092703.html

    – Henri Menke
    Mar 16 at 7:49












  • xelatex might be an alternative if you don't need lua-specifics, just fontspec.

    – Joseph
    Mar 16 at 11:23











  • @Joseph, yes xelatex has no problems of course. Although I notice something curious with xelatex. I use the true type collection font: NotoSansCJK-Regular.ttc. When I run pdffonts on the the PDF file produced by xelatex it gives: ROREZJ+NotoSansCJKjp-Regular-Identity-H. (Notice jp for Japanese instead of sc for Simplified Chinese as requested). I don't know where the error is though. I guess it xelatex could be embedding the right font from the ttc but with the wrong name.

    – David Purton
    Mar 16 at 11:38











  • As an addition to my previous comment: I'm pretty sure the output is correct even though the font reported is always the jp one. All the language specific fonts contain all glyphs and the right language seems to be automatically used by xelatex when you request a language specific font without manually specifying the Language= option of fontspec.

    – David Purton
    Mar 16 at 13:11















10















When a font is first used with lualatex, luaotfload does some magic to produce font cache files.



For large fonts (e.g., Noto Sans CJK) this can take a lot of time and a lot of memory.



I have an old computer (5 year old MacBook air with 4GB RAM) running Linux with a 4GB swap partition. The initial cache generation of this font can take more than 15 min and render my computer unusable. Sometimes I just run out of memory and the process is killed.



Let's say I want to use the font as such:



documentclassarticle
usepackagefontspec
setmainfont[Script=CJK,Language=Chinese Simplified]Noto Sans CJK SC
begindocument
中文
enddocument


What is the least resource intensive way and/or fastest way to generate the required cache files?



At the moment, I quit everything (even X11) and run lualatex from the console, but it still takes a long time, and quitting everything is a bit of a pain.










share|improve this question

















  • 1





    That is a very good question, but I don't think you can do any better as you do now. Here is Hans' statement about this: mailman.ntg.nl/pipermail/ntg-context/2018/092703.html

    – Henri Menke
    Mar 16 at 7:49












  • xelatex might be an alternative if you don't need lua-specifics, just fontspec.

    – Joseph
    Mar 16 at 11:23











  • @Joseph, yes xelatex has no problems of course. Although I notice something curious with xelatex. I use the true type collection font: NotoSansCJK-Regular.ttc. When I run pdffonts on the the PDF file produced by xelatex it gives: ROREZJ+NotoSansCJKjp-Regular-Identity-H. (Notice jp for Japanese instead of sc for Simplified Chinese as requested). I don't know where the error is though. I guess it xelatex could be embedding the right font from the ttc but with the wrong name.

    – David Purton
    Mar 16 at 11:38











  • As an addition to my previous comment: I'm pretty sure the output is correct even though the font reported is always the jp one. All the language specific fonts contain all glyphs and the right language seems to be automatically used by xelatex when you request a language specific font without manually specifying the Language= option of fontspec.

    – David Purton
    Mar 16 at 13:11













10












10








10


2






When a font is first used with lualatex, luaotfload does some magic to produce font cache files.



For large fonts (e.g., Noto Sans CJK) this can take a lot of time and a lot of memory.



I have an old computer (5 year old MacBook air with 4GB RAM) running Linux with a 4GB swap partition. The initial cache generation of this font can take more than 15 min and render my computer unusable. Sometimes I just run out of memory and the process is killed.



Let's say I want to use the font as such:



documentclassarticle
usepackagefontspec
setmainfont[Script=CJK,Language=Chinese Simplified]Noto Sans CJK SC
begindocument
中文
enddocument


What is the least resource intensive way and/or fastest way to generate the required cache files?



At the moment, I quit everything (even X11) and run lualatex from the console, but it still takes a long time, and quitting everything is a bit of a pain.










share|improve this question














When a font is first used with lualatex, luaotfload does some magic to produce font cache files.



For large fonts (e.g., Noto Sans CJK) this can take a lot of time and a lot of memory.



I have an old computer (5 year old MacBook air with 4GB RAM) running Linux with a 4GB swap partition. The initial cache generation of this font can take more than 15 min and render my computer unusable. Sometimes I just run out of memory and the process is killed.



Let's say I want to use the font as such:



documentclassarticle
usepackagefontspec
setmainfont[Script=CJK,Language=Chinese Simplified]Noto Sans CJK SC
begindocument
中文
enddocument


What is the least resource intensive way and/or fastest way to generate the required cache files?



At the moment, I quit everything (even X11) and run lualatex from the console, but it still takes a long time, and quitting everything is a bit of a pain.







fonts luatex fontspec luaotfload






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Mar 16 at 4:44









David PurtonDavid Purton

10.9k2941




10.9k2941







  • 1





    That is a very good question, but I don't think you can do any better as you do now. Here is Hans' statement about this: mailman.ntg.nl/pipermail/ntg-context/2018/092703.html

    – Henri Menke
    Mar 16 at 7:49












  • xelatex might be an alternative if you don't need lua-specifics, just fontspec.

    – Joseph
    Mar 16 at 11:23











  • @Joseph, yes xelatex has no problems of course. Although I notice something curious with xelatex. I use the true type collection font: NotoSansCJK-Regular.ttc. When I run pdffonts on the the PDF file produced by xelatex it gives: ROREZJ+NotoSansCJKjp-Regular-Identity-H. (Notice jp for Japanese instead of sc for Simplified Chinese as requested). I don't know where the error is though. I guess it xelatex could be embedding the right font from the ttc but with the wrong name.

    – David Purton
    Mar 16 at 11:38











  • As an addition to my previous comment: I'm pretty sure the output is correct even though the font reported is always the jp one. All the language specific fonts contain all glyphs and the right language seems to be automatically used by xelatex when you request a language specific font without manually specifying the Language= option of fontspec.

    – David Purton
    Mar 16 at 13:11












  • 1





    That is a very good question, but I don't think you can do any better as you do now. Here is Hans' statement about this: mailman.ntg.nl/pipermail/ntg-context/2018/092703.html

    – Henri Menke
    Mar 16 at 7:49












  • xelatex might be an alternative if you don't need lua-specifics, just fontspec.

    – Joseph
    Mar 16 at 11:23











  • @Joseph, yes xelatex has no problems of course. Although I notice something curious with xelatex. I use the true type collection font: NotoSansCJK-Regular.ttc. When I run pdffonts on the the PDF file produced by xelatex it gives: ROREZJ+NotoSansCJKjp-Regular-Identity-H. (Notice jp for Japanese instead of sc for Simplified Chinese as requested). I don't know where the error is though. I guess it xelatex could be embedding the right font from the ttc but with the wrong name.

    – David Purton
    Mar 16 at 11:38











  • As an addition to my previous comment: I'm pretty sure the output is correct even though the font reported is always the jp one. All the language specific fonts contain all glyphs and the right language seems to be automatically used by xelatex when you request a language specific font without manually specifying the Language= option of fontspec.

    – David Purton
    Mar 16 at 13:11







1




1





That is a very good question, but I don't think you can do any better as you do now. Here is Hans' statement about this: mailman.ntg.nl/pipermail/ntg-context/2018/092703.html

– Henri Menke
Mar 16 at 7:49






That is a very good question, but I don't think you can do any better as you do now. Here is Hans' statement about this: mailman.ntg.nl/pipermail/ntg-context/2018/092703.html

– Henri Menke
Mar 16 at 7:49














xelatex might be an alternative if you don't need lua-specifics, just fontspec.

– Joseph
Mar 16 at 11:23





xelatex might be an alternative if you don't need lua-specifics, just fontspec.

– Joseph
Mar 16 at 11:23













@Joseph, yes xelatex has no problems of course. Although I notice something curious with xelatex. I use the true type collection font: NotoSansCJK-Regular.ttc. When I run pdffonts on the the PDF file produced by xelatex it gives: ROREZJ+NotoSansCJKjp-Regular-Identity-H. (Notice jp for Japanese instead of sc for Simplified Chinese as requested). I don't know where the error is though. I guess it xelatex could be embedding the right font from the ttc but with the wrong name.

– David Purton
Mar 16 at 11:38





@Joseph, yes xelatex has no problems of course. Although I notice something curious with xelatex. I use the true type collection font: NotoSansCJK-Regular.ttc. When I run pdffonts on the the PDF file produced by xelatex it gives: ROREZJ+NotoSansCJKjp-Regular-Identity-H. (Notice jp for Japanese instead of sc for Simplified Chinese as requested). I don't know where the error is though. I guess it xelatex could be embedding the right font from the ttc but with the wrong name.

– David Purton
Mar 16 at 11:38













As an addition to my previous comment: I'm pretty sure the output is correct even though the font reported is always the jp one. All the language specific fonts contain all glyphs and the right language seems to be automatically used by xelatex when you request a language specific font without manually specifying the Language= option of fontspec.

– David Purton
Mar 16 at 13:11





As an addition to my previous comment: I'm pretty sure the output is correct even though the font reported is always the jp one. All the language specific fonts contain all glyphs and the right language seems to be automatically used by xelatex when you request a language specific font without manually specifying the Language= option of fontspec.

– David Purton
Mar 16 at 13:11










1 Answer
1






active

oldest

votes


















10














You can do as proposed in section 9.2.1 “Trimming fonts“ in Fonts out of ConTeXt and remove all the glyph names in the font.



enter image description here



Adapted to LaTeX and your example:



documentclassarticle
usepackagefontspec,luacode
beginluacode*


fonts.handlers.otf.readers.registerextender 
name = "remove names from Noto Sans CJK SC",
action = function(fontdata)
if string.match(fontdata.metadata.fullname, "Noto Sans CJK SC") then
texio.write_nl("Trimming font " .. fontdata.metadata.fullname)
for k, v in next, fontdata.descriptions do
v.name = nil
end
end
end





endluacode*
setmainfont[Script=CJK,Language=Chinese Simplified]Noto Sans CJK SC
begindocument
中文
enddocument





share|improve this answer























  • Can this solution be problematic in some cases?

    – Paul Gaborit
    Mar 16 at 8:21











  • @PaulGaborit Yes, anything that wants to access glyphs by name won't work. In ConTeXt there is getnamedglyphdirect which will break. I don't think there is anything like this in LaTeX. Also those name lookups are not very efficient.

    – Henri Menke
    Mar 16 at 8:28












  • Well, I did manage to successfully generate cache files for Source Han Serif (regular, bold). Chromium was killed to compensate, used up all my RAM, and took half an hour! But it did work. Without your lua code I didn't manage to complete the compile without it being killed. So that's something.

    – David Purton
    Mar 16 at 10:57










Your Answer








StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "85"
;
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',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
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%2ftex.stackexchange.com%2fquestions%2f479744%2fwhat-is-the-least-resource-intensive-way-to-generate-the-luatex-font-cache-for-a%23new-answer', 'question_page');

);

Post as a guest















Required, but never shown

























1 Answer
1






active

oldest

votes








1 Answer
1






active

oldest

votes









active

oldest

votes






active

oldest

votes









10














You can do as proposed in section 9.2.1 “Trimming fonts“ in Fonts out of ConTeXt and remove all the glyph names in the font.



enter image description here



Adapted to LaTeX and your example:



documentclassarticle
usepackagefontspec,luacode
beginluacode*


fonts.handlers.otf.readers.registerextender 
name = "remove names from Noto Sans CJK SC",
action = function(fontdata)
if string.match(fontdata.metadata.fullname, "Noto Sans CJK SC") then
texio.write_nl("Trimming font " .. fontdata.metadata.fullname)
for k, v in next, fontdata.descriptions do
v.name = nil
end
end
end





endluacode*
setmainfont[Script=CJK,Language=Chinese Simplified]Noto Sans CJK SC
begindocument
中文
enddocument





share|improve this answer























  • Can this solution be problematic in some cases?

    – Paul Gaborit
    Mar 16 at 8:21











  • @PaulGaborit Yes, anything that wants to access glyphs by name won't work. In ConTeXt there is getnamedglyphdirect which will break. I don't think there is anything like this in LaTeX. Also those name lookups are not very efficient.

    – Henri Menke
    Mar 16 at 8:28












  • Well, I did manage to successfully generate cache files for Source Han Serif (regular, bold). Chromium was killed to compensate, used up all my RAM, and took half an hour! But it did work. Without your lua code I didn't manage to complete the compile without it being killed. So that's something.

    – David Purton
    Mar 16 at 10:57















10














You can do as proposed in section 9.2.1 “Trimming fonts“ in Fonts out of ConTeXt and remove all the glyph names in the font.



enter image description here



Adapted to LaTeX and your example:



documentclassarticle
usepackagefontspec,luacode
beginluacode*


fonts.handlers.otf.readers.registerextender 
name = "remove names from Noto Sans CJK SC",
action = function(fontdata)
if string.match(fontdata.metadata.fullname, "Noto Sans CJK SC") then
texio.write_nl("Trimming font " .. fontdata.metadata.fullname)
for k, v in next, fontdata.descriptions do
v.name = nil
end
end
end





endluacode*
setmainfont[Script=CJK,Language=Chinese Simplified]Noto Sans CJK SC
begindocument
中文
enddocument





share|improve this answer























  • Can this solution be problematic in some cases?

    – Paul Gaborit
    Mar 16 at 8:21











  • @PaulGaborit Yes, anything that wants to access glyphs by name won't work. In ConTeXt there is getnamedglyphdirect which will break. I don't think there is anything like this in LaTeX. Also those name lookups are not very efficient.

    – Henri Menke
    Mar 16 at 8:28












  • Well, I did manage to successfully generate cache files for Source Han Serif (regular, bold). Chromium was killed to compensate, used up all my RAM, and took half an hour! But it did work. Without your lua code I didn't manage to complete the compile without it being killed. So that's something.

    – David Purton
    Mar 16 at 10:57













10












10








10







You can do as proposed in section 9.2.1 “Trimming fonts“ in Fonts out of ConTeXt and remove all the glyph names in the font.



enter image description here



Adapted to LaTeX and your example:



documentclassarticle
usepackagefontspec,luacode
beginluacode*


fonts.handlers.otf.readers.registerextender 
name = "remove names from Noto Sans CJK SC",
action = function(fontdata)
if string.match(fontdata.metadata.fullname, "Noto Sans CJK SC") then
texio.write_nl("Trimming font " .. fontdata.metadata.fullname)
for k, v in next, fontdata.descriptions do
v.name = nil
end
end
end





endluacode*
setmainfont[Script=CJK,Language=Chinese Simplified]Noto Sans CJK SC
begindocument
中文
enddocument





share|improve this answer













You can do as proposed in section 9.2.1 “Trimming fonts“ in Fonts out of ConTeXt and remove all the glyph names in the font.



enter image description here



Adapted to LaTeX and your example:



documentclassarticle
usepackagefontspec,luacode
beginluacode*


fonts.handlers.otf.readers.registerextender 
name = "remove names from Noto Sans CJK SC",
action = function(fontdata)
if string.match(fontdata.metadata.fullname, "Noto Sans CJK SC") then
texio.write_nl("Trimming font " .. fontdata.metadata.fullname)
for k, v in next, fontdata.descriptions do
v.name = nil
end
end
end





endluacode*
setmainfont[Script=CJK,Language=Chinese Simplified]Noto Sans CJK SC
begindocument
中文
enddocument






share|improve this answer












share|improve this answer



share|improve this answer










answered Mar 16 at 8:08









Henri MenkeHenri Menke

77k8170284




77k8170284












  • Can this solution be problematic in some cases?

    – Paul Gaborit
    Mar 16 at 8:21











  • @PaulGaborit Yes, anything that wants to access glyphs by name won't work. In ConTeXt there is getnamedglyphdirect which will break. I don't think there is anything like this in LaTeX. Also those name lookups are not very efficient.

    – Henri Menke
    Mar 16 at 8:28












  • Well, I did manage to successfully generate cache files for Source Han Serif (regular, bold). Chromium was killed to compensate, used up all my RAM, and took half an hour! But it did work. Without your lua code I didn't manage to complete the compile without it being killed. So that's something.

    – David Purton
    Mar 16 at 10:57

















  • Can this solution be problematic in some cases?

    – Paul Gaborit
    Mar 16 at 8:21











  • @PaulGaborit Yes, anything that wants to access glyphs by name won't work. In ConTeXt there is getnamedglyphdirect which will break. I don't think there is anything like this in LaTeX. Also those name lookups are not very efficient.

    – Henri Menke
    Mar 16 at 8:28












  • Well, I did manage to successfully generate cache files for Source Han Serif (regular, bold). Chromium was killed to compensate, used up all my RAM, and took half an hour! But it did work. Without your lua code I didn't manage to complete the compile without it being killed. So that's something.

    – David Purton
    Mar 16 at 10:57
















Can this solution be problematic in some cases?

– Paul Gaborit
Mar 16 at 8:21





Can this solution be problematic in some cases?

– Paul Gaborit
Mar 16 at 8:21













@PaulGaborit Yes, anything that wants to access glyphs by name won't work. In ConTeXt there is getnamedglyphdirect which will break. I don't think there is anything like this in LaTeX. Also those name lookups are not very efficient.

– Henri Menke
Mar 16 at 8:28






@PaulGaborit Yes, anything that wants to access glyphs by name won't work. In ConTeXt there is getnamedglyphdirect which will break. I don't think there is anything like this in LaTeX. Also those name lookups are not very efficient.

– Henri Menke
Mar 16 at 8:28














Well, I did manage to successfully generate cache files for Source Han Serif (regular, bold). Chromium was killed to compensate, used up all my RAM, and took half an hour! But it did work. Without your lua code I didn't manage to complete the compile without it being killed. So that's something.

– David Purton
Mar 16 at 10:57





Well, I did manage to successfully generate cache files for Source Han Serif (regular, bold). Chromium was killed to compensate, used up all my RAM, and took half an hour! But it did work. Without your lua code I didn't manage to complete the compile without it being killed. So that's something.

– David Purton
Mar 16 at 10:57

















draft saved

draft discarded
















































Thanks for contributing an answer to TeX - LaTeX Stack Exchange!


  • Please be sure to answer the question. Provide details and share your research!

But avoid


  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.

To learn more, see our tips on writing great answers.




draft saved


draft discarded














StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2ftex.stackexchange.com%2fquestions%2f479744%2fwhat-is-the-least-resource-intensive-way-to-generate-the-luatex-font-cache-for-a%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

How should I support this large drywall patch? Planned maintenance scheduled April 23, 2019 at 00:00UTC (8:00pm US/Eastern) Announcing the arrival of Valued Associate #679: Cesar Manara Unicorn Meta Zoo #1: Why another podcast?How do I cover large gaps in drywall?How do I keep drywall around a patch from crumbling?Can I glue a second layer of drywall?How to patch long strip on drywall?Large drywall patch: how to avoid bulging seams?Drywall Mesh Patch vs. Bulge? To remove or not to remove?How to fix this drywall job?Prep drywall before backsplashWhat's the best way to fix this horrible drywall patch job?Drywall patching using 3M Patch Plus Primer

random experiment with two different functions on unit interval Announcing the arrival of Valued Associate #679: Cesar Manara Planned maintenance scheduled April 23, 2019 at 00:00UTC (8:00pm US/Eastern)Random variable and probability space notionsRandom Walk with EdgesFinding functions where the increase over a random interval is Poisson distributedNumber of days until dayCan an observed event in fact be of zero probability?Unit random processmodels of coins and uniform distributionHow to get the number of successes given $n$ trials , probability $P$ and a random variable $X$Absorbing Markov chain in a computer. Is “almost every” turned into always convergence in computer executions?Stopped random walk is not uniformly integrable

Lowndes Grove History Architecture References Navigation menu32°48′6″N 79°57′58″W / 32.80167°N 79.96611°W / 32.80167; -79.9661132°48′6″N 79°57′58″W / 32.80167°N 79.96611°W / 32.80167; -79.9661178002500"National Register Information System"Historic houses of South Carolina"Lowndes Grove""+32° 48' 6.00", −79° 57' 58.00""Lowndes Grove, Charleston County (260 St. Margaret St., Charleston)""Lowndes Grove"The Charleston ExpositionIt Happened in South Carolina"Lowndes Grove (House), Saint Margaret Street & Sixth Avenue, Charleston, Charleston County, SC(Photographs)"Plantations of the Carolina Low Countrye