kcachegrind_qt - en to en_GB translation catalogue (22 entries)

[ctx: CallGraphView|]
en: <b>Call Graph around active Function</b><p>Depending on configuration, this view shows the call graph environment of the active function. Note: the shown cost is <b>only</b> the cost which is spent while the active function was actually running; i.e. the cost shown for main() - if it is visible - should be the same as the cost of the active function, as that is the part of inclusive cost of main() spent while the active function was running.</p><p>For cycles, blue call arrows indicate that this is an artificial call added for correct drawing which actually never happened.</p><p>If the graph is larger than the widget area, an overview panner is shown in one edge. There are similar visualization options to the Call Treemap; the selected function is highlighted.</p>
en_GB: <b>Call Graph around active Function</b><p>Depending on configuration, this view shows the call graph environment of the active function. Note: the shown cost is <b>only</b> the cost which is spent while the active function was actually running; i.e. the cost shown for main() - if it is visible - should be the same as the cost of the active function, as that is the part of inclusive cost of main() spent while the active function was running.</p><p>For cycles, blue call arrows indicate that this is an artificial call added for correct drawing which actually never happened.</p><p>If the graph is larger than the widget area, an overview panner is shown in one edge. There are similar visualisation options to the Call Treemap; the selected function is highlighted.</p>

[ctx: CallGraphView|]
en: Warning: a long lasting graph layouting is in progress.
    Reduce node/edge limits for speedup.
en_GB: Warning: a long lasting graph laying out is in progress.
    Reduce node/edge limits for speed up.

[ctx: CallGraphView|]
en: Layouting stopped.
en_GB: Laying out stopped.

[ctx: CallGraphView|]
en: No graph available because the layouting process failed.
en_GB: No graph available because the laying out process failed.

[ctx: CallGraphView|]
en: Error running the graph layouting tool.
en_GB: Error running the graph layout tool.

[ctx: CallGraphView|]
en: Stop Layouting
en_GB: Stop laying out

[ctx: CallGraphView|]
en: Visualization
en_GB: Visualisation

[ctx: CallMapView|]
en: <b>Caller Map</b><p>This graph shows the nested hierarchy of all callers of the current activated function. Each colored rectangle represents a function; its size tries to be proportional to the cost spent therein while the active function is running (however, there are drawing constraints).</p>
en_GB: <b>Caller Map</b><p>This graph shows the nested hierarchy of all callers of the current activated function. Each coloured rectangle represents a function; its size tries to be proportional to the cost spent therein while the active function is running (however, there are drawing constraints).</p>

[ctx: CallMapView|]
en: <b>Call Map</b><p>This graph shows the nested hierarchy of all callees of the current activated function. Each colored rectangle represents a function; its size tries to be proportional to the cost spent therein while the active function is running (however, there are drawing constraints).</p>
en_GB: <b>Call Map</b><p>This graph shows the nested hierarchy of all callees of the current activated function. Each coloured rectangle represents a function; its size tries to be proportional to the cost spent therein while the active function is running (however, there are drawing constraints).</p>

[ctx: CallMapView|]
en: <p>Appearance options can be found in the context menu. To get exact size proportions, choose 'Hide incorrect borders'. As this mode can be <em>very</em> time consuming, you may want to limit the maximum drawn nesting level before. 'Best' determinates the split direction for children from the aspect ratio of the parent. 'Always Best' decides on remaining space for each sibling. 'Ignore Proportions' takes space for function name drawing <em>before</em> drawing children. Note that size proportions can get <em>heavily</em> wrong.</p><p>This is a <em>TreeMap</em> widget. Keyboard navigation is available with the left/right arrow keys for traversing siblings, and up/down arrow keys to go a nesting level up/down. <em>Return</em> activates the current item.</p>
en_GB: <p>Appearance options can be found in the context menu. To get exact size proportions, choose 'Hide incorrect borders'. As this mode can be <em>very</em> time consuming, you may want to limit the maximum drawn nesting level before. 'Best' determines the split direction for children from the aspect ratio of the parent. 'Always Best' decides on remaining space for each sibling. 'Ignore Proportions' takes space for function name drawing <em>before</em> drawing children. Note that size proportions can get <em>heavily</em> wrong.</p><p>This is a <em>TreeMap</em> widget. Keyboard navigation is available with the left/right arrow keys for traversing siblings, and up/down arrow keys to go a nesting level up/down. <em>Return</em> activates the current item.</p>

[ctx: CallMapView|]
en: Visualization
en_GB: Visualisation

[ctx: QObject|]
en: There are %1 cost line(s) without machine code.
    This happens because the code of %2 does not seem to match the profile data file.
    Are you using an old profile data file or is the abovementioned
    ELF object from an updated installation/another machine?
en_GB: There are %1 cost line(s) without machine code.
    This happens because the code of %2 does not seem to match the profile data file.
    Are you using an old profile data file or is the above mentioned
    ELF object from an updated installation/another machine?

[ctx: QObject|]
en: (%n item(s) skipped) | (%n item(s) skipped)
en_GB[0]: (%n item skipped)
en_GB[1]: (%n items skipped)

[ctx: QObject|]
en: (%n function(s) skipped) | (%n function(s) skipped)
en_GB[0]: (%n function skipped)
en_GB[1]: (%n functions skipped)

[ctx: CoverageView|]
en: <b>List of all Callers</b><p>This list shows all functions calling the current selected one, either directly or with several functions in-between on the stack; the number of functions in-between plus one is called the <em>Distance</em> (e.g. for function A,B,C there exists a call from A to C when A calls B and B calls C, i.e. A => B => C. The distance here is 2).</p><p>Absolute cost shown is the cost spent in the selected function while a listed function is active; relative cost is the percentage of all cost spent in the selected function while the listed one is active. The cost graphic shows logarithmic percentage with a different color for each distance.</p><p>As there can be many calls from the same function, the distance column sometimes shows the range of distances for all calls happening; then, in parentheses, there is the medium distance, i.e. the distance where most of the call costs happened.</p><p>Selecting a function makes it the current selected one of this information panel. If there are two panels (Split mode), the function of the other panel is changed instead.</p>
en_GB: <b>List of all Callers</b><p>This list shows all functions calling the current selected one, either directly or with several functions in-between on the stack; the number of functions in-between plus one is called the <em>Distance</em> (e.g. for function A,B,C there exists a call from A to C when A calls B and B calls C, i.e. A => B => C. The distance here is 2).</p><p>Absolute cost shown is the cost spent in the selected function while a listed function is active; relative cost is the percentage of all cost spent in the selected function while the listed one is active. The cost graphic shows logarithmic percentage with a different colour for each distance.</p><p>As there can be many calls from the same function, the distance column sometimes shows the range of distances for all calls happening; then, in brackets, there is the medium distance, i.e. the distance where most of the call costs happened.</p><p>Selecting a function makes it the current selected one of this information panel. If there are two panels (Split mode), the function of the other panel is changed instead.</p>

[ctx: CoverageView|]
en: <b>List of all Callees</b><p>This list shows all functions called by the current selected one, either directly or with several function in-between on the stack; the number of function in-between plus one is called the <em>Distance</em> (e.g. for function A,B,C there exists a call from A to C when A calls B and B calls C, i.e. A => B => C. The distance here is 2).</p><p>Absolute cost shown is the cost spent in the listed function while the selected is active; relative cost is the percentage of all cost spent in the listed function while the selected one is active. The cost graphic always shows logarithmic percentage with a different color for each distance.</p><p>As there can be many calls to the same function, the distance column sometimes shows the range of distances for all calls happening; then, in parentheses, there is the medium distance, i.e. the distance where most of the call costs happened.</p><p>Selecting a function makes it the current selected one of this information panel. If there are two panels (Split mode), the function of the other panel is changed instead.</p>
en_GB: <b>List of all Callees</b><p>This list shows all functions called by the current selected one, either directly or with several function in-between on the stack; the number of function in-between plus one is called the <em>Distance</em> (e.g. for function A,B,C there exists a call from A to C when A calls B and B calls C, i.e. A => B => C. The distance here is 2).</p><p>Absolute cost shown is the cost spent in the listed function while the selected is active; relative cost is the percentage of all cost spent in the listed function while the selected one is active. The cost graphic always shows logarithmic percentage with a different colour for each distance.</p><p>As there can be many calls to the same function, the distance column sometimes shows the range of distances for all calls happening; then, in brackets, there is the medium distance, i.e. the distance where most of the call costs happened.</p><p>Selecting a function makes it the current selected one of this information panel. If there are two panels (Split mode), the function of the other panel is changed instead.</p>

[ctx: QObject|]
en: %n call(s) to '%2' | %n call(s) to '%2'
en_GB[0]: %n call to '%2'
en_GB[1]: %n calls to '%2'

[ctx: InstrView|]
en: There are %n cost line(s) without machine code. | There are %n cost line(s) without machine code.
en_GB[0]: There is %n cost line without machine code.
en_GB[1]: There are %n cost lines without machine code.

[ctx: PartSelection|]
en: <b>The Parts Overview</b><p>A trace consists of multiple trace parts when there are several profile data files from one profile run. The Trace Part Overview dockable shows these, horizontally ordered in execution time; the rectangle sizes are proportional to the total cost spent in the parts. You can select one or several parts to constrain all costs shown to these parts only.</p><p>The parts are further subdivided: there is a partitioning and an callee split mode: <ul><li>Partitioning: You see the partitioning into groups for a trace part, according to the group type selected. E.g. if ELF object groups are selected, you see colored rectangles for each used ELF object (shared library or executable), sized according to the cost spent therein.</li><li>Callee: A rectangle showing the inclusive cost of the current selected function in the trace part is shown. This is split up into smaller rectangles to show the costs of its callees.</li></ul></p>
en_GB: <b>The Parts Overview</b><p>A trace consists of multiple trace parts when there are several profile data files from one profile run. The Trace Part Overview dockable shows these, horizontally ordered in execution time; the rectangle sizes are proportional to the total cost spent in the parts. You can select one or several parts to constrain all costs shown to these parts only.</p><p>The parts are further subdivided: there is a partitioning and an callee split mode: <ul><li>Partitioning: You see the partitioning into groups for a trace part, according to the group type selected. E.g. if ELF object groups are selected, you see coloured rectangles for each used ELF object (shared library or executable), sized according to the cost spent therein.</li><li>Callee: A rectangle showing the inclusive cost of the current selected function in the trace part is shown. This is split up into smaller rectangles to show the costs of its callees.</li></ul></p>

[ctx: PartSelection|]
en: Visualization
en_GB: Visualisation

[ctx: SourceView|]
en: The list can be found in the configuration dialog.
en_GB: The list can be found in the configuration dialogue.

[ctx: TabView|]
en: <b>Information Tabs</b><p>This widget shows information for the currently selected function in different tabs: <ul><li>The Costs tab shows a list of available event types and the inclusive and self-costs related to these types.</li><li>The Parts tab shows a list of trace parts if the trace consists of more than one part (otherwise, this tab is hidden). The cost of the selected function spent in the different parts together with the calls happening is shown.</li><li>The Call Lists tab shows direct callers and callees of the function in more detail.</li><li>The Coverage tab shows the same as the Call Lists tab, but also shows indirect callers and callees, not just direct ones.</li><li>The Call Graph tab shows a graphical visualization of the calls made by this function.</li><li>The Source Code tab presents annotated source code if debugging information and the source file are available.</li><li>The Machine Code tab presents annotated assembly instructions if profile information at instruction level is available.</li></ul>For more information, see the <em>What's This?</em> help of the corresponding tab widget.</p>
en_GB: <b>Information Tabs</b><p>This widget shows information for the currently selected function in different tabs: <ul><li>The Costs tab shows a list of available event types and the inclusive and self-costs related to these types.</li><li>The Parts tab shows a list of trace parts if the trace consists of more than one part (otherwise, this tab is hidden). The cost of the selected function spent in the different parts together with the calls happening is shown.</li><li>The Call Lists tab shows direct callers and callees of the function in more detail.</li><li>The Coverage tab shows the same as the Call Lists tab, but also shows indirect callers and callees, not just direct ones.</li><li>The Call Graph tab shows a graphical visualisation of the calls made by this function.</li><li>The Source Code tab presents annotated source code if debugging information and the source file are available.</li><li>The Machine Code tab presents annotated assembly instructions if profile information at instruction level is available.</li></ul>For more information, see the <em>What's This?</em> help of the corresponding tab widget.</p>
