Created attachment 149211 [details]
actual

Created attachment 149213 [details]
expected

Created attachment 149214 [details]
bugdoc compared OO and LO 6.3+

Seems to me that text was always bold. No repro not bold. Test in Windows.

Maybe it's Linux only, at least OpenOffice 3.2 on Linux displayed the text non-bold (as shown in attachment 149213 [details]).

I can't reproduce it in

Versión: 6.2.0.3
Id. de compilación: 98c6a8a1c6c7b144ce3cc729e34964b47ce25d62
Subprocs. CPU: 1; SO: Windows 6.1; Repres. IU: predet.; VCL: win; 
Configuración regional: es-ES (es_ES); Idioma de IU: es-ES
Calc: threaded

nor in

Versió: 6.1.4.2
ID de la construcció: 1:6.1.4-0ubuntu0.16.04.1~lo2
Fils de CPU: 4; SO: Linux 4.15; Renderitzador de la IU: per defecte; VCL: gtk3; 
Configuració local: ca-ES (ca_ES.UTF-8); Calc: group threaded

however, using the bisect repositories i can reproduce it in

Version: 6.3.0.0.alpha0+
Build ID: c7ad7849d54fd3dad67e7779102f65b8b2f04881
CPU threads: 4; OS: Linux 4.15; UI render: default; VCL: gtk3; 
Locale: ca-ES (ca_ES.UTF-8); UI-Language: en-US
Calc: threaded

and

Version: 4.4.0.0.alpha0+
Build ID: ffeb03625f31fd3a88b7c0f0bccf57d0aeeca25c

only reproducible in development enviroments ??

There is a difference in LibreoOffice 6.1.4.2 TDF version vs Ubuntu version.
In the Ubuntu version it is shown as non-bold while in the TDF version it is shown as bold.

michaelweghorn> for me, text of tdf#123397 doc is shown in bold with libreoffice package 1:6.1.5~rc1-2  in debian testing

content.xml:

            <text:p text:style-name="P8">01<text:tab/>Wohnsitz des Antragsgegners oder eines Mitantragsgegners</text:p>

    <style:style style:name="P8" style:family="paragraph" style:parent-style-name="Table_20_Contents">
      <style:paragraph-properties fo:text-align="justify" style:justify-single-word="false">
        <style:tab-stops>
          <style:tab-stop style:position="0.397cm"/>
        </style:tab-stops>
      </style:paragraph-properties>
    </style:style>

styles.xml:
    <style:font-face style:name="Arial1" svg:font-family="Arial" style:font-adornments="Standard" style:font-family-generic="swiss" style:font-pitch="variable"/>

    <style:style style:name="Table_20_Contents" style:display-name="Table Contents" style:family="paragraph" style:parent-style-name="Standard" style:class="extra">
      <style:text-properties style:font-name="Arial1" fo:font-size="7pt" fo:font-weight="normal"/>
    </style:style>




so we have style:font-adornments="Standard" and fo:font-weight="normal", i don't see where the bold is supposed to come from?

styles.xml:

    <style:style style:name="Standard" style:family="paragraph" style:class="text" style:master-page-name="">
      <style:text-properties style:font-name="Arial Black" fo:font-size="10pt" fo:font-weight="900"/>
    </style:style>

somehow the fo:font-weight="900" of the parent style "Standard" is not overwritten by the fo:font-weight="normal" of the derived style "Table Contents".

if you use e.g. de_DE locale, you get "Regular" font weight.

but with en_US you get "Black" font weight.

the problem is that this style:

    <style:style style:name="Table_20_Contents_20__28_user_29_" style:display-name="Table Contents (user)" style:family="paragraph" style:parent-style-name="Standard">
      <style:paragraph-properties ns3:contextual-spacing="false" fo:margin-top="0.049cm" fo:margin-bottom="0.049cm" style:vertical-align="middle"/>
      <style:text-properties style:font-name="Arial" fo:font-size="7.5pt" style:font-name-complex="Arial" style:font-size-complex="7.5pt"/>
    </style:style>


"Table Contents (user)" will be mapped to the same internal SwTextFormatColl as the built-in style "Table Contents", but *only* if it matches the locale's translation of "Table Contents".

this could be fixed by:

1) reworking SwFormat etc. (haven't checked which of the 5-6 classes are actually subclasses of SwFormat) in Writer document model so it stores the "programmatic name" (as used in ODF/other file formats) instead of the "UIName" that is shown in the UI, and then moving the FillUIName / FillProgName conversions out of the "unocore" classes and into all UI classes that display style names.

2) making use of the SwFormat's m_nPoolFormatIds as a second part of the lookup key, so that we can store styles with same name but one has a pool-id and the other does not; not sure which/how many places would need to know whether they want a pool-style or not though.

either of these is a bit of work; anything simpler looks like it's going to cause some kind of problem or other...