Giter VIP home page Giter VIP logo

Comments (15)

fmherschel avatar fmherschel commented on August 22, 2024

In section "5.2 Installation" some paragraphs begin with a plus sign (+). In our adoc the plus has
been added, because we tell adoc to keep the indentation also after examples.

Also the titles of examples are damaged. And they begin with a plus sign and are formatted as paragraphs instead of titles.

Examples:
"+ .The XML password template", "+ .Using hdblcm in batch mode" (Examples for damaged titles)
"+ After having created the XML..." (Example for damaged paragraph)

Best,
Fabian

from suse-best-practices.

chabowski avatar chabowski commented on August 22, 2024

While I was able to solve some document internal problems regarding variable replacement we still
have two variables referenced by common_gfdl1.2_i.adoc. The missing variables are: {ldquo} and {rdquo}.

After discussing with Tom, we decided to replace these variables (which are indeed only quotation marks) with clear text, as variables are not really needed here.

from suse-best-practices.

fmherschel avatar fmherschel commented on August 22, 2024

+1

from suse-best-practices.

fmherschel avatar fmherschel commented on August 22, 2024

About the second topic - I only added the second topic, because github disallowed me to open an own issue for that (the apply button keeps gray):
Do you like me to send you (via mail) to screenshots of the "original" typesetting in our build and the
screenshot of the build document available online?

from suse-best-practices.

chabowski avatar chabowski commented on August 22, 2024

Yes that might be helpful. I am still "investigating" - it most probably is a conversion bug but I don't know yet why.

from suse-best-practices.

fmherschel avatar fmherschel commented on August 22, 2024

send the screenshots via eMail

from suse-best-practices.

chabowski avatar chabowski commented on August 22, 2024

Yes - got them, thank you Fabian! I am struggling to find the bug/issue - our build does it correctly in Example 7 but fails starting with Example 8 (which as far as I can see uses the same structure with the + like Example 7 ... ). But we will get there - I will ask Frank to have a look at it tomorrow morning ...

from suse-best-practices.

chabowski avatar chabowski commented on August 22, 2024

@fmherschel: we found the issue, it was a simple formatting issue. The bullet list above the two examples that did not show up correctly is now in an open block, the example titles show up correctly and the examples also have the correct indentation now.

from suse-best-practices.

fmherschel avatar fmherschel commented on August 22, 2024

Are the changes for this issue and also the problem solution for ldquo/rdquo committed to the project? Currently I do not see the commit. I would like to rebase/refork the project to test a rebuild.

from suse-best-practices.

chabowski avatar chabowski commented on August 22, 2024

The ldquo/rdquo is under commit 2055e1b.
The format issue is not yet committed, as I am fixing some other stuff and wanted to do one single commit for the changes. But I can commit it now (commit will contain some other stuff though in addition).

from suse-best-practices.

chabowski avatar chabowski commented on August 22, 2024

commit 56374a8 contains the solution for the format issue that caused the buggy display of the example titles. It also contains the fix of an outdated link, and replacement of abbreviation SLES with SUSE Linux Enterprise Server (there is a policy that there should not be product name abbreviations in plain text). I will give the paper another review tomorrow though before publication.

from suse-best-practices.

fmherschel avatar fmherschel commented on August 22, 2024

@chabowski: Did you have had a chance to review the paper and to publish it? Today I still got the old version from the sle12 docu page. Do you like to send us (Bernd and me) a build pdf just before publishing it?

from suse-best-practices.

chabowski avatar chabowski commented on August 22, 2024

@fmherschel, @pirat013
SLES4SAP-hana-scaleOut-PerfOpt-12_color_en.pdf

  • hmm seems the latest version I sent was on Thurs evening - sorry I meant to send another one on Mon and was wondering why I didn't hear back. You should have a current version in your inbox, but I just built a new one - see attached.

from suse-best-practices.

fmherschel avatar fmherschel commented on August 22, 2024

I think we could close this issue right now.

from suse-best-practices.

chabowski avatar chabowski commented on August 22, 2024

Sounds good - thank you :-)

from suse-best-practices.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.