Movatterモバイル変換

[0]ホーム
URL:

Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

 Sign up
Appearance settings

Commit4d15637

Browse files
committed
Doc: fix remaining over-length entries in SQL keywords table.
Even after the tweaking I did in commit5545b69, some of thelonger keywords mentioned in the SQL standard don't fit theavailable space in PDF output.I experimented with various solutions like putting such keywordson their own table lines, but everything looked ugly or confusingor both; worse, the weirdness also appeared in the HTML version,which (normally) doesn't need it.The best answer seems to be to insert &zwsp; into long keywordsso that they can be broken into two lines when, and only when,needed. It doesn't look too awful if the break happens afteran underscore --- and fortunately, all the problematic keywordshave underscores.Discussion:https://postgr.es/m/6916.1589146280@sss.pgh.pa.us
1 parent60c90c1 commit4d15637

File tree

1 file changed

+6
-1
lines changed

1 file changed

+6
-1
lines changed

‎doc/src/sgml/generate-keywords-table.pl

Lines changed: 6 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -82,8 +82,13 @@ END
8282

8383
foreachmy$word (sortkeys%keywords)
8484
{
85+
# Insert zwsp's into very long keywords, so that they can be broken
86+
# into multiple lines in PDF format (or narrow HTML windows).
87+
my$printword =$word;
88+
$printword =~s/_/_&zwsp;/gif (length($printword) > 20);
89+
8590
print" <row>\n";
86-
print" <entry><token>$word</token></entry>\n";
91+
print" <entry><token>$printword</token></entry>\n";
8792

8893
print" <entry>";
8994
if ($keywords{$word}{pg}{'unreserved'})

0 commit comments

Comments
 (0)
[8]ページ先頭
©2009-2025 Movatter.jp