View Issue Details

IDProjectCategoryView StatusLast Update
0034900FPCDocumentationpublic2019-01-19 16:25
ReporterKai BurghardtAssigned ToMichael Van Canneyt 
PrioritynormalSeverityminorReproducibilityalways
Status resolvedResolutionfixed 
Platformx86_64OSGNU/LinuxOS Version4.2.0
Product Version3.0.4Product Build3.0.4+dfsg-11 [2017/12/30] 
Target Version3.2.0Fixed in Version3.3.1 
Summary0034900: Programmer's guide: section name in context of resourcestrings doesn't make sense
DescriptionAn example in the context of the resourcestrings deals with a string that ought to be translated. However, it is defined in a const section, not in a resourcestring section.
Additional InformationFurthermore TranslateStrings is not defined in the gettext unit, but I guess the example code's purpose is only to demonstrate _the_ _principle_, so it's OK. We don't wanna "dictate" people to use gettext.
Tagsdocumentation
Fixed in Revision1537
FPCOldBugId
FPCTarget
Attached Files
  • prog.tex.patch (646 bytes)
    --- prog.tex~	2019-01-19 00:18:00.265466677 +0000
    +++ prog.tex	2019-01-19 00:18:00.265466677 +0000
    @@ -6180,57 +6180,57 @@
     
     \section{Caveat}
     In principle it is possible to translate all resource strings at any time in
     a running program. However, this change is not communicated to other
     strings; its change is noticed only when a constant string is being used.
     
     Consider the following example:
     \begin{verbatim}
    -Const
    +Resourcestring
       help = 'With a little help of a programmer.';
     
     Var
       A : AnsiString;
     
     
     begin
     
       { lots of code }
     
       A:=Help;
     
       { Again some code}
     
       TranslateStrings;
     
       { More code }
     \end{verbatim}
    
    prog.tex.patch (646 bytes)

Activities

Kai Burghardt

2019-01-19 01:27

reporter  

prog.tex.patch (646 bytes)
--- prog.tex~	2019-01-19 00:18:00.265466677 +0000
+++ prog.tex	2019-01-19 00:18:00.265466677 +0000
@@ -6180,57 +6180,57 @@
 
 \section{Caveat}
 In principle it is possible to translate all resource strings at any time in
 a running program. However, this change is not communicated to other
 strings; its change is noticed only when a constant string is being used.
 
 Consider the following example:
 \begin{verbatim}
-Const
+Resourcestring
   help = 'With a little help of a programmer.';
 
 Var
   A : AnsiString;
 
 
 begin
 
   { lots of code }
 
   A:=Help;
 
   { Again some code}
 
   TranslateStrings;
 
   { More code }
 \end{verbatim}
prog.tex.patch (646 bytes)

Michael Van Canneyt

2019-01-19 16:25

administrator   ~0113482

Fixed manually, patch for some reason didn't apply :(

Thanks for the fix !

Issue History

Date Modified Username Field Change
2019-01-19 01:27 Kai Burghardt New Issue
2019-01-19 01:27 Kai Burghardt Status new => assigned
2019-01-19 01:27 Kai Burghardt Assigned To => Michael Van Canneyt
2019-01-19 01:27 Kai Burghardt File Added: prog.tex.patch
2019-01-19 01:27 Kai Burghardt Tag Attached: documentation
2019-01-19 16:25 Michael Van Canneyt Fixed in Revision => 1537
2019-01-19 16:25 Michael Van Canneyt Note Added: 0113482
2019-01-19 16:25 Michael Van Canneyt Status assigned => resolved
2019-01-19 16:25 Michael Van Canneyt Fixed in Version => 3.3.1
2019-01-19 16:25 Michael Van Canneyt Resolution open => fixed
2019-01-19 16:25 Michael Van Canneyt Target Version => 3.2.0