Project

General

Profile

Bug #16221

Consider stopping to use DocBook-style CSS classes

Added by sajolida 9 months ago. Updated 21 days ago.

Status:
Confirmed
Priority:
Normal
Assignee:
Category:
Internationalization
Target version:
-
Start date:
12/13/2018
Due date:
% Done:

0%

Feature Branch:
Type of work:
Discuss
Blueprint:
Starter:
Affected tool:

Description

See http://lists.autistici.org/message/20181118.155100.286e6cc2.en.html.

We should remove this from our documentation guidelines.


Related issues

Related to Tails - Feature #16279: Research how to isolate the [[!meta directives that need translation in PO files Resolved 01/04/2019
Blocked by Tails - Feature #10034: Translation web platform Resolved 08/14/2015
Blocks Tails - Feature #16711: Core work 2019Q3 → 2019Q4: Technical writing Confirmed 01/08/2016
Blocked by Tails - Bug #16943: Upgrade to Weblate 3.x Confirmed

History

#1 Updated by sajolida 9 months ago

  • Blocks Feature #15941: Core work 2018Q4 → 2019Q2: Technical writing added

#2 Updated by sajolida 9 months ago

  • Subject changed from Stop using DocBook-style CSS classes to Consider stopping to use DocBook-style CSS classes

#3 Updated by sajolida 9 months ago

  • Type of work changed from Contributors documentation to Discuss

#4 Updated by sajolida 9 months ago

  • Related to Feature #16279: Research how to isolate the [[!meta directives that need translation in PO files added

#5 Updated by sajolida 9 months ago

emmapeel summarized the issue very well on the thread:

**Applications > Tails > Configure persistent storage**

Instead of:

<span class="guimenu">Applications</span>&nbsp;>
  <span class="guisubmenu">Tails</span>&nbsp;>
  <span class="guimenuitem">Configure persistent storage</span>
</span>
  • Markdown seems to be much more understandable.
  • Translators are less likely to make errors with the first version. But if they do make errors, Weblate will be able to spot the HTML errors better than the markdown ones.

#6 Updated by sajolida 9 months ago

  • Description updated (diff)

#7 Updated by sajolida 8 months ago

  • Target version changed from Tails_3.12 to Tails_3.13

We'll discuss at FOSDEM with Weblate whether they could implement validation of Markdown as this would solve the concerns raised by emmapeel and ignifugo about translators messing up with Markdown. Other projects looking into Weblate to translate markdown are also really interested in this.

#8 Updated by sajolida 8 months ago

#9 Updated by sajolida 7 months ago

#10 Updated by sajolida 7 months ago

The checks will make sure that the same Markdown are used in the original string and the translations, so this will solve our problem.

I'm marking this as blocked by the translation platform.

#11 Updated by sajolida 7 months ago

  • Blocks deleted (Feature #15941: Core work 2018Q4 → 2019Q2: Technical writing)

#12 Updated by sajolida 6 months ago

  • Target version changed from Tails_3.13 to Tails_3.14

#13 Updated by CyrilBrulebois 4 months ago

  • Target version changed from Tails_3.14 to Tails_3.15

#14 Updated by sajolida 2 months ago

  • Blocks Feature #16711: Core work 2019Q3 → 2019Q4: Technical writing added

#15 Updated by CyrilBrulebois 2 months ago

  • Target version changed from Tails_3.15 to Tails_3.16

#16 Updated by sajolida about 2 months ago

  • Target version changed from Tails_3.16 to Tails_3.17

If I understand correctly:

So I'll bump this ticket into to the future.

#17 Updated by sajolida about 1 month ago

  • Blocked by Bug #16943: Upgrade to Weblate 3.x added

#18 Updated by sajolida 21 days ago

  • Target version deleted (Tails_3.17)

Also available in: Atom PDF