Databases
StackOverflow2013
Postsdbo
POExtract localizable strings from source code, aspx, xaml to resource files
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POExtract localizable strings from source code, aspx, xaml to resource files
    primarykey
    data
    text
    <p>As part of internationalizing our application which is based on asp.net, c#, silverlight, XBAP, I'm evaluating approaches to start with. I'm having to chose between <a href="http://www.gnu.org/software/gettext/manual/html_node/C_0023.html" rel="nofollow">GNU gettext()(PO files)</a> and Microsoft's resource(resx) based approach. So at this juncture, I'm trying to understand what is the best way to extract localizable strings from .cs files, aspx, ascx, xaml (silverlight) files to resource files(resx) automatically if I have to go the MS way.</p> <p>I have below options in mind: </p> <ol> <li><a href="http://resourcerefactoring.codeplex.com/" rel="nofollow">Resource Refactoring tool</a>, but it extracts all strings (no matter if you have to translate or not) like page headers etc. And we cannot mark or exclude particular strings. Or we will have to manually select each string and then extract (right click and click extract).</li> <li><a href="http://www.jetbrains.com/resharper/webhelp/Resources__Index.html" rel="nofollow">Resharper's Localization assistance</a>, here I do not see the automatic extraction, but I'll have to manually extract string by string.</li> </ol> <p>I know there has to be a bit of manual intervention, but any advise would help in choosing the right direction, between gettext()(<a href="http://www.fairtutor.com/fairlylocal/" rel="nofollow">gnu gettext() c# or fairlylocal</a> or MS localization approach.</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USgsk
    1. USgsk
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POExtract localizable strings from source code, aspx, xaml to resource files
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POExtract localizable strings from source code, aspx, xaml to resource files
      1. This table or related slice is empty.
      1. VTUpMod
    1. COIf you are using VS 2010 then easiest way to localize aspx/ascx can be to use Tools->Generate Local Resource in design view. Also, don't forget to include java-script and images in your potential localization targets. Finally, it doesn't really matter if all strings are extracted for localization - if you don't want to localize some resource then leave it out from locale specific resource file. The default logic would fall-back on culture-neutral resources for the value.
      singulars
      1. POExtract localizable strings from source code, aspx, xaml to resource files
      1. USVinayC
    2. CO@VinayC: That does the trick for aspx/ascx, but I'm looking for a solution that would extract from source code and xaml too. Also, a resource file per page (or user control) looks more cumbersome when I have around 300 pages to handle, I hope we can club those in to one (with de-duping if there are any), but not sure on performance implications.
      singulars
      1. POExtract localizable strings from source code, aspx, xaml to resource files
      1. USgsk
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload