• <ins id="pjuwb"></ins>
    <blockquote id="pjuwb"><pre id="pjuwb"></pre></blockquote>
    <noscript id="pjuwb"></noscript>
          <sup id="pjuwb"><pre id="pjuwb"></pre></sup>
            <dd id="pjuwb"></dd>
            <abbr id="pjuwb"></abbr>
            posts - 319, comments - 22, trackbacks - 0, articles - 11
              C++博客 :: 首頁 :: 新隨筆 :: 聯系 :: 聚合  :: 管理

            Parse .strings file with Python

            Posted on 2013-01-08 13:44 RTY 閱讀(590) 評論(0)  編輯 收藏 引用 所屬分類: Mac os轉載隨筆

            Parse .strings file with Python

            I'm trying to write a small Python script to parse the .strings file in my iPhone application project and determine which keys might not be in use. I'm, also doing some string matching to filter out some of the results. This is where my problems start :). If I try something like

            for file_line in strings_file: if 'search_keyword' in file_line: ...

            the search keyword will often not match, even though if I print every file line in the same for I seem to be reading the text correctly and my search keywords appear.

            The problem is these .strings files are in some binary format. Does anyone know of a proper way to parse these files?

            asked Jan 25 '10 at 12:49
            Mihai Damian
            2,51631736

            80% accept rate
            Can you post an example .strings file? – Tim Pietzcker Jan 25 '10 at 12:57
            They are pretty standard in format. I have lines like: "Keyword" = "Value"; or "Keyword" = 0.0; The files are correct as far as they're concerned. I use them from Objective-C and I have no problems there. It's just that there I use some framework provided class to open them which I probably can't use from Python – Mihai Damian Jan 25 '10 at 13:04
            So how do you open the file? What does printing the repr() of a line you think should match show you? – Thomas Wouters Jan 25 '10 at 13:05
            1 
            I open it with open(filename, 'r'). Also tried 'U'. 'b' is not supported on Mac OS – Mihai Damian Jan 25 '10 at 13:11
            It just occurred to me I might be able to use PyObjC to use the Objective-C code that reads these files. I'm still open to simpler solutions though – Mihai Damian Jan 25 '10 at 13:14
            show 1 more comment
            feedback

            Use correct encoding to open the .strings-file and in your source code. According to documentationthe encoding of your file could be utf-16.

            # -*- coding: utf-8 -*- import codecs  for line in codecs.open(u'your_file.strings', encoding='utf-16'): if u'keyword' in line: # process line
            answered Jan 25 '10 at 13:27
            J.F. Sebastian
            61.9k1096173
            Thanks, this works perfectly. Using your solution I realized some of my .strings were encoded utf-8 and most were utf-16. This probably explains why the matching worked only in some of the files. – Mihai Damian Jan 25 '10 at 13:55
            feedback

            No experience with those .strings files, but here is the reason why you don't find matches:

            strings_file.read()

            returns a string with the full content of the file. Iterating over a string iterates over single characters, i.e. in your for loop, file_line isn't a line, it's always just one single character (a string of length 1), which obviously can't contain a multi-character search word.

            answered Jan 25 '10 at 12:57
            balpha
            12.9k55177
            Indeed. Use for line in strings_file: instead. – Thomas Wouters Jan 25 '10 at 13:01
            Ah, you are right, I was using simply for file_line in strings_file:, without the read(); will edit in a moment – Mihai Damian Jan 25 '10 at 13:02
            @MihaiD: for line in file will only work (as expected) on plain text files, which (as you say) the.strings files are not. – balpha Jan 25 '10 at 13:05
            feedback

            It sounds like the stings file was saved as data. If python can't read it as is you can convert it to a plain text file in Objective-c.

            Just: (1) read the strings file into a file with the proper encoding. (2) Convert to dictionary (3) write dictionary to another file.

            So:

            NSString *strings=[NSString stringWithContentsOfFile:filePath encoding:NSUTF16StringEncoding error:&error]; NSDictionary *dict=[strings propertyList]; [dict writeToFile:anotherFilePath atomically:NO]; 
            answered Jan 25 '10 at 13:33
            TechZen
            42.3k74379
            Yes, that's one way to go. Will keep in mind if all else fails. – Mihai Damian Jan 25 '10 at 13:47
            feedback

            Your Answer

            中文字幕精品无码久久久久久3D日动漫| 国内精品人妻无码久久久影院导航| 国产精品久久久久久久| 无码8090精品久久一区| 亚洲а∨天堂久久精品| 久久久久波多野结衣高潮| 亚洲国产精品一区二区久久hs| 久久精品国产亚洲AV高清热| 久久久久久综合一区中文字幕 | 国产激情久久久久影院小草 | 久久天天躁狠狠躁夜夜96流白浆 | 亚洲色大成网站www久久九| 久久香蕉超碰97国产精品| 国产精品九九久久免费视频| 久久久久久国产精品无码下载| 久久99久久99精品免视看动漫| 欧美久久久久久精选9999| 亚洲精品乱码久久久久久蜜桃不卡 | 久久精品无码一区二区三区| 色综合久久久久久久久五月| 国产Av激情久久无码天堂| 无码人妻久久一区二区三区| 激情久久久久久久久久| 亚洲AV无一区二区三区久久 | 精品久久久久久久国产潘金莲| 手机看片久久高清国产日韩| 久久九九全国免费| 香蕉久久夜色精品国产2020| 久久久久久久91精品免费观看 | 91亚洲国产成人久久精品| 国产成人久久精品二区三区| 久久久久国色AV免费观看| 九九久久精品无码专区| 久久人人添人人爽添人人片牛牛| 久久婷婷五月综合97色| 久久亚洲中文字幕精品一区| 精品久久久久久久久中文字幕| 久久99热这里只有精品66| 国产精品美女久久久久AV福利| 日韩人妻无码一区二区三区久久| 99久久99这里只有免费费精品|